Initializing... drag & drop files here
Supports: MP4, M4V
This walks through re-encoding an .m4v video — Apple's MP4 variant, the format iTunes movies, Apple TV episodes, and Mac/iPhone exports use — into AV1, the royalty-free codec from the Alliance for Open Media. Be clear about the trade-off up front: M4V already carries efficient H.264, so moving to AV1 buys you a smaller file at the same quality (or better quality at the same size), but it is a slow, lossy-to-lossy re-encode that plays in fewer places than the universal H.264/MP4 it came from. Convert to AV1 when storage efficiency or a modern streaming pipeline is the goal — not when you want maximum compatibility. If you just want a widely playable file, M4V to MP4 is nearly a rename for DRM-free M4V, and that is what most people who land here actually need.
.m4v file onto the page, or click "+ Add Files" to browse. Batch upload is supported, so you can queue several clips and encode them with the same settings.M4V holds H.264/AVC video; AV1 (AOMedia Video 1, bitstream spec released 28 March 2018) is a newer, more efficient codec. So M4V to AV1 is always a full re-encode — the H.264 picture is decoded and re-compressed into AV1 from scratch. The upside is real: in independent testing AV1 reached roughly 46% higher compression than x264 (H.264) at matched quality, which is why streamers adopted it. The honest limits are just as real:
To get a clean result, match the method to the goal:
Your M4V holds H.264. This is what actually changes when you move it to AV1:
| Property | H.264 / AVC (inside the M4V) | AV1 |
|---|---|---|
| Published by | ITU-T and ISO/IEC jointly, first approved in 2003 | Alliance for Open Media, bitstream v1.0.0 released 28 March 2018 |
| Licensing | Covered by patent pools with royalty terms | Royalty-free by design |
| Compression efficiency | The long-standing baseline | Substantially better at matched quality — see the walk-through above |
| Encoding speed | Fast; real-time on ordinary hardware | Much slower, because the encoder searches a far larger space |
| Decoding load | Trivial for anything made this century | Heavier in software; smooth playback benefits from hardware support |
| Hardware decode | Effectively universal | GPUs, TVs, and phones from around 2020-2022 onward; Apple silicon from the M3 / A17 Pro generation |
| Usual containers | MP4, M4V, MKV | MP4, MKV, WebM |
| Best for | Files that must simply play, everywhere, today | Storage efficiency, modern streaming pipelines, long-term archives |
Advanced Options offers several ways to control the encode, and they answer different questions:
| Method | What you are setting | Use it when |
|---|---|---|
| Quality Preset | A named quality level, defaulting to "Very High (Recommended)" | You want a good result without thinking about numbers |
| Constant Quality | A quality target the encoder holds throughout, spending whatever bitrate each scene needs; a lower number means higher quality | Archiving, or any time visual consistency matters more than a predictable file size |
| Constraint Quality | A quality target with a ceiling on how much bitrate it may spend | You want Constant Quality's look but cannot let busy scenes balloon the file |
| Constant Bitrate | A fixed rate for every second of the video | A delivery pipeline or device specifies an exact bitrate |
| Variable Bitrate | An average rate, letting the encoder move bits toward harder scenes | You have a rough size in mind but still want quality where it counts |
| Specific file size | A hard cap in MB, with the encoder working backwards to hit it | You have an upload limit to fit under |
For most people the honest ranking is: Constant Quality for archival, Specific file size when something imposes a limit, and the default Quality Preset for everything else.
If the M4V is a DRM-protected iTunes purchase, corrupted, or only partially downloaded, the video stream will not decode cleanly and the conversion fails — there is no software workaround for FairPlay encryption. And if your real goal is a file that plays everywhere rather than the smallest possible size, AV1 is the wrong target: H.264 in an MP4/M4V container plays on virtually everything modern, while AV1 still needs a recent decoder. Use M4V to MP4 for universal playback, Compress M4V to shrink the file while keeping H.264, or the reverse AV1 to M4V if you are bringing AV1 footage into the Apple ecosystem instead.
No. Movies and TV shows purchased or rented from the iTunes Store are often wrapped in Apple's FairPlay copy protection, which restricts playback to devices authorized with the purchasing Apple account. A FairPlay-protected M4V cannot be decoded by a converter, so the conversion will fail. Only DRM-free M4V files — your own screen recordings, exports, camera footage, or downloads that were never encrypted — can be converted to AV1.
No — a re-encode can only preserve or lose detail, never add it. M4V is already lossy H.264, and AV1 is also lossy, so the best AV1 can do is hold onto what H.264 kept while storing it more efficiently. The benefit is size: at the same perceptual quality the AV1 file is smaller, or at the same size it looks a bit better. For the cleanest result, use Constant Quality at a high-quality CRF setting rather than a low hard bitrate. In our testing, a 1080p H.264 M4V at 8 Mbps re-encoded to AV1 at visually matched quality landed around 45-55% smaller, while a 2 Mbps web-grade source shrank far less.
AV1 needs a recent decoder. On the desktop, Chrome 70+, Firefox 67+, and Edge play it in software, and VLC 3.0.5+ uses the dav1d decoder across platforms. Hardware decoding is built into most TVs and GPUs from 2022 onward, Pixel 7+ and recent Snapdragon phones, and Apple silicon from the M3 / A17 Pro generation forward. Older devices — including most pre-2022 Apple hardware — cannot decode AV1 at all, which is the main reason to keep H.264 when broad compatibility matters.
.av1 extension, and will it play?AV1 is a video codec, not a container. AV1 video is normally shipped inside a container — MP4 (ISO base media file format) or MKV are the standardized choices, with WebM common on the web. The output here packages the AV1 stream in a Matroska container but names the file .av1 after the codec — VLC, mpv, and other FFmpeg-based players open it as-is, and renaming it to .mkv (same bytes) satisfies players that judge files by extension.
It depends on where the file will play. The default Audio Codec for this conversion is Opus, which is royalty-free and pairs naturally with AV1 at smaller sizes. But Opus decodes in fewer players than AAC — notably some older and Apple-ecosystem players. If you need the result to play on iOS, Apple TV, or older media players, switch Audio Codec to AAC. Either choice re-encodes the audio, so pick a sensible bitrate (128-256 kbps for music, 96-128 for voice).
They solve the same problem from opposite directions. HEVC is the older of the two and has a decade-long head start in silicon, so it decodes in hardware on a huge installed base — Apple devices going back years, most 4K televisions, and essentially every recent GPU. Its drawback is licensing: HEVC is covered by multiple patent pools, which is precisely the friction that led the Alliance for Open Media to build AV1 as a royalty-free alternative. AV1 compresses at least as efficiently, is the codec the large streaming platforms have been standardising on, and is decoded by current versions of Chrome, Firefox, and Edge in software — but hardware decode only reaches devices from roughly 2020 onward. So: choose HEVC when the file has to play on existing consumer hardware, especially older Apple gear, and go to M4V to HEVC instead. Choose AV1 when you care about royalty-free delivery, browser playback, or a long-lived archive.
AV1 earns its compression by evaluating far more coding possibilities per frame than H.264 does, and that search is what costs the time — it is inherent to the codec, not a limitation of any particular tool. Three things genuinely help. First, trim before you encode: use Trim with a Time Range so the encoder only works on the seconds you actually need, rather than encoding a whole file and cutting afterwards. Second, drop the resolution if the destination does not need full size — encoding time scales with pixel count, so a 720p output finishes far sooner than the same clip at 4K. Third, do not upscale; enlarging the frame adds pixels the source never had and makes an already slow encode slower for no visual benefit. If none of that is acceptable and you simply need the job done quickly, H.264 in an MP4 encodes in a fraction of the time.
Your M4V is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion — no sign-up, no watermark, never shared or made public.