NUT to M2TS Converter
FileFlip converts NUT to M2TS entirely inside your browser, using FFmpeg compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert a NUT file to M2TS?#
- Drop your NUT file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to M2TS and the conversion starts on its own. FileFlip downloads 30.8 MB of WebAssembly the first time and nothing after that, then runs FFmpeg on your own machine.
- Save the M2TS file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting NUT to M2TS lose quality?#
It depends on what is inside the file. NUT is a container rather than a codec, so whether the M2TS conversion copies the streams across untouched or re-encodes them is decided by the codecs that particular file happens to use.
Is it safe to convert NUT files online?#
Yes, because nothing is uploaded. FileFlip converts NUT files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What NUT to M2TS actually does to the file#
Converting NUT to M2TS runs on FFmpeg, downloads 30.8 MB of WebAssembly the first time and nothing after that, re-encodes or copies through depending on the codecs in the file, and drops encoded streams.
| Engine | FFmpeg |
|---|---|
| Conversion path | One step: NUT → M2TS |
| Downloaded to your browser | 30.8 MB, once, then cached by your browser |
| Quality | Decided by the codecs inside the file |
| You get back | One file |
| Where it runs | In a background worker, so the page stays responsive |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Encoded streams | Dropped | The target format has nowhere to put it. |
What is a NUT file?#
A NUT file is a general-purpose media container created inside the FFmpeg and MPlayer projects, built as a simple, open, patent-free alternative to AVI and similar formats, and able to wrap any codec those tools support.
NUT is worth using only inside an FFmpeg-based pipeline, such as a test harness or a tool chain that already standardises on it.
Convert NUT to MP4 or MKV for anything that needs to open outside FFmpeg or a player built on its libraries, since almost no other software recognises the container.
What is an M2TS file?#
An M2TS file holds a BDAV MPEG-2 transport stream, the timestamped variant of MPEG-TS that Blu-ray Disc authoring software writes into a disc's BDMV/STREAM folder.
Keep footage as M2TS while it's still part of a Blu-ray authoring or playback pipeline that expects that exact stream structure.
Convert M2TS to MP4 or MKV once the goal is normal playback or editing outside of Blu-ray software, since both drop the disc-specific overhead while keeping the same video and audio.
NUT to M2TS questions people ask#
What opens a NUT file?
ffplay and mpv both open NUT files directly, since both are built on FFmpeg's own libavformat library, which is where the NUT container comes from. Outside that ecosystem, support is essentially nonexistent.
Why would a file be in NUT instead of MP4 or MKV?
NUT usually turns up as the output of an FFmpeg-based tool or test pipeline rather than something a person chose deliberately, since it was designed as an open, patent-free container within the FFmpeg and MPlayer projects. Matroska ended up filling the same role for everyone else.
Is NUT related to Matroska or AVI?
NUT was designed around the same time as Matroska and for a similar reason, as a flexible, open alternative to AVI's limitations, but the two are independent formats with no shared structure. Matroska is the one that ended up widely adopted; NUT stayed inside the FFmpeg and MPlayer projects that built it.
What produces an M2TS file?
M2TS files come from Blu-ray Disc authoring software, from ripping or ejecting a Blu-ray's BDMV/STREAM folder, and from professional camcorders that record straight to the Blu-ray-compatible format. Any tool built around the Blu-ray Disc Association's BDAV structure writes this extension.