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:
- 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.
- 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.
- 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.