NEF to TS Converter

NEF to TS — Which Target Do You Actually Need?

NEF is Nikon's RAW photo format — the unprocessed sensor data straight off a Nikon DSLR or mirrorless body — and TS is the MPEG transport stream, the broadcast container defined in ISO/IEC 13818-1 that splits audio and video into 188-byte packets for error-resilient transmission. A still photo has no timeline and no sound, so putting one into a broadcast video container is a narrow, specialist ask: the output is a single motionless, silent frame held for a duration you set. If a playout system, IPTV encoder, or HLS-segment-era tool specifically wants a .ts slate, this page does that. For almost everyone else, NEF to JPG (a viewable picture) or NEF to MP4 (a clip that plays everywhere) is the right target — the comparison below shows why.

NEF vs TS — Side-by-side Comparison

When to Convert NEF to TS

• A broadcast or playout system needs a .ts slate — a DVB/ATSC playout chain, an IPTV encoder, or a master-control tool that wants a single Nikon frame held as a slate or test card.
• An HLS-segment-era pipeline expects .ts — older HTTP Live Streaming tooling segmented into transport-stream files, and some workflows still feed a still frame in that shape.
• A set-top or capture device reads only plain transport streams — embedded players that parse the standard 188-byte stream but not other containers.
• You need the still packetized, not just viewable — the rare case where the downstream tool wants the photo inside a transport stream rather than as an image.

When to Pick JPG or MP4 Instead

• You just want a shareable picture — NEF to JPG renders the RAW to a viewable, universally supported image and keeps the file small; the original .nef stays your editable master.
• You want a clip that plays everywhere — NEF to MP4 wraps the held frame in MP4, which plays natively on phones, browsers, and modern editors while a bare transport stream often does not.
• You need the full sensor resolution — a transport stream targets video frame sizes, so it cannot hold a 20-45 MP still at full size; export a full-resolution image with NEF to TIFF instead.
• You only have an AVCHD camcorder workflow — the broadcast TS this page makes is not the BDAV variant editors auto-detect; the comparison-twin CR2 to TS explains the 188-vs-192-byte split for RAW sources.

How to Convert NEF to TS

1. Upload Your NEF File: Drag and drop your .nef onto the page or click "+ Add Files" to browse from your computer. You can queue several Nikon photos at once.
2. Set Merge Strategy and Image Duration: Open Advanced Options. Use "Merge strategy" to pick "Merge images" (combine several photos into one TS) or "Video per image" (a separate file each), then set "Duration" to control how long the still shows — from a single frame up to 10 seconds per frame, with 5 seconds the default.
3. Set Background Color, Quality Preset, and Video Codec (Optional): Pick a "Background Color" (Black by default) to fill any letterbox bars, keep "Quality Preset" on "Very High (Recommended)", and under "Video Codec" the default is H.264 — the codec broadcast .ts files most commonly carry.
4. Convert and Download: Click "Convert" and download your TS file. No sign-up, no watermark.

For the nearest related moves see NEF to MP4 for universal playback or NEF to JPG for a plain picture.

Frequently Asked Questions

Should I really convert a Nikon NEF to TS, or to MP4 or JPG?

Almost always to MP4 or JPG. TS is a broadcast/streaming container, so it makes sense only inside a chain that specifically expects the standard 188-byte transport stream — a DVB/ATSC playout system, an IPTV encoder, an HLS-segment-era pipeline, or a set-top device that reads only plain .ts. For anything you intend to watch or share, NEF to JPG gives you a viewable picture and NEF to MP4 gives you a clip that plays on phones, browsers, and editors. Reach for TS only when a tool downstream refuses everything else.

Will the TS clip have any motion or sound?

No. The conversion renders one NEF photo and presents it as a static image for the duration you set — no panning, zoom, animation, or transition. It is also silent: a photo carries no audio, so an image-to-video conversion writes no audio track rather than padding with silence. Real broadcast TS streams carry AC-3, MP2, or AAC audio, so if you need sound you must lay a music or narration track over the file in an editor afterward. If you upload several photos and choose "Merge images," they play back to back, but each frame is still a held still.

Does the TS keep my Nikon photo's full resolution?

No. A transport stream targets video frame sizes, not print-resolution stills, so a 20-to-45-megapixel NEF is downscaled to a 1080p-class raster to fit. The TS cannot match the detail of the original photo. If pixel count matters, keep the .nef and export a full-resolution still with NEF to TIFF instead, or render to a viewable image with NEF to JPG. Because a motionless frame barely changes between samples, H.264 still compresses it heavily, so even a high-resolution Nikon photo held for a few seconds usually produces a small TS.

Which video codec does the TS output use?

H.264 by default. A transport stream is codec-agnostic by design, so a .ts can carry MPEG-2, H.264/AVC, or H.265/HEVC; this converter defaults to H.264, the most broadly compatible choice for transport-stream players and the codec HLS .ts segments historically used. In the "Video Codec" list under Advanced Options you can switch to MPEG-2 (the classic DVB/ATSC broadcast codec), H.265, MPEG-4, or DivX if a specific decoder needs them.

Do I lose the RAW editing latitude when I convert NEF to TS?

Yes. A NEF stores 12-bit or 14-bit sensor data and keeps white balance, hue, tone, and sharpening as editable instruction sets rather than baked into the pixels, as Nikon describes. To write a video frame the converter must demosaic and develop the RAW first — applying the current white balance, exposure, and Picture Control and flattening the result to ordinary 8-bit video pixels. Once that frame is inside the TS the latitude is gone, exactly as it would be in a JPEG. Keep your original .nef as the master and set the look in a RAW editor before converting.

Is this TS the same as the MTS my camcorder records?

No — they are close relatives but not identical. A plain .ts uses 188-byte packets as defined in ISO/IEC 13818-1 and is the broadcast/streaming variant, while a camcorder's .mts (AVCHD) wraps each packet in an extra 4-byte header for 192 bytes total, aimed at non-linear editors. The TS this page produces is the standard broadcast stream, so it will not auto-detect as AVCHD footage in camcorder software — which is exactly the point when a broadcast tool needs plain TS. For the RAW-source equivalent of this distinction, CR2 to TS covers the same 188-vs-192-byte split.

How are my files handled during conversion?

In our testing, a single full-resolution Nikon NEF held for 5 seconds at the "Very High" preset produced a TS only a couple of megabytes in size, because a motionless H.264 frame compresses heavily. Your file is uploaded over an encrypted connection, rendered and packaged into TS on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. If the resulting clip is too large to send, run it through the video compressor first.