Convert BMP to TIFF

The TIFF format supports it, but the conversion cannot invent it. A BMP has no alpha channel, so every pixel including the background arrives fully opaque. Run /image-removebackground/ afterwards to cut the subject out — then the alpha channel TIFF provides has something to store. TIFF handles CMYK, 16-bit depth, embedded ICC profiles and multi-page documents, which is exactly what print and archival workflows require.

No pixel data, no. Both formats store the image without lossy compression, so the picture that comes out is identical to the one that went in and the conversion can be repeated indefinitely. What changes is file size, and which features travel — colour depth, embedded profiles, layers and animation are all supported unevenly between lossless formats. BMP usually stores completely uncompressed pixel rows with a small header, which is why it is so simple to parse. TIFF is a container more than a codec: it can hold uncompressed, LZW, ZIP or even JPEG data, at up to 32 bits per channel, with multiple pages in one file.

Transparency survives when going to PNG, WebP, TIFF, GIF, or SVG. Converting to JPG flattens the alpha channel against a white background — if you need transparency, target a transparency-aware format instead of TIFF.

Embedded ICC color profiles are read from the source BMP and re-attached to the TIFF output where the format supports it (JPG, PNG, TIFF, WebP). Formats without profile support fall back to sRGB.

Camera EXIF (ISO, shutter, lens, GPS) is preserved by default during BMP → TIFF conversion when both formats support metadata. Use the privacy option to strip metadata before download if you want to share images without geolocation.

Yes — drag multiple BMP files into the upload zone and we queue them in parallel. Free users get 100MB per file; Premium has no per-file cap and runs more parallel workers, so a 200-image batch typically finishes in under two minutes.

For straightforward format conversion we run the same libpng / libjpeg-turbo / libwebp / ImageMagick pipelines a desktop editor uses, with the same quality. The difference is that desktop tools open one file at a time; we accept a batch and run them in parallel.

Default behaviour is 1:1 — your TIFF output has the same pixel dimensions as the source BMP. Use a separate /resize-image/ step after conversion if you need to downscale or upscale as part of the workflow.

For JPG / WebP, quality 75-85 typically gets the file 60-80% smaller than the source BMP with no visible difference at normal viewing distance. For lossless targets (PNG, TIFF), expect smaller savings — usually 5-30% via better deflate / LZW compression.

Yes — uploaded BMP files are processed in isolated workers and deleted within minutes. We never read, store, or share the pixel data. The full privacy policy and retention window are documented at /privacy/.

Yes for free up to 100MB. Premium handles larger inputs (300MB+) and exotic per-pixel depths (16-bit PNG, 32-bit float TIFF). The pipeline streams pixel rows, so memory use scales with the row count, not the total pixel count.