JPG to BMP, raw and uncompressed. Nothing ever uploads.

Drop JPG photos below — get a raw BMP per file at 1/8/16/24/32-bit, in batches of up to 20. Converted entirely on your device.

  • Your file data never leaves the device
  • Full bit-depth range: 1/8/16/24/32-bit
  • Batch up to 20 files + ZIP
  • EXIF-rotated photos come out upright

Convert JPG to BMP

Add your JPG files

Drag & drop JPG files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Your browser decodes JPG natively — no decoder download, no waiting. EXIF rotation is applied, so phone photos come out upright.

    No files yet. Everything stays on this device. Downloads start instantly.

    Privacy you can verify, not just trust

    Most online JPG converters upload your photos to their servers first — and some keep a download link live for 30 days. This one can't: your browser decodes JPG natively and the BMP encoder runs entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no decoder to download and no file fetched after load for the conversion itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Convert any JPG above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — conversion still works.

    How to convert JPG to BMP without uploading it

    Every "free" online JPG converter you've used uploads your photos to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for days. For personal photos and anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.

    This tool does exactly that. When you drop a JPG here, your browser:

    1. Decodes the JPG natively — every browser includes a JPG decoder, so there is no decoder file to download and no waiting for a library to load.
    2. Reads the photo's EXIF orientation data and stores the output upright, so a portrait phone photo doesn't come back sideways. The rest of the EXIF data, including location, is dropped.
    3. Re-encodes the pixels as a raw BMP with a pure-JavaScript BMP encoder — BITMAPINFOHEADER, bottom-up rows, at the bit depth you chose. Your original file is never modified.

    What makes this converter different

    The converters that top the results for this search mostly upload your files to a server (XConvert, FreeConvert, Zamzar and ConvertFiles all convert server-side), and the client-side ones we found cap the bit depth — one offers only 24-bit and 32-bit output, another only a single file at a time under 5 MB. This page is the only dedicated JPG-to-BMP page we found that combines a batch of 20 files with a ZIP download, the full bit-depth range (1/8/16/24/32-bit), Floyd–Steinberg dithering, hardware and retro destination presets, and a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.

    When is BMP the right choice for a JPG?

    Almost never for sharing or storage — JPG is smaller and PNG is lossless and smaller still. BMP earns its place when the destination demands raw pixels: legacy Windows software and GDI tooling, printer utilities, embedded firmware and machine-vision rigs that read uncompressed data, and sprite or retro-game editors that load 1-bit or 8-bit BMPs. If the program you are feeding accepts anything else, use JPG to PNG instead and keep the smaller file.

    Honest limitations

    No quality recovery

    JPEG throws away detail when it compresses. A BMP holds the same decoded pixels, uncompressed — it cannot put back what JPEG discarded. Blocky artefacts in the JPG stay blocky in the BMP.

    BMPs are much larger than JPGs

    Expect roughly 20× the size for a 24-bit BMP of a photo, and more at 32-bit. Every file shows its size multiple honestly, and the batch bar shows the total before you download anything.

    16-bit loses colour depth

    16-bit BMP keeps 5 bits per channel — 32,768 colours instead of 16.7 million. Smooth gradients will band. Use it only when the destination insists on 16-bit.

    8-bit and 1-bit are approximations

    8-bit output is a 256-colour palette built by median cut; 1-bit is black and white only. Dithering fakes the missing shades by speckling pixels, but detail and smooth colour are lost either way.

    32-bit alpha is always 255

    JPG has no transparency, so there is no alpha to preserve. A 32-bit BMP from this tool is one-third larger than the 24-bit version with identical visible pixels — pick it only when the destination requires it.

    Metadata is stripped

    Camera metadata (EXIF, including location) is dropped on re-encode. The orientation tag is read and applied first, so the output is stored upright. Greyscale JPGs stay greyscale in the pixels.

    Frequently asked questions

    Will converting JPG to BMP restore lost quality?

    No. JPEG throws away detail when it compresses a photo, and no converter can put it back. The BMP holds exactly the pixels your browser decoded from the JPG — the same picture, uncompressed. If the JPG has blocky artefacts or soft edges, the BMP will have them too, only in a much larger file.

    Why is the BMP so much bigger than the JPG?

    BMP is uncompressed: every pixel is stored in full, while JPG compresses photos to a fraction of their raw size. A 1920×1080 photo is about 6 MB as a 24-bit BMP and often under 300 KB as a JPG — roughly 20 times larger. This tool shows the original and BMP size for every file, with the size multiple, so the trade-off is never hidden.

    Which bit depth should I choose?

    24-bit is the faithful choice for photos and screenshots — 16.7 million colours, no palette. 32-bit stores the same pixels plus an alpha channel that is always 255, because JPG has no transparency. 16-bit keeps 5 bits per channel and loses colour depth, so gradients band. 8-bit is a 256-colour palette approximation for retro hardware. 1-bit is black and white only, dithered, for game sprites and simple displays.

    What is 32-bit BMP if JPG has no transparency?

    Nothing extra. A 32-bit BMP is a 24-bit image with one more byte per pixel for alpha, and JPG has no alpha channel at all, so this tool writes 255 (fully opaque) for every pixel. The file is one-third larger than the 24-bit version with identical visible pixels. Choose 32-bit only when the program you are feeding insists on it.

    What happens to EXIF data and photo orientation?

    EXIF metadata, including location, is dropped on re-encode — the BMP carries no camera data at all, only dimensions. The EXIF orientation tag is the exception: it is read before encoding and applied, so a phone photo stored sideways comes out upright in the BMP. Greyscale JPGs stay greyscale in the pixels, stored as equal red, green and blue values.

    Why would anyone need a BMP in 2026?

    Some software only speaks BMP: legacy Windows applications and GDI tooling, printer utilities, embedded firmware and machine-vision rigs that expect raw uncompressed pixels, and sprite or retro-game editors that load 1-bit or 8-bit BMPs. BMP is also the simplest format to parse by hand, which is why hardware and teaching tools still use it. For anything else — sharing, web, storage — keep the JPG or use PNG.

    Can I convert several JPGs at once?

    Yes. Add up to 20 JPG files (25 MB each), pick a bit depth and width, and press Convert. Each file gets its own BMP download, and Download all as ZIP bundles them into one archive. BMPs are large, so a full batch of photos can be hundreds of megabytes — the tool shows the total size before you download.

    Is there a file size or daily limit?

    There is no daily limit and no account. A 25 MB safety cap applies per file and 20 files per batch, because decoding large images in the browser is memory-heavy and BMP output is much larger than the JPG input. Most JPGs saved from a phone or the web are well under 5 MB, far below the cap.