Initializing... drag & drop files here
Supports: NEF
This walk-through is for anyone who needs a Nikon NEF RAW photo turned into a plain Windows bitmap — usually because a Windows application or imaging pipeline insists on an uncompressed .bmp and won't accept anything else. It explains how to render the NEF, what the BMP gives up versus the RAW, why the output file is so large, and when you should pick NEF to PNG or NEF to JPG instead.
.nef onto the page or click "+ Add Files" to browse. You can queue several Nikon RAW files to convert with the same settings.The only real decision on this page is the Quality preset, because BMP itself has nothing to tune — it just stores whatever pixels the render produces, uncompressed. A NEF is not a picture yet: it is raw sensor samples with white balance, hue, tone and sharpening kept as adjustable instruction sets rather than baked into the image (per Nikon). To write a BMP the converter must demosaic that data and develop it into finished 8-bit-per-channel RGB, applying one fixed interpretation of those settings. After that step there is no compression loss layered on top — but the RAW latitude is spent.
.nef as your master.<img> tag and many phone galleries support it only partially. For viewing or sharing, NEF to JPG or NEF to PNG is the safer target.BMP is the right target only when a Windows tool, legacy application, or imaging pipeline specifically demands an uncompressed .bmp. For almost everything else it is the wrong choice: it is lossless but pays for that with enormous files and poor web support, while NEF to PNG is also lossless yet compressed and broadly viewable, and NEF to JPG is far smaller for sharing. If your .nef is corrupted or from a brand-new camera body the converter hasn't profiled, the render may fail or look wrong — re-export from Nikon's own software first, then convert that file.
Because BMP applies no compression to the rendered pixels — the size is fixed arithmetic, not an estimate. A 24-bit BMP is width × height × 3 bytes, so a ~24-megapixel NEF (about 6000×4000) becomes roughly 6000 × 4000 × 3 ≈ 72 MB, and a ~45-megapixel NEF (about 8256×5504) becomes roughly 8256 × 5504 × 3 ≈ 136 MB. The NEF is smaller because it stores compact sensor data, often losslessly compressed. If that size is a problem, NEF to PNG is lossless too but compressed, usually a fraction of the BMP.
Yes — that is the main thing to understand. A NEF keeps 12-bit or 14-bit sensor data with white balance, hue, tone and sharpening held as adjustable instruction sets rather than baked into the pixels, as Nikon describes. Rendering to BMP flattens those decisions into fixed 8-bit pixels, so you can no longer non-destructively recover highlights or redo the white balance. Keep the original .nef as your master and treat the BMP as a finished export.
No new compression loss after the render — BMP stores the rendered pixels exactly, with nothing thrown away on top. The loss that matters happens earlier, at the render step: the converter demosaics the RAW and bakes in white balance and exposure, collapsing the RAW's adjustable latitude into one fixed 8-bit interpretation. The pixels you get are exact; what you lose is the ability to re-render them differently later.
The output is a standard 24-bit true-color BMP — 8 bits each for red, green, and blue. A Nikon sensor captures 12-bit or 14-bit data, so the conversion maps that down to 8-bit per channel, and there is no higher-bit-depth selector for BMP on this page. If you specifically need to retain more than 8 bits of tonal data, BMP isn't the right target — NEF to TIFF can hold 16-bit data instead.
For most people, PNG is the better choice: it is lossless like BMP but compressed, so you get the same pixel-exact render at a much smaller size and with native browser support. Pick JPG when you just need a small, shareable photo that opens everywhere. Choose BMP specifically when a Windows tool or imaging pipeline requires a plain uncompressed bitmap and won't take anything else. In our testing, a full-resolution 24 MP NEF rendered to a 24-bit BMP landed near 72 MB, while the same render as PNG was several times smaller with no loss of pixel detail.
Your NEF is uploaded over an encrypted connection, rendered on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and your photos are never shared or made public.