Convert QuickTime and camera MOV clips into H.264/AAC MP4 files that are easier to upload and share. Free with clearly published fair-use limits — no sign-up, no watermarks.
Drop your MOV file here
or click to browse — One file per media job — 100 MB / 10 minute limit
☁️ Server conversion — your file is uploaded securely (HTTPS), converted, and removed from temporary processing storage after the request finishes. Forced-crash leftovers are removed by recovery sweeps. A verified codec/duration report is included on the download page. Which tools upload, and which do not
MOV is flexible enough to contain phone video, ProRes editing footage, HEVC or uncompressed audio, but the receiving software may support only a narrow subset. Re-encoding the primary picture and sound as H.264/AAC produces a predictable delivery copy; the original MOV remains untouched as your editing master.
This page has a real two-second fixture made from generated motion, colour and tones — no copyrighted clip and no visitor data. Download the source, run it through the tool, and compare it with the expected profile-1.0.0 output.
⬇ Sample input (MOV) ⬇ Verified expected output
| Check | Input | Expected output |
|---|---|---|
| Codecs | h264 + pcm_s16le | h264 + aac |
| Duration | 2 s | 2 s (Δ 0 s) |
| File size | 273,388 bytes | 84,697 bytes |
| SHA-256 | 6cd69d1d4d42f9652fc4737f0b491f68c96c7fcebbd2d26e4c5d0ece228d35cc | 667430357cbeaab2e7d0b7272003aadb38756dcf88627541273d5d258814ee06 |
| Measured time | — | 132 ms in the published environment |
| Validation | Signature + ffprobe | Codec, complete decode and duration: pass |
No confidence score is invented: transcoding is deliberately lossy, so the defensible result is a set of pass/fail structural checks, not “97% accurate.” Your download page exposes the same per-job evidence report as JSON and CSV. See the method, limitations and six-case comparison, or download the anonymous CSV / JSON dataset.
“Accuracy” for this lossy task means the published structural gates below; perceived quality still needs human review of the output.
| Profile | Date | Validation change | Re-test | Result |
|---|---|---|---|---|
| 1.0.0 | 2026-08-16 | Fixed codec profile; EBML DocType / ISO brand checks; rotation-aware dimensions; ffprobe; complete decode; duration tolerance | FH-MEDIA-02 plus the six-profile release gate and adversarial regressions | pass |
MOV is Apple's flexible QuickTime container. Phones, cameras and editing software can place anything from H.264 and HEVC to ProRes video and uncompressed audio inside it. That makes MOV useful as a recording or editing master, but unpredictable for a receiving app that expects a simple H.264/AAC MP4.
MP4 is the safest delivery container for video. The widely supported combination is H.264 picture with AAC sound, which plays on current phones, browsers, televisions and editing apps. MP4 can contain other codecs too, so a genuine compatibility conversion must inspect and encode the streams rather than merely rename the extension.
| MOV | MP4 | |
|---|---|---|
| Type | Video/audio container | Video/audio container |
| Compression | Codec-dependent | Usually H.264/H.265 + AAC |
| Transparency | Codec-dependent | Usually no |
| Animation | Video | Video |
| Typical use | Phone/camera video, editing masters | Sharing, uploads, playback, editing |
MOV describes a container, not one predictable kind of video. An iPhone may put HEVC and AAC inside it, a camera may use H.264, and an editing application may export ProRes with PCM audio. That freedom is valuable during production and exactly why a receiving app can reject the file. Re-encoding the primary streams into H.264/AAC MP4 replaces that uncertainty with a combination designed for delivery.
The compatible copy is not a substitute for the source. Professional codecs, high bit depths, alpha channels, alternate audio and camera metadata may have no equivalent in the chosen MP4 profile. Archive the MOV, then inspect orientation, color and the first and last seconds of the MP4 before publishing — especially for HDR phone footage or files exported by an editor.
Yes — there is no sign-up, payment or watermark. The published safeguards are 100 MB input, a 160 MB output cap, a 10 minute selected-stream limit, an 8 minute request-wide deadline and four jobs per visitor per 10 minutes; they are technical limits, not a paid tier.
Media files are handled one at a time. That makes the documented CPU, memory and cleanup limits enforceable and gives the next file a clean job directory. Finish or clear the current file before adding another.
Yes. Native FFmpeg is too large and resource-intensive for a reliable browser-only conversion, so this tool sends the file over HTTPS to our server. It is limited to 100 MB and 10 minutes and uses an isolated temporary job directory. Normal cleanup removes that directory after success, failure, cancellation or timeout; startup and five-minute sweeps remove a forced-crash leftover once it is older than the request deadline. Media files are never intentionally retained.
The visible content, timeline and aspect ratio are retained, but H.264/AAC output is lossy. Keep the MOV as the editing master and use the MP4 as the compatible sharing copy, especially for HDR or professional camera footage.
filehugger.com