PicaJet

Reference Formats

NEF

Nikon's proprietary TIFF-based RAW format, introduced with the Nikon D1, storing unprocessed sensor data with several internal compression options and Nikon-specific MakerNotes metadata.

Extension

.nef

Full name

Nikon Electronic Format

Introduced

1999, with the Nikon D1

Vendor

Nikon

What is inside the container

NEF is TIFF/EP-derived, carrying an embedded JPEG preview, standard Exif data, and a Nikon MakerNotes block (Picture Control settings, autofocus points, lens data). Nikon has shipped several distinct internal compression schemes over the format's life — lossless-compressed, compressed, uncompressed, and newer "high efficiency" variants on recent bodies — each of which third-party decoders have to support individually rather than assuming one universal NEF structure.

How to open it

Nikon native Nikon NX Studio (successor to Capture NX-D and View NX-i)
Cross-vendor commercial Adobe Camera Raw / Lightroom Classic
Cross-vendor commercial Capture One
Open source RawTherapee and darktable

For archives

NEF has over two decades of continuous vendor support and broad third-party coverage, making it low-risk to keep as-is for most active archives. For a DAM handling mixed-brand collections, still consider a DNG conversion pass to normalize toward a single RAW format, since Nikon periodically introduces new internal compression variants that older raw-processing software may not decode correctly.

Nikon introduced NEF with the D1 in 1999, the company’s first fully in-house digital SLR and one of the earliest manufacturer-specific RAW formats on the market. Being TIFF-based from the outset gave third-party software a documented structural starting point, similar to Canon’s later CR2, and NEF has stayed Nikon’s format of choice across every DSLR and mirrorless body the company has released since.

The practical wrinkle for a DAM is that NEF is not one fixed structure but a family of internal variants Nikon has introduced over 25-plus years — lossless-compressed, compressed, uncompressed, and, on recent mirrorless bodies, newer high-efficiency compression modes. A raw-processing engine that handled NEF perfectly for a 2010-era Nikon body isn’t guaranteed to correctly decode a current-generation camera’s NEF without an update, which is a common source of “why won’t my DAM preview this RAW file” tickets when a photography team upgrades cameras faster than their asset-management stack’s raw engine gets updated.

Frequently asked

Does NEF use one consistent internal compression scheme?

No. Nikon has shipped several distinct internal compression schemes over NEF's life, including lossless-compressed, compressed, uncompressed, and newer high-efficiency variants on recent bodies, each of which third-party decoders have to support individually.

Is NEF structurally related to TIFF?

Yes. NEF is TIFF/EP-derived, carrying an embedded JPEG preview, standard Exif data, and a Nikon MakerNotes block for Picture Control settings, autofocus points, and lens data.

Should a DAM convert NEF masters to DNG?

Not urgently for single-brand archives. NEF has over two decades of continuous vendor support and broad third-party coverage, making it low-risk to keep as-is; a DNG pass is worth considering mainly for DAMs handling mixed-brand collections or to guard against newer Nikon compression variants older software cannot decode.

When was NEF introduced?

1999, with the Nikon D1.

What native Nikon software opens NEF?

Nikon NX Studio, the successor to Capture NX-D and View NX-i.

Why might a newer Nikon camera's NEF files fail to open in older raw-processing software?

Nikon periodically introduces new internal compression variants, such as recent high-efficiency modes, that older raw-processing software may not yet decode correctly.

What does NEF's Nikon MakerNotes block contain?

Picture Control settings, autofocus points, and lens data, layered on top of standard Exif metadata.

What third-party tools can decode NEF besides Adobe products?

Capture One commercially, and RawTherapee and darktable as open-source options.

Sources