CONVERT
Y4M → NUT
Tap to choose your fileDRAG. DROP. DONE.
Upload any file and our engines will handle format detection automatically.
Max 25 MB · Free plan · No signup required
Convert to:
Detecting available formats...
Optimize for
Leave empty to use original name. Extension added automatically.
Uploading...
Processing your file...
Fast, secure Y4M to NUT conversion. No registration required.
Here is the short version — Y4M is a video container, so playback depends on the codec inside as well as the wrapper itself. Hence the need for NUT. Repackaging a Y4M file into NUT is one of the fastest video jobs there is. When the codecs already match the target container specification, the bytes are literally copied across — no re-encoding, no quality drop, no long wait. Upload above and watch the progress bar usually fly. One more beat. Y4M is a video container, so playback depends on the codec inside as well as the wrapper itself. Receiving format: NUT is a video container, so playback depends on the codec inside as well as the wrapper itself.
YUV4MPEG2
Source formatYUV4MPEG2 (Y4M) is a simple uncompressed video format that stores raw YUV pixel data with a minimal header. It is widely used as an intermediate format for video processing and quality benchmarking where no compression artifacts are acceptable.
NUT Container
Target formatNUT is an open multimedia container format designed by MPlayer and FFmpeg developers as a simpler, more robust alternative to existing containers. It supports any codec and offers good error resilience with low overhead.
Why convert Y4M to NUT
NUT Container is better supported than YUV4MPEG2 across web uploads, social networks and consumer devices. Converting trades the niche advantages of Y4M for broad playback and fewer "file type not supported" messages. Stream copy (when codecs match) keeps the video bit-identical to the source.
HOW TO CONVERT
Y4M → NUT
Upload the Y4M
Drop your Y4M onto the uploader. Files up to 25 MB run on the free tier without registration; paid plans go up to 2 GB.
Stream-copy or re-encode
FFmpeg probes the codecs; if compatible, it stream-copies (no quality loss). Otherwise it transcodes at matching bitrate.
Download the NUT
Fetch the converted NUT as soon as it is ready. Both files auto-delete within two hours.
Common Use Cases
Share across platforms
Send NUT files to anyone without worrying about whether they have the right software for Y4M.
Embed in documents
Drop NUT output into Word, Google Docs, PowerPoint, Notion or a website without conversion warnings.
Optimize size
NUT often produces smaller files than Y4M for web, email and storage.
Archive & future-proof
Store in a widely-supported format that will still open on future operating systems without legacy plugins.
Y4M vs NUT — Strengths and limitations
What each format does best, and where it falls short.
Y4M Strengths
- Uncompressed raw YUV — codec benchmark truth.
- Dead-simple header.
- Universal codec development support.
Limitations
- Enormous file sizes.
- Development-only — not for consumption.
- No metadata beyond basic stream params.
NUT Strengths
- Technically efficient.
- Low overhead.
- FFmpeg-native support.
Limitations
- Tiny ecosystem.
- Overshadowed by MKV.
- Rarely used in production.
Y4M vs NUT — Technical specifications
Side-by-side comparison of the technical details.
Y4M
- MIME type
- video/x-yuv4mpeg2
- Extension
- .y4m
- Pixel format
- YUV 4:2:0, 4:2:2, 4:4:4
- Header
- ASCII single line
NUT
- MIME type
- video/x-nut
- Extension
- .nut
- Design
- FFmpeg/MPlayer collaborative spec
- Encoding
- Variable-length integers
| Specification | Y4M | NUT |
|---|---|---|
| MIME type | video/x-yuv4mpeg2 | video/x-nut |
| Extension | .y4m | .nut |
| Pixel format | YUV 4:2:0, 4:2:2, 4:4:4 | — |
| Header | ASCII single line | — |
| Design | — | FFmpeg/MPlayer collaborative spec |
| Encoding | — | Variable-length integers |
Y4M vs NUT — Typical file sizes
Approximate file sizes for common scenarios.
Y4M
- 10 sec 1080p Y4M ~600 MB
- 1 min 4K Y4M ~14 GB
NUT
- 10-min H.264 clip 80-200 MB
Quality & Compatibility
Stream-copy is bit-perfect: when the codecs inside Y4M match what NUT can carry, the frames are copied across without re-encoding and the output is visually identical to the source. When transcoding is required, we target CRF 20–23 H.264 — visually transparent for most content — and keep audio bitrate at 192 kbps AAC.
Tips for Best Results
- Stream-copy beats re-encoding by orders of magnitude — check if your Y4M already uses NUT-compatible codecs before picking Advanced settings.
- For social uploads, 1080p at 30 fps strikes the best quality-to-size ratio; 4K is often downscaled server-side anyway.
- Keep the Y4M if you plan further editing — transcoded NUT is fine for final delivery but not for intermediate edits.
Frequently Asked Questions
Only when it has to. If the codecs inside Y4M (usually H.264 or H.265 for video, AAC for audio) are accepted by NUT, we stream-copy — the bytes are repackaged into the new container with zero re-encoding and no quality loss. When the source uses a codec the target does not support, we transcode at a matching bitrate to keep the visual quality close to the original.
With stream copy, expect the job to finish in seconds to tens of seconds regardless of video length — the work is mostly rewriting the container. Transcoding is slower (roughly real-time: a ten-minute clip takes about ten minutes) because every frame must be decoded and re-encoded. The progress bar shows which mode applies.
Yes. Resolution, frame rate, colour space and bit depth are preserved by default; stream copy is literally bit-identical on these parameters. If you explicitly pick a lower bitrate or a different codec in Advanced, the output is rebuilt to those settings, but the default is always "match the source".
RELATED CONVERSIONS
Other popular pairs involving Y4M or NUT
More from Y4M
More ways to reach NUT
Related comparisons
See these formats side by side to understand which fits your use case best.
Secure & Private Conversion
Your files are encrypted during transfer, processed in isolated containers, and automatically deleted within 60 minutes. We never read, share, or store your data.