Use the NEF Converter when you want a Nikon-produced TIFF working file from a NEF original, while leaving the original NEF unchanged.

Source files stay unchanged

The app does not modify original NEF files during conversion. The converter reads the NEF and writes new generated output files in the configured conversion folders. If a generated TIFF with the same output name already exists, the app can overwrite that generated TIFF.

The app also does not write metadata back into existing source images after capture. Capture-time metadata such as Artist Name, Copyright, and User Comment is handled by asking the camera to write supported body metadata fields before the image is saved. This preserves the camera-produced source file and any authenticity behavior the camera applies.

Converter Notes

  • It uses the Nikon Imaging SDK, Nikon's official NEF converter. The SDK uses Nikon's camera and sensor knowledge for NEF conversion. Nikon releases SDK updates after new camera releases and firmware changes. Nikon Imaging SDK news
  • The Image Browser and NEF Converter do not require the Nikon NEF Codec.
  • It converts a NEF to an uncompressed lossless TIFF with 16 bits per color channel and embeds as much of the NEF metadata as it can find in the TIFF and optional companion files.
  • The selected output color profile is used during the NEF to TIFF conversion, and the same profile is embedded in the resulting TIFF.
  • It converts asShot, which means it applies the camera settings recorded in the NEF, such as picture control, sharpening, and noise reduction. This usually makes the converted TIFF look close to the matching camera JPEG and the embedded NEF preview, without JPEG compression loss.
  • It does not provide manual conversion controls like Nikon NX Studio or other raw editors. The app is not an image editor.
  • The camera's 12-bit or 14-bit NEF data is preserved into 16-bit TIFF color channels. This matters for smooth gradients and for post-processing workflows such as focus stacking.
  • Compressed NEFs can take longer to convert than uncompressed NEFs.
  • The resulting TIFFs are uncompressed. They are large, but they avoid another decompression step when used in post-processing.

How to use the NEF converter

  1. Review the NEF Converter configuration in Settings.
  2. Go to the Image Browser, navigate to a folder, select one or more NEF thumbnails, and right-click.
  3. Select a conversion option and the conversion will begin.
  4. Monitor the conversion status and cancel if needed.
  5. Running the conversion again on the same NEFs will overwrite any previously generated TIFFs with the same output names.
  6. The generated TIFFs are saved in a /nef2tif subfolder under the folder that contains the original NEF. Extracted data is saved in a sibling /nefinfo subfolder. These folder names can be configured by the app, including Unicode names.
c:\images\mysamplenefs (where you select NEF thumbnails)
	c:\images\mysamplenefs\nef2tif (the generated TIFFs)
	c:\images\mysamplenefs\nefinfo (optional nef data)

What the settings do

  • Suffix: adds text after the underscore in the converted TIF file name.
  • Nef2Tif subfolder name: names the folder that receives the converted TIF files.
  • NefInfo subfolder name: names the folder that receives the extra Nikon info files.
  • Output profile: lets you choose the color profile used during conversion. The selected profile is embedded in the converted TIF, and you can browse for another .icm or .icc file if needed.

About Color Profiles

TL;DR: Use NKsRGB unless you have a perfect shot that needs to be printed or focus stacked.

  • The in-camera color profile setting only affects JPGs and camera-made TIFFs. It does not affect NEF to TIF conversion, which is why you choose an output profile here.
  • Choose the output profile based on how you plan to use the converted TIF.
  • If your post-processing apps, monitor, and printer are all color-managed, you can use sRGB, Adobe RGB, or ProPhoto RGB. That kind of workflow is best for important images that need very accurate color, especially if you are printing or focus stacking.
  • If you are not sure, use NKsRGB. It is the safe default, and the converted TIF is still 16-bit no matter which profile you choose.
  • Real-world example: a smooth blue sky gradient may look slightly different depending on the profile. A wider-gamut profile can preserve more subtle color steps for later editing or printing, while a smaller profile can be more limited. For most images NKsRGB is fine, but for a critical image with delicate color, a color-managed workflow can help preserve more of what matters.

File naming

  • Converted TIFFs always use the source file name plus an underscore and your suffix.
  • If the suffix is blank, the file name still ends with an underscore before the .tif extension.
  • Example: myphoto_conv.tif
  • Example: myphoto_.tif
  • The app can overwrite a previous converted TIFF with the same converted name.
  • The original NEF file is never changed.

Extra info output

  • When Extract info is on, the app writes extra companion files for the converted image.
  • Those files are grouped under a nefinfo folder beside the nef2tif output folder by default.
  • The extra files are meant for people who want to inspect the conversion details, not for normal viewing.

Canceling a conversion

  • Use the Cancel button to stop the current batch conversion.
  • Cancel stops the current run as soon as the converter can safely stop.
  • You can start a new conversion after the current one finishes or is canceled.

Super-user notes

  • The app uses Nikon's own conversion engine, so the output usually looks very close to the camera-made JPEG.
  • The converter works from the NEF data and Nikon camera settings recorded in the file.
  • This is not an image editor. It does not provide manual tone, sharpening, or color-tuning controls.
  • A 16-bit TIFF keeps more image data than a JPEG, which helps if you plan to edit or archive the converted file.
  • The batch converter processes one file at a time, which keeps progress and cancellation behavior predictable.
  • Unicode file names are supported, so NEF files and suffixes can use non-English text.
  • If a TIFF already exists with the same converted name, the app is allowed to overwrite that converted file.

Did you know?

  • A .NEF file is Nikon's RAW format, which means it keeps more of the original camera data than a JPEG.
  • Many NEF files contain an embedded preview image, so they can look correct in a file browser even before conversion.
  • Two photos from the same camera can produce different NEF output looks because the file records the camera settings used at capture time.
  • A NEF is usually a better choice than a JPEG if you want more room for later editing, especially for exposure and color recovery.
  • Nikon RAW files are designed to be interpreted by Nikon-aware software, and the app uses Nikon's official NEF conversion engine, the Nikon Imaging SDK, which is why its output can look much closer to the camera's own rendering than a third-party RAW converter.