Initializing... drag & drop files here
Supports: NEF
NEF is Nikon's RAW photo — the unprocessed 12-bit or 14-bit sensor data a Nikon DSLR or mirrorless body writes before white balance, exposure, or a Picture Control look is baked in — and M2TS is the AVCHD transport-stream file as it is spelled on a computer or inside a Blu-ray disc structure. This converter renders one Nikon photo and packages it as that stream, for the narrow case of dropping a still into a Blu-ray-authoring project or an AVCHD-era timeline that expects the .m2ts extension. The honest catch up front: .m2ts and .mts hold the same H.264 transport stream — .MTS is the 8.3 short name a camcorder writes to its card, .m2ts is the long-filename form software uses after import — so NEF to MTS and NEF to AVCHD produce the identical recording under their own extensions. Pick whichever spelling your software is looking for; if you only want a viewable picture or a clip that plays anywhere, skip ahead to the last FAQ.
| Property | M2TS | MTS |
|---|---|---|
| Full name | BDAV MPEG-2 Transport Stream | AVCHD camcorder stream (same data) |
| Where you see it | On a computer after import, and in Blu-ray disc structure | On the camcorder's SD card, written in-camera |
| Filename form | Long-filename .m2ts |
8.3 short name .MTS |
| Container | BDAV transport stream (188-byte TS packet + 4-byte timestamp header = 192-byte packets) | Same BDAV transport stream |
| Video codec | H.264 / MPEG-4 AVC | H.264 / MPEG-4 AVC |
| Audio codec | Dolby AC-3 or linear PCM | Dolby AC-3 or linear PCM |
| Disc location | BDMV/STREAM/ on a Blu-ray; AVCHD/BDMV/STREAM/ on AVCHD media |
PRIVATE/AVCHD/BDMV/STREAM/ on the card |
| Typically associated with | Blu-ray authoring, computer playback/editing | Sony and Panasonic AVCHD camcorders (since 2006) |
| Best for | Importing into disc-authoring or editing software that wants .m2ts |
The raw recording straight off a camcorder |
The two extensions describe the same H.264-in-transport-stream payload — the difference is naming convention and where the file lives, not the encoded video. You can rename one to the other and it still plays; a .m2ts is simply what most editors and Blu-ray authoring tools display once an .MTS recording has been copied off the card.
.m2ts clips into its timeline..m2ts and refuses to recognize a .mts file.BDMV/STREAM/ layout and want the new still to match that extension..MTS — use NEF to MTS so the extension matches the rest of the card..avchd/.mts spelling — use NEF to AVCHD..nef onto the page or click "+ Add Files" to browse. You can queue several Nikon photos at once.For this conversion, effectively yes. Both extensions wrap the same H.264 video in the same BDAV MPEG-2 transport stream — .MTS is the 8.3 short name a camcorder writes to its card, and .m2ts is the long-filename form software shows after the clip is imported or placed in a Blu-ray disc structure. The encoded video is byte-for-byte the same recording; you can even rename one to the other and it still plays. Only the filename convention and the typical home of the file differ. This page outputs the .m2ts spelling some Blu-ray-authoring and editing tools expect, while NEF to MTS writes the identical stream as .mts.
No on both counts. The converter renders your single NEF to one still frame and holds that motionless frame on screen for the duration you set — there is no pan, zoom, or transition. It is also silent: a photo carries no audio, so there is nothing to encode, even though the M2TS container itself can carry Dolby AC-3 or linear PCM. If you upload several photos and choose "Merge images," they play back to back, each shown for its set duration — a sequence of stills, not a cross-faded slideshow. Add narration or music on your editing timeline after import.
Yes. A NEF stores 12-bit or 14-bit sensor data with white balance, tone and sharpening kept as editable instruction sets rather than baked into the pixels, as Nikon describes. To put the photo into a transport stream the converter must develop it first — demosaicing the sensor data and baking in white balance, exposure and the current Picture Control, then flattening to ordinary 8-bit video pixels — because a video stream has no concept of undeveloped RAW. Once that rendered frame is inside the M2TS the latitude is gone, exactly as in a JPEG. Develop the RAW in a dedicated editor first if you want that control, and keep the original .nef as your master.
Lower than the photo, in practice. Recent Nikon D-series and Z-series bodies capture roughly 20 to 45 megapixels, far more than any HD video frame holds, so AVCHD/M2TS targets 1080p-class dimensions — choosing a 1920×1080 preset under "Video resolution" downscales the rendered image to fit. AVCHD was built around HD recording, so 1920×1080 is the natural target and detail beyond it is discarded — normal for putting a high-resolution photo into video. If preserving every pixel matters, keep the still as an image with NEF to TIFF instead of wrapping it in a video stream.
No. This is a file converter — it outputs a single rendered .m2ts stream, not the full BDMV/STREAM/ directory tree with the playlist (.mpls) and clip-information (.clpi) files a Blu-ray player or authoring tool reads. Building that structure is a disc-authoring task, much as a lone .m2ts is not a finished disc and a single .vob is not a finished DVD. Import the rendered clip into your Blu-ray-authoring or editing project, let that software lay it into the disc layout, and author from there. If your tool's dedicated AVCHD/Blu-ray importer doesn't see the loose file, use its generic file import instead.
In our testing, a single full-resolution Nikon NEF held for 5 seconds at the "Very High" preset produced an M2TS 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 the M2TS on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public.
For almost everyone, M2TS is the wrong target. If you only want a viewable, shareable picture, NEF to JPG gives you a far smaller file that opens everywhere, and you keep the original .nef as your editable master. If you need a video clip for a modern editor, web upload, or phone playback, NEF to MP4 carries the same H.264 in a container that plays natively almost anywhere, while M2TS does not. Reach for M2TS only when a specific Blu-ray-authoring or AVCHD-era workflow requires that exact container and extension.