BMP → JPG
Converting locally — nothing is uploaded
Megabytes down to kilobytes — free, and finished on your machine.
Drop your BMPs in the drum
or — nothing leaves this tab
READS JPG · PNG · WEBP · GIF · BMP · SVG · AVIF
CYCLE →
WASH TEMP
OUT OF ORDER — JAM REPORT
The BMP → JPG cycle
Windows Paint exports and scanner defaults produce BMPs measured in tens of megabytes. One pass through the warm cycle and they travel like normal photographs.
Neither stock holds transparency, so nothing is lost in the wash. JPG lands at ordinary photograph weight. Either way, re-encoding through the canvas collects EXIF like lint — camera model, GPS coordinates and timestamps are stripped from the folded copy.
Need the other direction? Other routes into PNG → JPG, WebP → JPG, GIF → JPG, SVG → JPG.
Questions at the counter
Why are BMP files so enormous?
BMP stores raw pixels with essentially no compression: a 4000×3000 photo costs over 30 MB before anyone looks at it. JPEG describes the same pixels in a few hundred kilobytes.
Is any quality lost?
Only what the temperature dial chooses. BMP itself is uncompressed, so at Hot the result is visually indistinguishable while weighing a hundredth as much.
Should I just keep using BMP?
For archiving originals, PNG serves the same lossless purpose at a fraction of the size. BMP’s remaining role is mostly historical — and as the thing you convert away from.
Is the conversion really private?
Yes — architecturally. This page is static files; there is no server to receive an upload. Your BMP is decoded and re-encoded inside this tab by your own machine, and you can watch the absence of network traffic in your browser’s developer tools.