BMP and JPG both stay on your machine.
Nothing ever uploads. The conversion is local-first by architecture.
Windows-era bitmaps weighing in at megabytes, re-issued as JPGs an order of magnitude smaller — without ever leaving your browser tab. Conversion runs instantly in your browser tab — no upload, no cloud, no per-seat ladder.
No server. The browser reads the BMP header, we read the pixel grid, then re-encode.
Photographic quality preserved. Visual difference: imperceptible at normal viewing distances.
Nothing ever uploads. The conversion is local-first by architecture.
Each file processes independently. No queue, no rate limit, no daily cap.
BMP is the format Windows built when storage was cheap and the internet was a dial tone. It stores every pixel raw, with no compression and no smarts. That's why a single screenshot can balloon to 30+ MB. Converting to JPG re-encodes the pixel grid through a modern lossy codec — the same one your phone camera uses — and produces a file an order of magnitude smaller without any visible loss. The conversion runs in your browser tab, so no BMP ever leaves your machine.
BMP stores every pixel uncompressed. A 4K bitmap is 33 MB before any image data. JPG's whole purpose is to compress that down to something the web can ship in milliseconds.
JPG uses lossy compression, but at default quality the loss is invisible to the human eye. For most BMPs — screenshots, photos, scans — you'll never see a difference.
Pick PNG instead — also free, also local. BMP → PNG keeps every pixel exact and still ships ~2–4× smaller than the source.
Yes — RGB, RGBA, indexed-color, and run-length encoded variants all parse correctly.
Practical limit is your device's RAM. A 100MB BMP works fine on most modern hardware.