NEF to JPG — Free, Fast & Private
NEF — Nikon Electronic Format — has a distinction almost no other raw format can claim: Nikon has kept the same extension across its entire digital era. A D70 from 2004, a D750 from 2014, and a current Z-series mirrorless body all write .nef, where Canon split its history into CR2 and CR3. The practical consequence is that "a folder of NEFs" can span twenty years of bodies and multiple internal format revisions — and the failure mode is always the same: a computer without raw software shows grey placeholder icons, a family member cannot open the attachment, an upload form wants JPEG. This tool converts NEF to JPG on your own machine. The file is decoded in your browser by a real raw pipeline, and never leaves your device on the way.
What a NEF actually holds, and why demosaicing matters
A NEF stores what the sensor saw before the camera made any rendering decisions: each photosite's raw reading — 12 or 14 bits deep, against a JPEG's 8 — behind a colour filter mosaic, plus the camera's white balance and picture settings recorded alongside rather than baked in. Turning that into a viewable image means demosaicing: reconstructing full-colour pixels from the mosaic of single-colour readings. This tool does that work for real — unpacking the sensor data and demosaicing with your camera's recorded white balance — rather than taking the shortcut of extracting the small JPEG preview Nikon embeds for the camera's rear screen, which is how suspiciously instant converters manage to be instant. The difference lands in the output: sensor resolution versus a screen-sized approximation.
Twenty years of NEF variants, one honest caveat
Under the stable extension, NEF has evolved: 12-bit and 14-bit depths, uncompressed, lossless-compressed and lossy-compressed flavours, changing sensor formats. The LibRaw decoder this tool ships handles that spread — it is the library much of the raw-processing ecosystem leans on precisely because it tracks camera support so broadly. One honest caveat: Nikon's newest Z bodies introduced High Efficiency compressed NEF variants using a newer compression scheme, and the freshest camera formats routinely lead third-party decoder support by some months. If a particular file is beyond the decoder, you get a clear error — never a silently exported preview pretending the conversion worked. For the overwhelming bulk of NEFs in circulation, from D-series archives to current standard-compression Z files, the full pipeline runs.
On-device, and why that suits raw files in particular
Raw converters that work by upload have an awkward shape: NEFs are big — 20 to 60 MB is routine for modern bodies — so you wait for a large upload, then a queue, then a download, and your unpublished work sits on someone else's server in between. Here the direction is reversed: about 1.4 MB of decoder (LibRaw compiled to WebAssembly) downloads from this site's own servers on your first conversion, gets cached by the browser, and every conversion after that starts instantly and works entirely locally. A 40 MB file converts without 40 MB moving anywhere. For photographers, the privacy is not abstract — client galleries, unpublished work, and second-shooter contracts all have opinions about where files may travel, and "nowhere" is the easy answer to defend.
Resolution, the quality slider, and the canvas ceiling
The export honours sensor resolution up to one disclosed limit: browsers cap the total canvas area they will allocate, and high-megapixel NEFs — 24 MP and up, which covers a lot of Nikon's recent lineup — can exceed it. When that happens the JPG is exported at the largest size the browser allows and the notice states both figures, native and exported. The quality slider defaults to 90%, a keep-forever setting; for email and portal uploads, drop it, or hand the converted file to the JPEG compressor to hit an exact KB target. And if the destination is a government or exam portal with strict dimension rules, the resizer takes the JPG from here.
Metadata: read for display, dropped from the export
NEFs carry a rich metadata block — body and serial number, lens, exposure settings, timestamps, GPS coordinates when location was on. The tool reads it to show you what it decoded, and then exports pixels only: the JPG that comes out carries no EXIF at all, because the conversion re-encodes image data from scratch. That default suits the most common reason for converting — sharing with someone who needs the picture, not your gear inventory or the shoot's coordinates. The original NEF on your drive keeps its full metadata untouched. Shooting Sony or Canon alongside? The same converter handles ARW, CR2 and DNG.