Convert MOV to MP4
FFmpeg Online — Run FFmpegin Your Browser
Convert your MOV file to MP4 right in your browser. Nothing is uploaded, nothing is installed, and your files never leave your device.
Convert, compress, trim, and process video & audio locally. Files never leave your device. No signup. The real FFmpeg.- 100% private — nothing is uploaded
- Free, no account
- Real FFmpeg — any command runs
Convert MOV to MP4 — tool
Loading the tool…
What this does
This tool converts MOV files to MP4 in your browser. It runs the real FFmpeg, compiled to WebAssembly, right inside your browser — nothing is installed, no account is needed, and your files are never uploaded to a server. Add a MOV file, press Run, and download the MP4 — the output matches what you would get from FFmpeg on the command line.
About the formats
MOV is Apple's QuickTime format — the one iPhones and Macs record video in.
The result is an H.264 MP4 set to the yuv420p pixel format, so it plays in every browser and player.
The FFmpeg command
This is the exact command the tool runs for you. Copy it to run the same conversion with FFmpeg on your own machine.
ffmpeg -i input.mov -c:v libx264 -preset veryfast -pix_fmt yuv420p -movflags +faststart -crf 23 -c:a aac -b:a 128k output.mp4 Two ways your MOV becomes an MP4
Many MOV files already contain video and audio that MP4 supports (H.264 video with AAC or MP3 audio). When the tool detects that, it repackages the file into an MP4 without re-encoding: near-instant, at full original quality.
Otherwise it re-encodes the video to H.264 and the audio to AAC, the combination that plays on Windows, Android, every browser and every social site. Re-encoding runs in your browser, so a long video takes a while; the progress bar shows how far along it is.
Choosing the quality
When re-encoding, the Quality (CRF) slider trades size for quality. Lower numbers mean better quality and bigger files: 18 looks practically identical to the original, 23 (the default) is a good balance, and 28–30 gives much smaller files that look softer.
| CRF | Quality | File size |
|---|---|---|
| 18 | Visually near-identical | Largest |
| 23 (default) | Very good | Balanced |
| 28–30 | Softer detail | Smallest |
Same commands. No limits.
Test in your browser free — run at scale on Rendi's FFmpeg API. n8n, Zapier & Make integrations.
Frequently asked
Will I lose quality converting MOV to MP4?
Not when the tool can repackage the file: the video and audio are copied as they are. When it has to re-encode, the default setting looks very close to the original; move the Quality slider to 18 if you want it practically identical.
Why convert MOV to MP4 at all?
MOV is Apple's format. It plays fine on a Mac or iPhone, but some Windows apps, Android phones, websites and editors handle MP4 better. MP4 with H.264 plays practically everywhere.
Does it keep the sound?
Yes. When repackaging, the original audio is kept as it is. When re-encoding, the audio is converted to AAC at 128 kbps, which is standard for MP4.
How long does the conversion take?
Repackaging takes seconds even for large files. Re-encoding is slower in a browser than in a desktop app, so a long, high-resolution video can take several minutes. For big batches, the same command runs much faster on the Rendi API.
Is it really private?
Yes. FFmpeg runs entirely in your browser via WebAssembly. Your files are never uploaded, streamed, or seen by any server — including ours.
What's the file size limit?
Around 2 GB, and it's a browser limit rather than ours. WebAssembly can only address so much memory, so the whole job has to fit in the tab. Lightweight operations that copy streams instead of re-encoding (trimming, remuxing, stripping the audio track) work on files right up near that ceiling, because the file is read in place instead of being copied into memory. Full re-encodes need room for the input, the output, and working memory at once, so their practical ceiling is lower — lower still on phones. For anything bigger, the exact same command runs with no size limit on the Rendi API.
Does it work on my phone?
Yes. It's a web page, so it opens in Safari or Chrome on a phone the same way it does on a laptop: nothing to install, and your files still never leave the device. The layout is built for touch, and the Run button stays pinned to the bottom of the screen while you work. What changes on a phone is memory — there's much less of it, so the size limits are halved: the tool stops at files over about 1 GB, and it refuses re-encodes over 500 MB instead of letting the tab crash mid-run. Trimming, remuxing and extracting audio stay cheap, so those are the jobs a phone handles best. For a long video or a heavy encode, send the same command to the Rendi API; that works from a phone just as well.
Why does my MP4 look green in some players?
That's a pixel-format mismatch. When a video isn't encoded as yuv420p, some players and browsers can't display it and fall back to green or garbled frames. Every MP4 our tools re-encode already sets -pix_fmt yuv420p, so you won't hit this here — and operations that copy the video stream untouched keep whatever format already played. If you write your own command in the terminal, add -pix_fmt yuv420p and it'll play everywhere.