Both files stay local.
No upload. No cloud.
When the tool downstream wants raw pixels and nothing else — uncompressed, predictable, and Windows-shaped. Conversion runs instantly in your browser tab — no upload, no cloud, no per-seat ladder.
The lossy decompression already happened in the source JPG; we just read pixels.
Standard 24-bit BMP. Every pixel addressable, no compression. Predictable byte layout for legacy tools.
No upload. No cloud.
Each JPG becomes a BMP. Parallel processing in your browser.
BMP is one of the most boring image formats ever shipped, which is also why it persists. Some industrial software, some scientific instruments, and a long tail of legacy Windows applications still want their input as a flat, predictable, uncompressed bitmap. Re-encoding in the tab gets you there without an upload. The file size goes up, but predictability is the whole point.
Some legacy industrial software, scientific imaging tools, embedded systems, and older Windows applications only accept BMP. Outside those contexts, BMP is rarely the right answer.
Yes — BMP doesn't compress. Expect roughly 10× larger than the source JPG.
No. The JPG already lost data when it was first encoded. Converting to BMP doesn't get it back; it just writes the (already-lossy) pixels out uncompressed.
Yes — 24-bit RGB is preserved exactly.
Yes, drop a folder; each JPG becomes a BMP in parallel.