Initializing... drag & drop files here
Supports: NEF
NEF is Nikon's raw format: the unprocessed 12-bit or 14-bit sensor readout your camera wrote before white balance, hue, tone and sharpening were applied — Nikon keeps those "retained as instruction sets" rather than baked into pixels (Nikon USA on NEF). Almost nothing outside a raw editor opens that file, so this tool develops it into a PNG any viewer, editor or browser will read.
One thing worth knowing before you press Convert, because no other converter states it: at the default quality preset the PNG comes back as a 256-colour palette image, not a 24-bit true-colour file. Choose the "Highest" preset when you want true colour. The rest of this page explains what each control really does with a Nikon raw file.
.nef files onto the page or click "+ Add Files" to browse. Several Nikon shots can be queued and converted with the same settings.| Quality Preset | Palette step | Colours in the delivered PNG | Pick it for |
|---|---|---|---|
| Highest | skipped | Full true colour, 8 bits per channel | Archiving, print prep, anything you will edit again |
| Very High (Recommended) — the default | applied, quality ceiling 95 | Up to 256 | A small web-ready file where banding is acceptable |
| High | applied, ceiling 90 | Up to 256 | Same, slightly smaller |
| Medium | applied, ceiling 80 | Up to 256 | Thumbnails, contact sheets |
| Low / Very Low / Lowest | applied, ceiling 70 / 60 / 50 | Up to 256 | Only when file size is the single priority |
The palette step is why a "lossless" format can still lose data here: PNG's own compression is lossless, but reducing 16.7 million possible colours to 256 before that compression runs is not. On a photograph the visible symptom is banding in skies and skin tones.
Three sliders render on this page but have no effect on the file you download when the source is a Nikon raw file, so do not spend time on them:
The two controls that genuinely move the needle are the Quality Preset and Image resolution. "Specific file size" is also live if you need to hit a byte target, with "Auto Scale" allowed to drop resolution when compression alone cannot get there.
| Property | NEF (Nikon Electronic Format) | PNG (this output) |
|---|---|---|
| Type | Camera raw sensor data | Rendered raster image |
| Container | TIFF-structured, Nikon-specific | PNG chunk stream |
| Bit depth | 12-bit or 14-bit per channel | 8 bits per channel |
| White balance / tone | Held as editable instruction sets | Baked in at render time |
| Compression | Uncompressed or lossless-compressed raw | Deflate, applied after an optional palette step |
| Transparency | None (a photo is opaque) | Supported, but nothing to carry over |
| Opens without special software | No | Yes |
| Best for | The editable master of the shot | Sharing, embedding, viewing anywhere |
Only on the "Highest" preset. PNG's deflate compression is always lossless, but on every other preset the converter runs a palette quantiser first, and collapsing a photograph to 256 colours discards real image data before deflate ever sees it. We ran the exact command chain this page uses against a full-colour test image and the result reports back as a 256-colour file, which matches what the preset is designed to do. If you want a true-colour PNG from a Nikon raw file, set the Quality Preset to "Highest".
No. Nikon states that a NEF "retains 12-bit or 14-bit data" depending on the camera, but the render step here outputs 8 bits per channel, so that extra tonal headroom is gone even at the "Highest" preset. PNG itself can store 16 bits per channel; this pipeline does not produce one. If you need high-bit-depth output for heavy shadow or highlight work, develop the raw in Nikon NX Studio, Lightroom, Capture One or RawTherapee and export 16-bit from there.
Pick by what happens next. PNG at the "Highest" preset is the right call when you need an exactly-reproducible 8-bit render that any tool will open — screenshots of a shot, overlays, graphics work. Use NEF to JPG when the goal is emailing or posting the photo, since a JPG of the same frame is a fraction of the size. Use NEF to TIF when you want the widest editor and print-shop support and intend to keep working on the file, but read that page first: its default compression type is lossy JPEG-in-TIFF, not LZW.
Not on this conversion. When the source is anything other than a PNG, the palette size you choose is never handed to the quantiser (it runs at 256 colours), the compression speed is pinned to the slowest and most thorough setting, and the compression level is either overridden or discarded when the file is rewritten. They are shared image controls that stay visible across image targets; on a NEF source only the Quality Preset, Image resolution and Specific file size settings change the output.
No. A photograph fills its whole frame, so nothing in the raw file is transparent and the rendered PNG is fully opaque. PNG supports an alpha channel, but a format conversion cannot invent one. Cutting a subject out onto transparency is a masking job for an image editor, done after the conversion.
Both directions happen, and the Quality Preset decides which. A raw file stores one losslessly compressed sensor sample per photosite; a true-colour PNG stores three full colour channels per pixel, so a 24-megapixel frame carries roughly 72 MB of pixel data before deflate, and deflate saves comparatively little on photographic detail. That is why "Highest" often produces a file larger than the NEF. At any other preset the 256-colour palette step usually makes the PNG dramatically smaller than the raw file instead.
Core EXIF fields such as shutter speed, aperture, ISO, focal length and lens model are generally carried into the PNG, and the palette step explicitly copies the extra PNG metadata block across. Nikon's proprietary MakerNote tags — in-camera Picture Control, Active D-Lighting and similar — are not part of any standard PNG or EXIF tag set, so treat those as lost. Keep the original .nef if the shooting metadata matters for cataloguing.
A NEF holds the sensor's raw Bayer mosaic rather than a finished picture, so it has to be demosaiced and colour-managed before anything can display it. That is what "developing" a raw file means, and it is why operating-system photo viewers and web pages reject a .nef unless a camera-specific codec is installed. Converting to PNG performs that development once and writes out a standard image every viewer understands.
Your NEF is uploaded over an encrypted connection, rendered on our servers, and deleted automatically after a few hours. Nothing is shared or made public, there is no sign-up and no watermark. The practical limit on a large batch of 40-plus-megapixel raw files is upload size and time rather than anything at the conversion step.