NUT to Y4M Converter
FileFlip converts NUT to Y4M 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 Y4M?#
- 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 Y4M 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 Y4M file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting NUT to Y4M lose quality?#
It depends on what is inside the file. NUT is a container rather than a codec, so whether the Y4M 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 Y4M actually does to the file#
Converting NUT to Y4M 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 → Y4M |
| 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 a Y4M file?#
A Y4M file holds YUV4MPEG2 data, raw uncompressed video frames in planar YCbCr with a short plain-text header, the format codec developers feed into encoders like x264, x265 and vpxenc so nothing but the codec under test touches the pixels.
Use Y4M when testing or comparing video encoders, where the point is to remove every other codec from the pipeline so the one under test is the only variable.
Convert Y4M to a compressed format like MP4 for anything other than encoder testing, since the raw size makes it impractical to store or share.
NUT to Y4M 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.
Why is a Y4M file so much bigger than the video it represents?
A Y4M file stores every pixel of every frame with no compression at all, unlike MP4 or MKV, which is exactly the point: encoder developers use it as clean, unaltered input so nothing but the codec being tested affects the result. A minute of 1080p footage can run to several gigabytes.