GIF to BMP, frame by frame. Nothing ever uploads.

Drop GIF files below — still GIFs become one BMP, animated GIFs become one BMP per frame, at 1/8/16/24/32-bit, in batches of up to 20. Converted entirely on your device.

  • Your file data never leaves the device
  • Animated GIF → one BMP per frame
  • Full bit-depth range: 1/8/16/24/32-bit
  • Batch up to 20 files + ZIP

Convert GIF to BMP

Add your GIF files

Drag & drop GIF files here

or browse your files · you can also paste from clipboard (Ctrl+V)

GIFs are decoded in your browser with the vendored omggif decoder — no decoder download, no waiting. Animated GIFs convert to one BMP per frame; still GIFs convert exactly.

Animated GIF? Every frame becomes its own BMP — BMP cannot store animation, so the motion is kept as a numbered stills sequence (anim-frame-01.bmp, anim-frame-02.bmp …). The frame count is shown on every file.

    No files yet. Everything stays on this device. Downloads start instantly.

    Privacy you can verify, not just trust

    Most online GIF converters upload your images to their servers first — and some keep a download link live for 30 days. This one can't: your browser decodes the GIF with a local decoder script and the BMP encoder runs entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no decoder to download and no file fetched after load for the conversion itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Convert any GIF above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — conversion still works.

    How to convert GIF to BMP without uploading it

    Every "free" online GIF converter you've used uploads your images to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for days. For personal graphics, icons, sprites and anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.

    This tool does exactly that. When you drop a GIF here, your browser:

    1. Decodes the GIF locally — the vendored omggif decoder reads every frame, compositing each one onto the full canvas and honouring disposal methods, so a frame that only paints part of the image still converts as the complete picture.
    2. No rotation is applied — GIFs carry no orientation metadata, so the image is stored the way its pixels are. A GIF can carry comment and application extensions, but they are dropped on conversion, so the BMP carries no metadata at all.
    3. Re-encodes each frame as a raw BMP with a pure-JavaScript BMP encoder — BITMAPINFOHEADER, bottom-up rows, at the bit depth you chose. At 32-bit the GIF alpha channel is written into every pixel; at other depths transparency is flattened onto your chosen background colour. Your original file is never modified.

    What makes this converter different

    The converters that top the results for this search mostly upload your files to a server (XConvert converts server-side with three presets, and 101convert converts server-side and caps free files at 10 MB and three per batch), and the client-side ones we found cap the output — Convertlo keeps only the first frame of an animated GIF, Filevolve offers only 24-bit and 32-bit output, Fylo is a dedicated client-side page but 24-bit only and one file at a time, and Imagen asks for a free account before it converts. PureConverter runs ImageMagick in the browser as a batch tool, but it is a generic converter, not a dedicated GIF-to-BMP page. This page is the only dedicated GIF-to-BMP page we found that combines a batch of 20 files with a ZIP download, the full bit-depth range (1/8/16/24/32-bit), Floyd–Steinberg dithered 8-bit and 1-bit output, hardware and retro destination presets, a background colour for flattened transparency, one BMP per frame for animated GIFs, and a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.

    When is BMP the right choice for a GIF?

    Almost never for sharing or storage — GIF is far smaller and PNG is lossless and smaller still. BMP earns its place when the destination demands raw pixels: legacy Windows software and GDI tooling, printer utilities, embedded firmware and machine-vision rigs that read uncompressed data, and sprite or retro-game editors that load 1-bit or 8-bit BMPs. If the program you are feeding accepts anything else, use GIF to PNG instead and keep the smaller file.

    Honest limitations

    No animation in BMP

    BMP cannot store animation. An animated GIF becomes one still BMP per frame, in order — the motion is preserved as a sequence, not as a playable animation. Frame delays are not stored.

    BMPs are much larger than GIFs

    Expect roughly 10–30× the size for a 24-bit BMP of a still image, and more for animated GIFs, which produce one BMP per frame. Every file shows its size multiple honestly, and the batch bar shows the total before you download anything.

    GIFs are capped at 256 colours

    A GIF holds at most 256 colours, and converting cannot add detail. Dithering and banding in the GIF stay in the BMP — the BMP holds the same pixels, only bigger.

    16-bit loses colour depth

    16-bit BMP keeps 5 bits per channel — 32,768 colours instead of 16.7 million. Smooth gradients will band. Use it only when the destination insists on 16-bit.

    32-bit keeps alpha, other depths flatten

    A 32-bit BMP writes the GIF alpha channel, so transparency survives exactly — GIF alpha is all-or-nothing. At 24-bit and below there is no alpha channel: transparent areas are flattened onto the background colour you pick.

    Metadata is stripped

    Comment and application extensions are dropped on conversion. The BMP carries no metadata at all, only dimensions. Frame delays are not stored either — each frame is a separate still file.

    Frequently asked questions

    Does converting a GIF to BMP keep the animation?

    No. BMP cannot store animation at all, so the motion cannot survive the conversion. This tool keeps every frame instead of only the first: an animated GIF becomes one still BMP per frame (anim-frame-01.bmp, anim-frame-02.bmp and so on), in order, with the frame count shown on the file card. If you need the motion itself, keep the GIF.

    Why is the BMP so much bigger than the GIF?

    BMP is uncompressed: every pixel is stored in full, while GIF is a compact palette format with LZW compression. A 1920×1080 image is about 6 MB as a 24-bit BMP and often under 200 KB as a GIF — roughly 30 times larger — and an animated GIF produces one BMP per frame, so the total grows with the frame count. This tool shows the original and BMP size for every file, with the size multiple, so the trade-off is never hidden.

    Which bit depth should I choose?

    24-bit is the faithful choice for GIF graphics and screenshots — 16.7 million colours, no palette. 32-bit stores the same pixels plus the GIF alpha channel, so it is the only depth that keeps transparency. 16-bit keeps 5 bits per channel and loses colour depth, so gradients band. 8-bit is a 256-colour palette approximation — close to the GIF itself, which is already capped at 256 colours — for retro hardware. 1-bit is black and white only, dithered, for game sprites and simple displays.

    Does 32-bit BMP keep my GIF's transparency?

    Yes. A 32-bit BMP from this tool writes the GIF alpha channel into every pixel, so see-through areas stay see-through. GIF transparency is all-or-nothing — a pixel is fully opaque or fully transparent — so the preserved alpha is exact, with no blended edges. At 24-bit and below there is no alpha channel, so transparent areas are flattened onto the background colour you pick in the settings.

    Will converting GIF to BMP add detail or improve quality?

    No. A GIF is limited to 256 colours, and converting cannot add colours or detail that were never in the file. The BMP holds exactly the pixels your browser decoded from the GIF — the same picture, uncompressed. If the GIF is dithered or banded, the BMP will be too, only in a much larger file.

    What happens to GIF metadata?

    A GIF can carry a comment extension and application extensions, but they are dropped on conversion — the BMP carries no metadata at all, only dimensions. Frame delays are not stored either: each frame becomes a separate still file, so the timing of the original animation is not preserved in the output. The file card shows the total animation duration so you know what was in the source.

    Can I convert several GIFs at once, and is there a limit?

    Yes. Add up to 20 GIF files (25 MB each), pick a bit depth and width, and press Convert. Each frame of each file gets its own BMP download, and Download all as ZIP bundles them into one archive. There is no daily limit and no account. BMPs are large, so a full batch of animated GIFs can be hundreds of megabytes — the tool shows the total size before you download.

    Why would anyone need a BMP in 2026?

    Some software only speaks BMP: legacy Windows applications and GDI tooling, printer utilities, embedded firmware and machine-vision rigs that expect raw uncompressed pixels, and sprite or retro-game editors that load 1-bit or 8-bit BMPs. BMP is also the simplest format to parse by hand, which is why hardware and teaching tools still use it. For anything else — sharing, web, storage — keep the GIF or use PNG.