Skip to content

RAF to NEF Converter

Convert RAF to NEF in your browser. You download a Linear DNG (.dng), not a .nef: only a Nikon camera can create a genuine NEF, and every editor that opens NEF also opens DNG. Nothing is uploaded.

  • Processed locally
  • No upload, no wait
  • No sign-up
  • No watermark

Drop images here

or choose files · paste with Ctrl/⌘ V

RAW expected · other image formats also work

Files are processed on this device. Nothing is uploaded.0 B uploaded

How to use RAF to NEF

  1. 1

    Add your RAF files: drop them here, choose them, or paste from the clipboard.

  2. 2

    There is nothing to tune: the DNG is written uncompressed. Resizing and rotating are under More options if you need them.

  3. 3

    Click Convert. Each file is decoded and encoded in a background thread on this device.

  4. 4

    Download the .dng files one at a time or together as a ZIP.

Why use Aback Images for raf to nef

Where a NEF would go

NEF files are opened by Nikon NX Studio, Lightroom, Photoshop Camera Raw, Capture One and RawTherapee, and every one of them opens the DNG too.

DNG next to RAF

The DNG stores the camera preview's pixels uncompressed, so it can be as large as the 20 to 60 MB raw file, or larger, depending on the preview's resolution.

No new artefacts

The preview inside the RAF is a camera JPEG; the DNG stores its decoded pixels uncompressed, so this step adds no compression damage of its own.

Processed on your device

Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.

RAF vs NEF

What changes from RAF to NEF

Encoding: the RAF uses uncompressed or lossless compressed sensor data in Fujifilm's own container; NEF uses uncompressed, lossless compressed, lossy compressed, or High Efficiency on recent Z bodies, and the download is a Linear DNG: demosaiced 8-bit RGB with the colour matrices raw editors need.

Bit depth: 12 to 16 bits per channel depending on the camera in the RAF; NEF allows 12 or 14 bits per channel, and the DNG written here has 8 bits per channel, linearised. The sensor's 12 to 16 bits are not used: the 8-bit camera preview is converted.

Colour: camera RGB from an X-Trans 6×6 or Bayer 2×2 mosaic in the RAF; NEF supports camera RGB from a Bayer mosaic, written here as 8-bit sRGB.

Metadata: the RAF can carry EXIF and Fujifilm maker notes, including the Film Simulation; NEF can carry EXIF and Nikon maker notes, partly encrypted, plus a thumbnail and a larger preview, but nothing is copied across.

About RAF

RAF is the raw format of Fujifilm cameras, from the X series to the medium-format GFX. Most X-series bodies use an X-Trans sensor with a 6×6 colour filter pattern instead of the usual Bayer 2×2.

RAF is not TIFF at the top level: it opens with the text 'FUJIFILMCCD-RAW', then a header with the camera model and offsets to three blocks: a JPEG preview near the start of the file, a header describing the sensor layout, and the sensor data.

RAF files usually come from Fujifilm X-T, X-H, X-S, X-E, X100 and GFX cameras.

About NEF

NEF is the raw format of Nikon cameras, from the D1 to the current Z series. It stores 12 or 14-bit sensor data, uncompressed or compressed, with a JPEG preview the camera renders using its Picture Control.

NEF is TIFF-based: the first directory usually holds a small thumbnail, and sub-directories hold the sensor data and, on current bodies, a full-size JPEG preview. Nikon's maker notes are a TIFF structure of their own, and since the D2X their white-balance block is encrypted with a key derived from the camera's serial number and shutter count.

NEF files come from Nikon DSLRs (D-series) and Z-series mirrorless cameras.

When converting RAF to NEF makes sense

Forms and workflows that ask for NEF usually feed a raw editor, and each of those opens DNG as well, so the DNG can take the NEF's place. Keep the RAF if you only need to view or share the picture.

What NEF offers when it comes straight from the camera: Lossless compressed mode with no data loss; Picture Control recorded so Nikon NX Studio can reapply it; 12 or 14-bit sensor data. Its drawbacks: Partly encrypted maker notes; The lossy compressed mode discards some sensor data; Large files on high-resolution Z bodies.

Limitations

  • The JPEG preview is converted, and it already carries the Film Simulation (Provia, Velvia, Classic Chrome and so on) chosen in camera.
  • X-Trans sensor data is never demosaiced here, so none of the artefacts some raw developers produce from it appear.
  • The DNG holds the decoded 8-bit pixels, so it adds no dynamic range or detail beyond the RAF.

Frequently asked questions

Why do I get a .dng file instead of a .nef?

A real NEF is written by Nikon cameras and holds the sensor's own readings (12 or 14 bits per channel, stored as uncompressed, lossless compressed, lossy compressed, or High Efficiency on recent Z bodies) along with EXIF and Nikon maker notes, partly encrypted, plus a thumbnail and a larger preview. This converter reads the JPEG preview inside the RAF, not its sensor data, so it cannot make one either. The Linear DNG you get instead is Adobe's open raw format, and every editor that opens NEF files opens it with the same raw controls. It holds decoded pixels, so it adds no quality or dynamic range.

Are my images uploaded anywhere?

No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.

Can I process many files at once?

Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.

Is it free? Is there a file limit or watermark?

It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.