NEF to 3GP Converter

NEF to 3GP: What This Tutorial Covers

A .nef is a single Nikon raw photograph. A .3gp is a mobile video container from the GSM/UMTS era. So this conversion has two halves that are worth understanding separately: the raw file is first developed into a viewable picture, and that picture is then encoded as a short silent clip. Most of the ways this goes wrong happen in the second half, and almost all of them come down to one setting.

This walk-through takes you through the four steps, then goes deep on the codec choice — because picking H.263 on a Nikon still will silently distort your photograph, and the quality slider means something completely different depending on which codec is selected. If you only wanted a photo you can look at, stop here and use NEF to JPG instead.

How to Convert NEF to 3GP

1. Upload Your NEF File: Drag the .nef onto the page or click "+ Add Files". NEF is one of the two raw formats with a dedicated preview path, so a thumbnail of the shot normally appears before you convert. Files upload over an encrypted connection and are processed on our servers.
2. Pick the Video Codec: Under Advanced Options, Video Codec offers H.264 (selected by default), H.263, MPEG-4 and Xvid. Leave it on H.264 unless the receiving device predates it.
3. Set Image Duration, Merge strategy and Background Color: Image Duration holds the still on screen and defaults to 5 seconds per frame; Merge strategy defaults to Merge images so a batch becomes one slideshow; Background Color defaults to White and fills any letterbox area a resize creates.
4. Choose a Quality Mode and Convert: File Compression opens on Quality Preset, with Constant Quality and Constraint Quality as the alternatives — no bitrate or file-size modes render for an image source. Leave Video resolution on Keep original, click Convert, and download. No sign-up, no watermark; files are deleted automatically after a few hours.

Walk-through: Choosing a Codec Without Wrecking the Frame

The Video Codec dropdown looks like a list of four interchangeable options. It is not. Two of them change what the rest of the panel does, and one of them changes the shape of your photograph.

• If the destination is anything from the last fifteen years, keep H.264. It is the default, it is legal in 3GP under TS 26.244, and it is the only choice on this page where Quality Preset behaves the way its name implies.
• If you pick H.263, expect your picture to be resized without asking. H.263 only permits a fixed list of picture sizes, and our encoder snaps to the largest legal one that fits inside the source: 128×96, 176×144, 352×288, 704×576 or 1408×1152. That snap overrides your Video resolution selection and does not preserve aspect ratio. Every legal size is 4:3; Nikon DX and FX stills are 3:2. The result is a vertically squashed photograph.
• If you pick MPEG-4 or Xvid, ignore Quality Preset — it does nothing here. The preset works by scaling the source bitrate, and a still photograph has no source bitrate. Use Constant Quality or Constraint Quality instead.
• On H.263, MPEG-4 and Xvid, the Constant Quality slider is a quantizer, not a CRF. The value is emitted as a 1–31 quantizer where lower means better, but the control opens at a number inherited from H.264's 16–51 CRF scale, which lands near the bad end of a 1–31 range. It genuinely works — drag it down to roughly 3–6 and the picture sharpens up immediately.

The practical rule: use H.264 and Quality Preset, or use a qscale codec and Constant Quality with a low number. The combination that produces disappointing output is a qscale codec left on the defaults.

Common Errors and How to Fix Them

• "The photo is squashed vertically." H.263's size snap, described above. Letterbox to 4:3 before uploading, set Width x Height to one of the legal sizes, or switch to H.264.
• "The output is soft and blocky even at the highest preset." You are on MPEG-4 or Xvid, where Quality Preset is inert on an image source. Switch to Constant Quality and set the value low.
• "The clip is silent." It is meant to be. An image source always produces a silent clip; the audio controls do not render on this page and no audio track is written.
• "There is a white band around my picture." A resize that changed the aspect ratio letterboxed the frame, and image sources fill that area with the Background Color, which defaults to White. Set it to Black, or resize to a matching aspect ratio.
• "My 45-megapixel file came out much smaller than the original." Every image is normalised and capped at 4096 px on the long edge before encoding. For a 3GP target that is far above anything the container is used for anyway.
• "The colours look flatter than in Nikon's software." That is the raw development step. A NEF holds no baked-in rendering, and a general-purpose converter cannot apply the camera's Picture Control profile.

When This Doesn't Work

If the receiving device is a genuinely old handset, the constraint is not the container but the decoder: many pre-smartphone devices only handle H.263 or MPEG-4 Simple Profile at QCIF or CIF sizes, and the size snap that ruins a 3:2 photograph is the format telling you it was never meant to carry one. In that case, crop or pad the photograph to 4:3 in an image editor first so you control the framing, then convert. If the device turns out to accept modern files after all, NEF to MP4 gives you a far more capable container for the same silent-still workflow. And if what you actually need is a moving image that plays inline anywhere without a video player, NEF to GIF is the better route.

NEF Source vs 3GP Output

Which Codec Should You Pick?

Frequently Asked Questions

Why does my Nikon photograph come out distorted in H.263 but fine in H.264?

Because H.263 does not allow arbitrary picture sizes. The codec defines a fixed set — 128×96, 176×144, 352×288, 704×576, 1408×1152 — and our encoder picks the largest one that fits inside your image, overriding whatever you selected under Video resolution. All of those sizes are 4:3, and Nikon's DX and FX sensors produce 3:2 frames, so the picture is squeezed vertically to fit the box. Raw ffmpeg would reject the encode instead of distorting it; our validation layer accepts it and resizes. H.264 has no such constraint and keeps your frame as it is.

Is 3GP different from 3G2, and does it matter for a photo?

Barely, for this use case. 3GP is 3GPP's container for GSM and UMTS networks (TS 26.244); 3G2 is 3GPP2's for CDMA2000 networks (C.S0050-B). Both sit on the ISO base media file format and both permit H.263, MPEG-4 Part 2 and H.264 video. The real divergence is audio — 3GP carries the AMR family plus AAC-LC and HE-AAC, while 3G2 carries the CDMA voice codecs — and since a still-image conversion produces no audio at all, that difference never surfaces here. Use whichever extension the receiving system asks for by name.

Why is the clip silent, and can I add music?

An image source has no audio to carry, so the pipeline writes a video-only file and the audio controls are not shown on this page. There is no preselected audio codec here at all. If you want a soundtrack under the still, the sequence is to produce the clip here and then mux audio onto it in a video editor, or to build the whole thing in a slideshow application. Adding audio is not something a single-file image-to-video conversion can do.

How long is the clip, and can I make a slideshow from several NEFs?

One image lasts as long as Image Duration, which defaults to 5 seconds. Upload several NEFs with Merge strategy on Merge images and they become a single clip in filename order, each held for that duration — a hundred photographs at the default is an eight-minute file. Switch to Video per image for one clip per photograph instead. Note that the encode runs at 1 fps, so each picture is a single long-held frame rather than a smoothly played sequence; that is the correct behaviour for stills and the reason the output stays small.

What does the raw development step actually change about my image?

Everything that makes a raw file a photograph. A NEF stores 12- or 14-bit mosaiced sensor readings with no display rendering applied; producing a viewable image requires demosaicing the colour filter array, applying a white balance, running a tone curve over the linear sensor response, and mapping the result into a display colour space. Different converters make different choices at every one of those steps, which is why the output can look flatter or cooler than the version Nikon's own software shows you — that one applies the Picture Control profile set on the camera, which a general-purpose converter does not have. This is ordinary raw development and is not the same as HDR tone-mapping, which this pipeline does not do.

Why is there a white border around my picture?

Because a resize changed the aspect ratio and the empty area was filled with the Background Color, which defaults to White for image sources. If you would rather have black bars — the convention for video — change that dropdown before converting. The colour also fills any area a transparent source would have left empty, though that never applies to NEF, which has no alpha channel.

Does the 4096-pixel cap mean I lose detail from a high-megapixel body?

For this target, no meaningfully. Every image is normalised to PNG and capped at 4096 px on the long edge before encoding, so a 45-megapixel Z-series file is downscaled — but 3GP is a legacy mobile format whose practical ceiling is far lower, and H.263 in particular tops out at 1408×1152. The cap only becomes worth thinking about if you are using an image-to-video conversion to produce a high-resolution master, in which case NEF to MP4 at a modern resolution is the sensible target, and the cap still applies there.

How are my raw files handled and how long are they kept?

Your .nef uploads over an encrypted connection, is developed and encoded on our servers, and is deleted automatically after a few hours. There is no sign-up, no watermark on the output, and files are never shared or made public. The one practical thing to plan for is upload time: raw files run roughly two to six times the size of a JPEG of the same shot, so a full card's worth takes a while even on a fast connection. If you are converting a batch, uploading them in groups is usually less frustrating than one very long transfer.