Initializing... drag & drop files here
Supports: BMP
A .bmp is a Windows Bitmap — a raster image that usually stores its pixels uncompressed, which is why BMP files are so large. This page converts a single BMP into a static .gif, walks through the one setting that decides whether the result looks clean (the Colors control), and is honest about the split: flat-color graphics like UI screenshots, logos, and diagrams convert cleanly and often shrink dramatically, while 24-bit photos and gradients get squeezed into GIF's 256-color palette and visibly band. If a .gif extension is not a hard requirement, BMP to PNG is the better target for general use.
A typical BMP is stored at 24 bits per pixel — up to 16.7 million possible colors — with no compression, so a full-screen capture can run into several megabytes. GIF takes the opposite approach: it keeps at most 256 colors per image (8 bits per pixel) chosen from the 24-bit RGB space, then packs the indexed pixels with lossless LZW compression. That difference is the whole story of this conversion:
| Property | BMP (Windows Bitmap) | GIF |
|---|---|---|
| Type | Raster, normally stored uncompressed | Raster, palette-indexed |
| Origin | Microsoft Windows / OS-2 device-independent bitmap, mid-1980s | CompuServe GIF87a (1987), GIF89a (1989) |
| Colors | Commonly 24-bit (16.7 million); 32-bit variants add alpha | 256 per frame maximum (8-bit indexed) |
| Compression | Usually none (BI_RGB); optional run-length variants | Lossless LZW over the palette indices |
| Transparency | Per-pixel alpha in 32-bit variants only | 1-bit — one palette entry is fully transparent, everything else opaque |
| Animation | No | Yes, in GIF89a (not from a single still) |
| Metadata | Minimal — no Exif in the base format | Comment and application extension blocks |
| Best for | A lossless working copy on Windows | Flat-color graphics and destinations that demand .gif |
.bmp onto the page or click "+ Add Files" to pick it from your computer. You can queue several files and convert them with the same settings in one batch.GIF stores at most 256 colors per image, chosen from the full 24-bit RGB space, so the Colors control is where you spend your quality budget. How you set it decides whether the output is crisp or obviously stepped:
.gif extension is negotiable, convert to PNG (lossless, no color limit, real transparency) or JPG (built for photos) instead.Choosing "By Color Reduction + Dither" (under File Compression → Custom) opens a Color Palette Size dropdown with the eight power-of-two palettes GIF allows, plus a Dither control. Because GIF stores one index per pixel, halving the palette removes one bit per pixel before LZW compression even runs:
| Color Palette Size | Bits per pixel | Best for | What you give up |
|---|---|---|---|
| 256 | 8 | Screenshots with shading, icons with soft edges, anything you are unsure about | Nothing beyond GIF's own ceiling — this is the largest GIF of the set |
| 128 / 64 | 7 / 6 | UI captures, charts, diagrams, maps with a modest color count | Slight shifts in anti-aliased text and drop shadows |
| 32 / 16 | 5 / 4 | Logos, line art, flat illustrations, pixel art | Any photographic region posterizes hard |
| 8 / 4 | 3 / 2 | Two- and three-color stencils, sprites, simple icons | All shading collapses into flat blocks |
| 2 | 1 | Pure black-and-white line art, scanned faxes, silhouettes | Every pixel becomes one of two colors |
Dithering trades banding for noise: it scatters pixels of neighbouring palette colors to fake in-between shades, which helps gradients but adds texture that LZW cannot pack efficiently, so a dithered GIF is usually larger than an undithered one at the same palette size.
If your goal is an animated GIF, this single-image converter is the wrong tool — it does not stitch several BMPs into one moving file. And if you are converting a 24-bit photo only because something asked for a .gif, first check whether it needs the GIF format or just a smaller, more portable image: in most cases BMP to PNG keeps every color losslessly, and BMP to JPG handles photographs far better, while GIF would visibly degrade the picture.
It depends entirely on the image. A flat-color BMP — a UI screenshot, logo, chart, or piece of line art — fits inside GIF's 256-color palette and converts with no visible loss, often shrinking a lot because the uncompressed bitmap becomes LZW-compressed. A 24-bit photograph or gradient holds far more than 256 colors, so smooth areas band visibly. If you only need a non-animated image and the format is up to you, PNG keeps every color and JPG handles photos more gracefully.
Because BMP stores pixels uncompressed — a 24-bit bitmap dedicates three bytes to every pixel regardless of content — while GIF indexes the image to a small palette and compresses it with lossless LZW. A screenshot or diagram uses few distinct colors and large flat regions, which is exactly what LZW rewards, so the GIF can be a small fraction of the BMP's size with no quality loss. The win disappears on photographic content, where flat regions are scarce.
No. One still image produces one static GIF frame. GIF animation is a sequence of frames played in order, which needs multiple source frames — this tool converts a single BMP to a single static .gif. To build a moving GIF you would start from a video clip, not one bitmap.
Only as a hard cutout. A 32-bit BMP can store per-pixel alpha, but GIF transparency is binary: one palette index is fully transparent and every other pixel is fully opaque, with no partial opacity. Anti-aliased or feathered edges that relied on alpha will turn jagged against a new background. For smooth transparency, convert to PNG, which has a full alpha channel.
Almost only when a destination specifically requires the GIF format — some legacy forums, ticketing systems, and dated upload widgets still demand .gif — or when you have genuinely flat graphics like simple logos or pixel art, where GIF can match or beat PNG on size. For everything else, especially photos and anything needing clean transparency, BMP to PNG is the better target because PNG is lossless and has no 256-color ceiling.
Yes. GIF's LZW step is mathematically lossless — it never throws pixels away — so the only loss in this conversion comes from quantization, the stage that maps 24-bit colors onto the palette. If your BMP contains fewer distinct colors than the Color Palette Size you choose, nothing has to be remapped and the GIF reproduces the bitmap exactly, just far smaller. That is why a two-color diagram or a flat-color logo survives untouched while a photograph does not.
It is not carried across in a form print software will read. A BMP header records pixels-per-metre values for horizontal and vertical resolution, but GIF has no equivalent field in its own specification — a GIF describes its size purely in pixels. The image data is unaffected, so a 3000 x 2000 BMP is still 3000 x 2000 pixels as a GIF; you simply lose the "this was 300 DPI" hint, which matters for a print workflow and not at all for a web or forum upload. If you need the resolution tag preserved, convert to a format that stores it, such as PNG with its pHYs chunk.
Your file is uploaded over an encrypted connection, converted on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. In our testing, a flat-color UI screenshot saved as a 24-bit BMP reduced to a 64-color palette produced a GIF a fraction of the original size with no visible loss, while the same control applied to a 24-bit photograph produced visible banding in the sky and a much smaller quality benefit.