Convert JPEG to BMP

No. The compression artefacts already baked into the JPEG are ordinary pixel data now, and BMP preserves them perfectly rather than removing them. The file usually gets larger, sometimes several times larger. It is still worth doing before editing, because further edits will not stack a second generation of loss on top. BMP needs no decoder library at all, so it remains the safe interchange format for embedded systems and legacy Windows tooling. JPEG shares every JPG limitation — no alpha, generational loss on re-save — with the added nuisance of software that treats the two extensions differently.

It is converted to sRGB, because BMP has no CMYK mode. For screen use that is exactly what you want. For commercial print it is not — the gamut shift changes how saturated colours reproduce on press, so send the printer the original JPEG rather than the BMP. BMP is gigantic — a 12-megapixel photo is around 36 MB — and no browser treats it as a sane web format.

By default yes, wherever the target has somewhere to put it — camera model, exposure settings, lens and GPS coordinates all carry across. GPS is the field worth thinking about: if the image is going to be published, use the strip-metadata option so you are not broadcasting where the photo was taken. JPEG is the same standard as JPG and JFIF — the four-letter extension is the original, and the three-letter one exists only because of the DOS 8.3 filename limit.

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

Embedded ICC color profiles are read from the source JPEG and re-attached to the BMP 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 JPEG → BMP 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 JPEG 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 BMP output has the same pixel dimensions as the source JPEG. 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 JPEG 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 JPEG 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/.