How to convert TIFF to BMP without uploading it
Every "free" online TIFF converter you've used uploads your scans to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for days. For personal scans, photos 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 TIFF here, your browser:
- Decodes the TIFF with the bundled UTIF.js decoder — uncompressed, LZW, PackBits and Deflate TIFFs, greyscale, palette, CMYK and 16-bit files, all in the browser. JPEG-compressed TIFFs are refused with a clear message, because the decoder cannot read them.
- Converts every page to its own BMP — a multi-page scan becomes one BMP per page, named -p1, -p2 and so on, so no page is silently dropped. Orientation tags are NOT applied, so the BMP keeps the stored orientation. The rest of the metadata, including location, is dropped.
- Re-encodes the pixels as a raw BMP with a pure-JavaScript BMP encoder — BITMAPINFOHEADER, bottom-up rows, at the bit depth you chose. At 32-bit the TIFF 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, MConverter, 101convert and DigitalOfficePro all convert server-side), and the client-side ones we found offer only 24-bit output or no batch. This page is the only dedicated TIFF-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 dithering, hardware and retro destination presets, a background colour for flattened transparency, one BMP per page of a multi-page TIFF, 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 TIFF?
Almost never for sharing or storage — TIFF 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 TIFF to PNG instead and keep the smaller file.
Honest limitations
No quality recovery
A BMP holds the same decoded pixels, uncompressed — it cannot put back detail the TIFF never held. A soft or blocky scan stays soft or blocky in the BMP.
BMPs are much larger than TIFFs
Expect roughly 6–10× the size for a 24-bit BMP of a photo, and more at 32-bit. Every file shows its size multiple honestly, and the batch bar shows the total before you download anything.
Multi-page TIFFs become one BMP per page
A 3-page scan produces three BMPs, named -p1, -p2 and -p3. BMP has no pages, so there is no single-file multi-page output — the file card lists every page it produced.
16-bit TIFFs are downsampled, orientation is not applied
16-bit TIFF colour is downsampled to 8-bit per channel by the decoder, so deep-colour detail is not preserved. TIFF orientation tags are NOT applied — the BMP keeps the stored orientation, so rotate the scan first if it comes out sideways.
JPEG-compressed TIFFs are refused
Some TIFFs store their pixels with JPEG compression. This decoder cannot read those, so they are refused with a clear message instead of producing garbage. Re-save the TIFF as uncompressed, LZW, PackBits or Deflate and try again.
32-bit keeps alpha, other depths flatten
A 32-bit BMP writes the TIFF alpha channel, so transparency survives — the advantage over GIF. At 24-bit and below there is no alpha channel: transparent areas are flattened onto the background colour you pick. Metadata (EXIF, including location) is dropped.