Convert BMP to JPG.
Turn bulky BMP bitmaps into small JPGs — in your browser.
Drop BMP files here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
BMP stores every pixel raw, which is why screenshots and exports balloon to megabytes. JPG keeps what the eye sees at a fraction of the size — and the conversion runs entirely on your device.
How it works
- Drop files anywhere on the page, click to browse, or paste with ⌘V.
- Pick a quality or preset — or set an exact target size and let the tool find it.
- Compress, compare before/after, and download — individually or as a ZIP.
From 6 MB to a few hundred KB
BMP spends three bytes on every pixel no matter what the picture shows — a full-HD screenshot is ~6 MB before it contains anything interesting. JPG stores what the eye actually sees, so the same screenshot typically lands at 200–500 KB with no visible difference. Batches convert in one run and download as a ZIP.
When JPG is the wrong target
JPG is built for photos and smooth tones. If the BMP is a diagram, pixel art or a screenshot full of sharp text, flip the output format to PNG instead — lossless crispness in a fraction of BMP’s bytes, and the PNG compressor squeezes it further.
Frequently asked questions
Why are BMP files so large?
BMP is essentially uncompressed — three bytes per pixel plus padding. A 1920×1080 screenshot is ~6 MB as BMP and typically 200–500 KB as a JPG that looks identical.
Will the JPG lose quality?
JPG is lossy, but at the default quality the difference is invisible for photos and screenshots. For pixel-perfect graphics choose PNG or lossless WebP on the JPG tab instead.
Where do BMP files still come from?
Mostly older Windows software: legacy screenshot tools, scanners, industrial and medical systems, MS Paint saves. The format works fine — it simply predates modern compression, which is why the files are enormous.
Is it private?
Yes. The conversion happens entirely on your device — the image is read, re-encoded and saved without ever touching a network. There is no server-side queue, no temporary copy in some bucket, nothing to expire or leak. Want proof? Run one file through, switch your connection off, and run another — it still works.