Reset to defaults
Need help?Convert NEF to TIF Online
A NEF is Nikon's digital negative — 12-bit or 14-bit sensor data with white balance, hue, tone and sharpening "retained as instruction sets" instead of baked into pixels (Nikon USA on NEF). TIF is the flat, finished version of that shot: a TIFF file, readable by essentially every editor, layout application, print shop and archive since Aldus published TIFF Revision 6.0 on June 3, 1992.
Two facts about this specific converter decide whether you get a good TIF or a bad one, and both catch people out: the Compression Type box opens on JPEG, which is lossy, and two of the entries in that list cannot encode a colour photograph at all. Read the compression table below before you convert.
How to Convert NEF to TIF
- Upload Your NEF File: Drag and drop your
.neffiles onto the page or click "+ Add Files" to browse. Several Nikon raw files can be queued and converted with one set of settings. - Change the Compression Type to LZW or DEFLATE: Open Advanced Options. The Compression Type selector starts on JPEG, which re-encodes your photo lossily inside the TIFF wrapper. Switch it to LZW for the widest compatibility, DEFLATE or ZSTD for smaller lossless files, or NONE if a downstream tool insists on uncompressed data.
- Set the Image Resolution and File Extension: Leave Image resolution on "Keep original" for the full frame, or downscale with "Resolution Percentage", a preset height, "Width", "Height" or "Width x Height". Under File extension, choose
.tifor.tiff— the bytes are identical, only the filename differs. - Convert and Download: Click "Convert" and save the file. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.
Compression Type: What Each Entry Actually Does Here
| Entry in the list | Lossless? | Behaviour with a colour photo | Verdict |
|---|---|---|---|
| JPEG — the default | No | Re-encodes the picture with JPEG inside the TIFF | Works, but defeats the point of choosing TIFF |
| LOSSY | No | Identical to JPEG — the two entries map to the same encoder setting | Duplicate; ignore it |
| LZW | Yes | Classic TIFF 6.0 lossless coding, universally readable | Best default for a photo archive |
| DEFLATE | Yes | Zlib coding; usually a little smaller than LZW | Good when file size matters |
| ZSTD | Yes | Modern lossless coding, smallest of the three in our checks | Good if your reader supports it |
| PACKBITS | Yes | Simple run-length scheme; TIFF 6.0 itself warns it "is often ineffective on continuous tone images" | Barely compresses a photograph |
| NONE | Yes | Raw uncompressed pixel data | Only when a tool demands it |
| WebP | No | Lossy WebP inside the TIFF wrapper | Niche; poor reader support |
| CCITT Fax 4 | n/a | TIFF 6.0 defines the CCITT encodings as bilevel — 1 bit per sample | Do not use on a photo |
| JP2K (JPEG 2000) | n/a | Not implemented by the TIFF encoder in this pipeline | Do not use |
CCITT Fax 4 and JP2K do not report a clean error — they write a file that exists but has no usable image in it. Stay on LZW, DEFLATE, ZSTD or NONE for a photograph.
What the Quality Preset Does on a TIF
The Quality Preset only feeds the JPEG and WebP paths. If you pick LZW, DEFLATE, ZSTD, PACKBITS or NONE, the encoding is mathematically lossless and the preset changes nothing about the pixel data — so leaving it on "Very High (Recommended)" is fine. It matters only if you deliberately keep the JPEG compression type, in which case it sets the JPEG quality ceiling.
Two other controls are live on this page: Image resolution, where "Keep original" is preselected and the preset list sets height only (width follows the source aspect ratio), and Specific file size, which lets you name a byte target and optionally allow "Auto Scale" to reduce resolution when compression alone cannot reach it. There is no DPI or bit-depth control on this page.
NEF vs TIF: What Carries Over
| Property | NEF (Nikon Electronic Format) | TIF (this output) |
|---|---|---|
| Type | Camera raw sensor data | Rendered raster image |
| Structure | TIFF-style container with Nikon-specific tags | TIFF 6.0 and its later compression extensions |
| Bit depth | 12-bit or 14-bit per channel | 8 bits per channel |
| White balance / tone | Editable instruction sets | Fixed at render time |
| Compression | Uncompressed or lossless-compressed raw | Your choice of the table above |
| Layers | None | TIFF supports multi-page; this converter writes a single page |
| Software support | Nikon NX Studio, Lightroom, Camera Raw, RawTherapee | Near-universal, including print and archival workflows |
| Best for | The re-editable master | Delivery, print, long-term storage of a finished render |
Frequently Asked Questions
Is .tif the same thing as .tiff?
Yes — same format, same bytes, different filename length. "TIF" is the three-letter spelling that survived from MS-DOS filename limits, and some older or fussier software still expects exactly three characters. The File extension control on this page lets you pick either, so choose whichever your downstream tool prefers. If you specifically want the four-letter name, NEF to TIFF is the same conversion under the other spelling.
Why is the default compression lossy, and what should I switch it to?
The Compression Type selector opens on JPEG, which compresses the picture the same way a .jpg would before wrapping it in a TIFF container. That is a reasonable default for a small preview file, but it is the opposite of why most people choose TIFF. For an archive or an editing master, switch it to LZW — the lossless scheme TIFF 6.0 defines in its own section 13 and the one virtually every TIFF reader supports. DEFLATE and ZSTD are also lossless and usually produce smaller files if your reader handles them.
What is the difference between the "LOSSY" and "JPEG" entries in the compression list?
Nothing. Both map to the same JPEG-in-TIFF encoder setting; "LOSSY" is an alias that was never removed from the list. Selecting one or the other produces the same file, so treat the list as eight real choices rather than ten.
Do I get a 16-bit TIFF from my 14-bit NEF?
No. TIFF as a format can carry 16 bits per channel, but this converter renders to 8 bits per channel, so the extra tonal range Nikon describes — "12-bit or 14-bit data" depending on the camera — is compressed down during the develop step. An 8-bit lossless TIF is a perfectly good delivery and print file, but it is not a substitute for the raw file when you plan aggressive shadow-lifting or highlight recovery. For genuine 16-bit output, develop the NEF in NX Studio, Lightroom, Capture One or RawTherapee and export from there.
Why do CCITT Fax 4 and JP2K produce a file I cannot open?
Because neither can represent a colour photograph in this pipeline. TIFF 6.0 defines the CCITT Group 3 and Group 4 encodings as bilevel schemes — one bit per sample, built for fax and scanned line art — so a three-channel photo has nothing valid to encode. JPEG 2000 in TIFF is a later extension that the encoder in this pipeline does not implement. We put a colour test image through every entry in the list using the same encoder the converter calls: LZW, DEFLATE, ZSTD, PACKBITS, NONE, JPEG and WebP all produced readable images, while CCITT Fax 4 and JP2K wrote small files whose pixel data reads back as empty. Treat those two as unusable here rather than as slow-but-working options.
Does the Quality Preset change anything if I choose LZW?
No. Lossless compression types have no quality dial to turn, so the preset is only consumed by the JPEG and WebP paths. Leave it alone when you are encoding losslessly. If you want a smaller lossless TIF, reduce the pixel dimensions under Image resolution or switch from LZW to DEFLATE or ZSTD instead.
Why is the TIF so much larger than the NEF?
A raw file records one compressed brightness sample per photosite behind a colour filter array; a TIF records three finished colour channels for every pixel. At 8 bits per channel a 24-megapixel frame is roughly 72 MB of pixel data before compression, and lossless schemes save comparatively little on photographic texture, so a lossless TIF landing well above the NEF's size is normal. If you need something small and shareable, NEF to JPG is the right target instead.
Does my Nikon EXIF and lens data survive?
TIFF was designed to carry tag metadata, so standard EXIF fields such as shutter speed, aperture, ISO, focal length and lens model generally come through. Nikon's proprietary MakerNote tags — Picture Control, Active D-Lighting, in-camera retouch history and the rest — are not part of the standard TIFF or EXIF tag set, so do not count on those surviving. Keep the .nef if that shooting metadata matters to your catalogue.
Should I keep the original NEF after converting?
Yes, always. Even a lossless TIF is a rendered interpretation: white balance, tone curve and sharpening are fixed the moment the raw is developed, and the recoverable highlight and shadow information in the digital negative is gone once the image is demosaiced and flattened to 8 bits. Archive the NEF as your master and treat the TIF as a high-quality working or delivery copy.
How are my raw files handled during conversion?
Your NEF is uploaded over an encrypted connection, developed and encoded on our servers, and deleted automatically after a few hours. Nothing is shared or made public, and there is no sign-up or watermark. With 40-plus-megapixel raw files the practical constraint is upload size and time rather than the conversion itself.