Initializing... drag & drop files here
Supports: MP4, M4V
.m4v (Apple's MP4 variant). Batch is supported — drop in several MP4s and each one converts in parallel.MP4 (ISO/IEC 14496-14, standardized in 2003 and derived from Apple's QuickTime File Format) is the closest thing video has to a universal container. It plays on Windows, macOS, iOS, Android, every modern browser, smart TVs, and game consoles, which is exactly why most cameras and phones record to it and why most people never need to leave it. But a container is just a wrapper: MP4 holds codecs (usually H.264 or H.265 video with AAC audio), and the moment a specific app, editor, or platform wants a different wrapper or a different codec, the universal file becomes the wrong file. Converting re-wraps or re-encodes those streams into a combination the target speaks natively. Common reasons people convert away from MP4:
<video> embed, WebM cuts bandwidth — though Safari only added AV1 decoding (partial) in version 17, so many sites still ship an MP4 fallback alongside the WebM.The single most useful thing to understand about video files is that the file extension names the container, not the codec. MP4, MOV, MKV, and WebM are containers — they define how the video stream, audio stream, subtitles, and metadata are packed together. H.264, H.265, VP9, and AV1 are codecs — they define how each frame is compressed. A .mp4 and a .mkv can hold the exact same H.264 video bytes; only the wrapper differs.
This matters because it determines whether a conversion is lossless or not. When the source and target containers can both hold the codec already inside your MP4 — for example MP4 to MOV, where both happily carry H.264 + AAC — xconvert performs a container remux: the compressed streams are copied byte-for-byte into the new wrapper with no re-encoding and zero generational loss. This is the same -c copy operation FFmpeg performs, and it's near-instant. When the codec has to change — MP4's H.264 into WebM's VP9, or an H.264 video into a GIF's palette frames — the video is genuinely re-encoded, which takes longer and introduces some loss. Setting Constant Quality (CRF) to 18-20 keeps that loss invisible in side-by-side viewing.
| Target container | Standard / Origin | Native playback | Typical codecs | Best for |
|---|---|---|---|---|
| MOV | Apple QuickTime File Format (1991, opened 2001) | macOS, iOS, QuickTime, VLC | H.264, HEVC, ProRes, AAC | Final Cut, ProRes intermediates, Mac editing |
| WebM | Google / WHATWG (2010, royalty-free) | Chrome, Firefox, Edge; Safari 17+ for AV1 | VP8, VP9, AV1, Vorbis, Opus | HTML5 web embeds, background video |
| MKV | Matroska (open, 2002) | VLC, MPV, modern Android players; not Safari / Roku | H.264, H.265, AV1, FLAC, multi-track | Media servers, multi-subtitle libraries |
| AVI | Microsoft (1992) | Windows native, VLC | DivX, XviD, MPEG-4, MP3, PCM | Legacy Windows editors and players |
| WMV | Microsoft (2003) | Windows Media Player, VLC | WMV1/2, WMA | Legacy Windows / Microsoft workflows |
| MTS / M2TS | AVCHD (Sony/Panasonic 2006) | VLC, MPC-HC | H.264, AC-3, LPCM | Re-wrapping for camcorder-style workflows |
| M4V | Apple MP4 variant | iTunes, Apple devices, VLC | H.264, HEVC, AAC | Apple ecosystem / iTunes libraries |
| GIF | CompuServe (1987) | Everywhere | n/a (frame-by-frame palette) | Short silent loops, broad embed support |
| Codec | File size (relative) | Where it plays | Notes |
|---|---|---|---|
| H.264 (AVC) | 100% (baseline) | Every device made since ~2010 | Universal default; fast encode, hardware decode almost everywhere |
| H.265 (HEVC) | ~50-60% of H.264 | Safari 11+ (iOS) / 14.1+ (macOS), Chrome 107+, Edge, recent Android | iPhones record HEVC by default since iOS 11; royalty-bearing |
| VP9 | ~50-70% of H.264 | Chrome 29+, Firefox 28+, Edge 79+, Android; not Safari | Royalty-free; a primary YouTube codec |
| AV1 | ~30-50% of H.264 | Chrome 70+, Firefox 67+, Safari 17+ (partial), Edge; hardware decode on Intel Arc, NVIDIA RTX 30+, AMD RX 6000+ (RDNA 2), Apple M3+ | Royalty-free; slow software encode but the most efficient option |
| MPEG-4 / XviD / DivX | ~140% of H.264 | VLC, older AVI workflows | Legacy; encode only for old-hardware compatibility |
| MJPEG | ~400% of H.264 | Editors, VLC, browser-native | Per-frame JPEG; handy for editing, poor for distribution |
Need only one direction? Jump straight to a pair: MP4 to MOV · MP4 to WebM · MP4 to MKV · MP4 to AVI · MP4 to M4V · MP4 to MP3. Going the other way — into MP4 — use MOV to MP4, MKV to MP4, WebM to MP4, AVI to MP4, or HEVC to MP4. To shrink an MP4 without changing format, use Compress MP4; to cut footage first, use the Video Cutter.
It can be. MOV and MP4 are closely related containers — MP4 was directly derived from Apple's QuickTime File Format — and both natively carry H.264 + AAC, which is what most MP4s already contain. In that case the conversion is a container remux: the compressed video and audio streams are copied into the MOV wrapper unchanged, so quality is identical and the job is near-instant. Re-encoding only happens if you switch codecs (for example to ProRes for editing) or change the resolution, bitrate, or quality preset.
Convert MP4 to MOV. Final Cut Pro and most Apple-centric editors prefer the MOV container, and re-wrapping your MP4 into MOV makes it import without the "incompatible media" prompt. If you're doing serious color grading or compositing, transcode to a ProRes-based MOV rather than leaving the long-GOP H.264 in place — ProRes is an edit-intermediate codec that scrubs and renders far more smoothly, at the cost of a much larger file. For light trims and assembly, a straight H.264 MOV remux is fine.
WebM pairs the VP9 or AV1 codec with Opus audio, and both VP9 and AV1 compress more efficiently than the H.264 that's usually inside an MP4 — typically landing 30-50% smaller at comparable perceptual quality. That efficiency is the whole reason Google built WebM for the web: smaller files mean faster page loads and lower bandwidth. The tradeoff is encode time (AV1 software encoding is slow) and compatibility — Safari only added partial AV1 support in version 17, so web pages targeting all browsers often ship an MP4 fallback next to the WebM.
Often not — and that's usually a reason to convert to MP4, not away from it. MKV is excellent for media-server libraries because it holds multiple audio and subtitle tracks, but Roku, most smart-TV browsers, and Apple devices don't decode MKV natively. So if your goal is plain TV playback, your MP4 is already the safer file — keep it. Convert MP4 to MKV only when you specifically need the multi-track features for a player that supports them, like VLC, Plex, or Jellyfin. (If you've got the reverse problem — an MKV that won't play — use MKV to MP4 instead.)
You have two paths. To stay in MP4, switch the bitrate mode to Specific file size and enter your target in MB — for example 10 MB for Discord's free tier, 25 MB for Gmail, or 16 MB for WhatsApp — and the encoder auto-tunes the bitrate to hit it. For more headroom at the same size, combine downscaling (4K → 1080p, or 1080p → 720p) with the H.265 or AV1 codec, each of which cuts size another 40-50% beyond H.264 at equal quality. Trimming dead footage first is the highest-leverage step on long clips. If you only need to shrink and not re-wrap, the dedicated Compress MP4 tool is the most direct route.
Yes. Pick MP3 as the output format and the converter drops the video track and encodes the audio stream to MP3 — useful for pulling a song out of a music video or the audio from a lecture or interview. If the MP4 already contains AAC and you'd rather keep it lossless, you can target an AAC/M4A output to copy the audio without re-encoding. The dedicated MP4 to MP3 page walks through the audio-extraction settings, including bitrate selection.
Very little at the byte level — M4V is Apple's MP4 variant, used mainly inside iTunes and the Apple ecosystem, and it usually holds the same H.264 + AAC streams. The main practical difference historically was that purchased M4V files could carry Apple's FairPlay DRM; plain video M4V is otherwise just an MP4 with a different extension. Converting MP4 to M4V is typically a fast container remux so the file is recognized cleanly by iTunes and Apple devices.
There's no fixed per-file cap. Conversion runs on our servers, so the practical limit is upload size and connection speed and your patience for the upload — multi-gigabyte 4K and 8K MP4s are routine. Batch jobs have no quantity limit either; you can queue many files and grab them all as one ZIP. If a very large file makes your device start swapping, process one at a time or trim it down first with the Video Cutter.