Windows Bitmap (BMP) files remain the blunt, honest way to store raster pixels: a straightforward header, optional palette, and raw or lightly packed scanlines that every graphics API from the 1990s onward learned to read. That simplicity is also why BMP archives balloon in size—especially for 24-bit truecolor captures where three bytes per pixel (plus row padding) add up faster than stakeholders expect when they email “just the screenshot.” Tagged Image File Format (TIFF), by contrast, is the professional interchange container print shops, legal archives, GIS pipelines, and medical imaging front-ends still cite when they want **lossless** delivery, explicit resolution metadata, optional transparency, and compression choices that can shrink strip data without re-quantizing color the way JPEG would.
SynthQuery’s **BMP to TIFF Converter** bridges those worlds entirely in your browser: drag up to twenty `.bmp` files (each up to one hundred megabytes—matching how large uncompressed captures can grow), preview them locally, pick DPI tags that map to TIFF XResolution and YResolution for print briefs, choose **uncompressed** strips when compatibility paranoia wins, **LZW-labeled PackBits** (TIFF compression type 32773) for lightweight lossless run-length encoding, or **ZIP / Adobe Deflate** (TIFF type 8) for zlib-style lossless compression that often beats PackBits on noisy screenshots, toggle whether 32-bit BMP alpha becomes a four-channel RGBA TIFF or flattens to opaque RGB over white, and download each `.tif` separately or bundled in a ZIP. Decoding uses the same Canvas and ImageBitmap path browsers already rely on to paint BMP in tabs; encoding uses UTIF.js with optional Web Worker offload so long batches do not freeze the UI. **Nothing is uploaded** to SynthQuery for the conversion itself—critical for regulated imagery, unreleased product shots, and any laptop where installing IrfanView or ImageMagick is not an option. This introduction situates BMP-to-TIFF in professional archiving, print, and publishing workflows where container choice matters as much as pixel values.
What this tool does
The interface is organized around **ingestion**, **color and alpha policy**, **resolution metadata**, and **compression semantics**, mirroring our PNG to TIFF tool so power users recognize the mental model immediately. Ingestion accepts BMP by MIME type (`image/bmp`, `image/x-ms-bmp`) or `.bmp` extension, rejects oversize files with a clear toast, and caps the queue at twenty items to protect memory on mid-tier hardware. Thumbnails use blob URLs that are revoked when you remove rows or clear the session, preventing long editing cycles from leaking object URLs.
**Alpha handling** is explicit because TIFF transparency semantics differ from BMP’s fourth byte in 32-bit DIB layouts. With **Preserve alpha** enabled, the converter samples eight bits per channel including unassociated alpha and writes PhotometricInterpretation RGB with ExtraSamples configured for transparency-aware viewers. When disabled, each bitmap is drawn over solid white before readback, yielding a three-sample TIFF that matches what many print vendors expect when they refuse “live” transparency in a flat master.
**DPI presets** (72, 150, 300, 600) encode rational resolution tags with inch units—the same vocabulary designers use when discussing commercial offset, photo lab, or large-format jobs. These tags **do not resample** pixels; they describe how layout software should map the existing grid to physical units. If you need a different inch-per-pixel ratio without changing dimensions, adjust DPI here; if you need more pixels, pair this tool with the **Image Resizer** first.
**Compression** interacts with both file size and decoder expectations. **Uncompressed** strips maximize compatibility at the cost of the largest files—sometimes comparable to BMP itself depending on headers. **PackBits** applies Macintosh-style RLE to strip bytes (TIFF tag 32773) and remains widely implemented for baseline RGB(A) TIFFs. The menu label **LZW (PackBits)** reflects how many teams colloquially bucket “legacy lossless TIFF compression” even though classic TIFF LZW is technically tag 5; browser-side UTIF encoding does not emit tag 5, so we surface PackBits under the LZW column with honest footnotes in the UI and FAQ. **ZIP / Deflate** uses Adobe’s TIFF compression tag 8 with zlib deflate, the same algorithm family PNG uses internally—often the best byte savings on gradients and photographic noise while staying lossless relative to decoded pixels.
**Batch conversion** walks the queue sequentially, shows per-file output sizes against the bloated BMP inputs, and exposes **Download all as ZIP** when more than one TIFF succeeds—ideal for DAM uploads or ticket attachments. **Web Workers** mirror the PNG→TIFF pipeline: when a dedicated worker is available, strip compression and UTIF packing run off the main thread; if the worker fails to spin up, the page falls back to synchronous encode with a toast so you are never stuck silent.
Technical details
**BMP** stores raster data in a BITMAPFILEHEADER plus DIB header variants (BITMAPINFOHEADER, V4, V5) describing dimensions, bit depth, compression mode (usually BI_RGB for uncompressed), and palette entries when bit depth ≤ 8. Pixels typically arrive bottom-up in BGR order for 24-bit modes, with optional alpha in 32-bit modes. There is no mandatory EXIF block like JPEG; metadata is sparse compared to TIFF or PNG ancillary chunks.
**TIFF** is a tagged IFD structure: each image describes photometric interpretation, samples per pixel, bits per sample, rows per strip, compression type, and offsets to strip data. SynthQuery emits baseline contiguous strips—one strip per page, rows per strip equal to image height—using big-endian “MM” magic and eight-bit samples. **Uncompressed** strips store raw interleaved RGB or RGBA bytes. **PackBits** (32773) applies run-length encoding on those bytes. **Adobe Deflate** (8) wraps zlib-compressed strip payloads that UTIF decoders inflate with pako.
**Metadata support** in this tool focuses on geometry, resolution, and software strings rather than full XMP or EXIF replication from BMP (which usually lacks rich camera tags). If you require ICC profile embedding or CMYK separations, desktop suites remain the appropriate layer after this conversion.
**Why not classic TIFF LZW (tag 5)?** Open-source browser encoders rarely implement tag-five writers with uniform patent/licensing history; PackBits and Deflate cover the practical lossless needs of most archival handoffs without surprising decoders.
Use cases
**Document archiving and records management** teams sometimes inherit thousands of BMP exports from vintage capture stations, fax gateways, or line-of-business scanners. TIFF remains the format many retention policies name explicitly because it pairs lossless RGB storage with rich tagging ecosystems. Converting BMP masters to TIFF with explicit DPI and compression makes it easier to ingest those rasters into enterprise DAMs without re-snapping paperwork.
**Professional printing and prepress** workflows frequently reject BMP even when the pixels are perfect. A print-ready TIFF with embedded resolution tags slots into InDesign, Affinity Publisher, or XPress placeholders without arguments from preflight tools. When art departments receive BMP logos from vendors who “only have the bitmap,” this converter upgrades the container minutes before imposition.
**GIS, mapping, and remote-sensing adjacency** often revolves around GeoTIFF, which this tool does **not** emit—but converting a BMP legend, color ramp, or scanned map tile to baseline TIFF is still a common preprocessing step before desktop GIS software attaches georeferencing tags. The lossless path ensures color ramps survive without JPEG ringing.
**Medical imaging and scientific visualization** sometimes intersect TIFF for PACS viewers, journal figure submission, or instrument software that predates PNG. Browser-side conversion keeps PHI on-device when policies forbid cloud upload converters; always follow your institutional BAA and de-identification rules regardless of tool architecture.
**Publishing and editorial** teams juggling legacy Windows assets benefit from batch ZIP export: drop an entire folder of BMP figures, convert with consistent DPI, and attach one archive to production. Pair with **TIFF to PNG** when the web team later needs transparent PNGs for the article HTML.
**Corporate IT and help desks** still encounter BMP screenshots from remote-support tools. Packaging them as TIFF can satisfy ticket systems that MIME-filter attachments or downstream OCR pipelines that prefer TIFF ingestion.
How SynthQuery compares
**Adobe Photoshop**, **GIMP**, **Affinity Photo**, and **XnConvert** provide industrial batch conversion, ICC embedding, JPEG-in-TIFF, CMYK, and scripting. They assume installation, updates, and sometimes subscriptions. **SynthQuery** targets borrowed laptops, locked-down corporate profiles, and mobile Safari sessions where native software is unavailable. Compared to ad-supported “upload to convert” sites, the differentiator is **privacy**: pixels stay in your tab. Compared to **ImageMagick** on a server you control, the differentiator is **accessibility**—no shell required, with transparent limits (twenty files, one hundred megabytes each) and immediate adjacency to other SynthQuery utilities listed at https://synthquery.com/tools.
Aspect
SynthQuery
Typical alternatives
Privacy
Canvas + UTIF.js (+ optional Web Worker) run locally; BMP bytes are not uploaded for conversion.
Hosted converters may process files on shared infrastructure with unclear retention windows.
Compression clarity
Uncompressed, PackBits (TIFF 32773), or Adobe Deflate (TIFF 8) with explicit FAQ on LZW tag 5.
Some web tools mislabel compression modes or recompress losslessly without disclosure.
Batch + ZIP
Up to twenty BMPs per session, per-file downloads, and one-click batch ZIP naming.
Desktop batch tools scale higher but require installs and scripted folder hygiene.
Print metadata
DPI presets write TIFF resolution tags for common print specs without resampling pixels.
Basic Save As dialogs may omit resolution tags unless you dig through export settings.
Ecosystem
Links to BMP→JPG/PNG, PNG→TIFF, TIFF→JPG/PNG, WebP Converter, JPG to PDF, Free tools hub, and full tools directory.
Single-purpose converter sites rarely sit beside AI writing, readability, and schema utilities.
How to use this tool effectively
**Step 1 — Collect BMP sources you are allowed to process.** Confirm licensing for stock captures, user uploads, and medical scans before conversion. Internal UI screenshots are usually straightforward, but compliance teams may still require audit trails—note the original filenames in your ticket because the tool preserves basenames in output names.
**Step 2 — Open `/bmp-to-tiff` and add files.** Drag files onto the dashed hero region or activate **Choose files** through keyboard (focus the drop zone and press Enter or Space, or tab to the hidden file input). Only BMP inputs enter the queue; other formats trigger a toast so you know they were skipped intentionally. Wait for thumbnails: if decode fails, the file may be corrupt, truncated, or blocked by browser security policy—re-export from the authoring application.
**Step 3 — Set DPI for your downstream consumer.** Pick 72 when the TIFF is primarily a screen reference embedded in layout drafts; 150 for quick office proofs; 300 for many commercial print specifications; 600 when a vendor requests ultra-fine addressability for plates or art reproduction. Remember: DPI metadata alone does not invent detail that was never in the BMP.
**Step 4 — Choose compression.** Use **Uncompressed** when a downstream validator rejects anything except tag 1. Choose **LZW (PackBits)** when you need modest lossless shrinkage with broad baseline TIFF support. Choose **ZIP / Deflate** when you want stronger lossless compression and your recipients run modern viewers (Photoshop, Affinity, Preview, many DAM transcoders). Read the helper copy under the select: classic TIFF LZW (tag 5) is **not** emitted in this browser encoder.
**Step 5 — Decide on alpha.** Leave **Preserve alpha** on when overlays, soft masks, or UI chrome with transparency must survive as RGBA TIFF. Turn it off when you need an opaque master matted on white—common for legacy print RIPs that ignore alpha.
**Step 6 — Convert and download.** Press **Convert to TIFF** and wait for the worker-backed encode. Review the byte comparison column: TIFF with uncompressed strips may approach BMP size, while Deflate may reduce bytes dramatically on complex rasters. Download individual `.tif` files or use **Download all as ZIP** for batches. If you also need JPEG for email, run **BMP to JPG** afterward; if you need PDF pagination, see **JPG to PDF** after an intermediate JPEG step, or explore **PNG to PDF** when your pipeline already moved through PNG.
Limitations and best practices
Browser memory and canvas limits still cap how many huge bitmaps you can decode at once; if conversion fails, use **Image Resizer** first or split batches. Exotic BMP variants (vendor-specific compression modes beyond what the browser decodes) may fail where desktop tools succeed. This tool does not emit BigTIFF, tiled TIFF, Fax Group 4, JPEG-in-TIFF, or GeoTIFF keys. For **BMP to PDF**, convert to JPEG or PNG first, then use **JPG to PDF** or **PNG to PDF**—there is no dedicated BMP-to-PDF route at launch. There is no **TIFF to BMP** page yet; use **TIFF to PNG** or **TIFF to JPG** and convert onward if you need BMP. Legally, confirm redistribution rights. For accessibility, pair exported figures with meaningful alt text in publishing systems—the TIFF itself does not supply web alt attributes.
Paginate JPEG sequences into PDF—use after BMP→JPG when your workflow needs a document container instead of a raster folder.
Frequently asked questions
BMP is a simple raster dump with minimal metadata and no standard compression story for truecolor files—files grow quickly and some enterprise tools prefer TIFF for archival indexes, print pipelines, and DAM MIME policies. TIFF lets you attach resolution tags, choose lossless strip compression, and package RGBA data in a container print vendors recognize. When you only need smaller files and lossy output is fine, BMP to JPG may be faster; when you need lossless web delivery without TIFF, BMP to PNG is the parallel path.
Yes relative to the pixels your browser decodes from the BMP: SynthQuery does not apply JPEG-style quantization. Uncompressed, PackBits, and Deflate modes all preserve the sampled RGB or RGBA values exactly. The only pixel change occurs when you disable Preserve alpha, which composites transparent areas onto white before encoding—a deliberate flattening, not a compression artifact.
The menu entry reads “LZW (PackBits, TIFF 32773)” because classic TIFF LZW (compression tag 5) is not emitted by this UTIF-based encoder. Instead, PackBits implements a lossless run-length scheme standardized for TIFF baseline readers. Many teams still ask for “LZW TIFF” colloquially when they mean “lossless compressed TIFF”; PackBits satisfies a large subset of those requests with honest tagging. If a vendor mandates true LZW tag 5 specifically, re-save through desktop software that supports that codec after verifying license policies.
ZIP / Deflate maps to TIFF compression type 8, Adobe’s zlib-wrapped deflate stream—the same algorithm family used inside PNG IDAT chunks and ZIP archives. Decoders inflate strip data losslessly back to raw RGB(A) bytes. It often yields smaller files than PackBits on noisy screenshots or gradients, though simple flat colors may favor PackBits. Always test outputs in the viewer your recipient uses if compatibility is uncertain.
Start with your vendor’s preflight checklist. Uncompressed TIFF is the safest lingua franca when specs are vague. When vendors allow lossless compression, Deflate (ZIP) is commonly accepted in modern RIP chains; PackBits is another conservative choice. Avoid assuming compression support for exotic RIPs—send a one-page test strip before batching thousands of plates.
When Preserve alpha is enabled, SynthQuery writes RGBA TIFF with ExtraSamples indicating unassociated alpha, similar to the PNG to TIFF tool. Not every legacy viewer composites TIFF alpha the way a browser composites PNG; disable the toggle to matte on white if your downstream path requires opaque RGB.
Up to twenty BMP files per session, each up to one hundred megabytes, matching other BMP utilities on SynthQuery. The queue processes sequentially to avoid exhausting GPU memory; if you routinely exceed these limits, use a desktop batch tool or split jobs.
No. Decode, rasterize, compress strips, and package TIFF bytes entirely inside your browser tab using JavaScript, Canvas (or ImageBitmap), UTIF.js, optional Web Workers, and JSZip for batch archives. Network activity is limited to loading the site assets themselves—your BMP contents are not sent to SynthQuery servers for conversion.
Uncompressed TIFF strips store the same interleaved samples as decoded RGB(A) data plus TIFF headers and IFD overhead; sizes can be similar or slightly larger depending on BMP row padding versus TIFF strip layout. Compressed modes usually reduce bytes, but highly random noise may resist RLE while still compressing under Deflate—compare the before/after stats in the UI.
Use BMP to JPG or BMP to PNG first, then WebP Converter for modern web codecs, or JPG to PDF / PNG to PDF when you need paginated documents. Dedicated BMP→WebP and BMP→PDF pages may arrive later; the linked tools cover the same workflows today without uploading sources to third-party converters.