MOV to MOV Converter

How to Re-encode MOV Video Online

1. Upload Your MOV File: Drag and drop or click "+ Add Files" to load .mov files from your computer. Batch upload is supported — re-encode a folder of iPhone screen recordings, QuickTime exports, or camera card dumps with the same settings in one pass.
2. Pick a Video Codec: Default is H.264 — the universally compatible codec QuickTime has shipped with for years. Switch to H.265 (HEVC) for ~40-50% smaller files at the same visual quality (the iPhone default since iOS 11), AV1 for the smallest size on modern hardware, or pick from VP9, MPEG-4, MJPEG, DivX, XviD, Theora, H.263, H.261, or HuffYUV when a downstream editor or player needs that specific codec inside the MOV wrapper.
3. Tune Quality, Resolution, or Trim (Optional): Use the Video Quality Preset dropdown (Lowest/Low/Medium/High/Highest), set a CRF value (16-51 for H.264/H.265, 16-63 for VP9/AV1) on the Constant Quality slider, set a Constant or Variable Bitrate, pick a resolution preset (144p, 240p, 360p, 480p, 576p, 720p, 1080p, 1440p, 2160p, 4320p), scale by percentage, or use Video Trim with start time and duration. Audio Codec defaults to AAC with AC3, MP3, MP2, Opus, FLAC, Vorbis, AMR, Speex, and PCM variants available.
4. Re-encode and Download: Click "Convert" and your re-encoded MOV downloads in seconds. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.

Why Re-encode MOV?

MOV is Apple's QuickTime container — the wrapper Final Cut Pro, iMovie, QuickTime Player, and the iPhone camera roll all default to. The same .mov file might hold an iPhone HEVC recording from 2017 onward, an older H.264 capture from a 2014-era iPhone, a ProRes master from a Final Cut export, or an MJPEG stream from a DSLR. Re-encoding the same MOV gives you control over codec, bitrate, resolution, and length without changing the extension that QuickTime, Final Cut, iMovie, and Apple Photos expect.

• Shrink iPhone 4K HEVC for sharing — A 60-second iPhone 4K/60fps HEVC clip is roughly 400-500MB. Re-encoding to 1080p H.264 at CRF 23 cuts that to ~80-120MB while keeping the .mov extension that Mac and iPhone apps prefer — small enough for AirDrop in seconds and well under most cloud upload thresholds.
• Fix HEVC playback on older Macs and Windows — H.265 inside MOV stutters or refuses to play on Macs older than the 2017 lineup and on Windows machines without the HEVC Video Extension installed. Re-encoding to H.264 keeps the MOV container but produces a file every QuickTime build since 2009 plays smoothly.
• Hit messaging and email size limits — Gmail and Outlook cap attachments at 25MB. Discord's free tier is 10MB (lowered from 25MB in September 2024; Nitro Basic 50MB, Nitro 500MB). Slack free workspaces top out at 1GB per file but throttle anything large. Re-encode a 200MB MOV recording down to 720p H.264 at a lower CRF and it lands well under those limits without leaving the MOV format.
• Transcode to ProRes-friendly H.264 proxies for editing — Editors often re-encode high-bitrate camera MOV files into smaller H.264 proxies for offline editing, then relink to the original masters at finish time. Lower CRF + 720p produces a proxy a third the size that scrubs smoothly on a laptop.
• Downscale 4K screen recordings for web upload — macOS and iPhone screen recordings save as 4K MOV by default. For YouTube tutorials, software demos, or bug reports, 1080p is plenty. Downscaling cuts file size 60-75% while keeping every UI element legible.
• Trim out dead time — Long camera takes and screen recordings often have minutes of setup before the useful content starts. Use Video Trim to keep just the segment you need and re-encode it cleanly, dropping a multi-gigabyte file to the size of the shot you actually want.
• Standardize codec across a mixed library — A folder pulled off a few seasons of iPhones might mix H.264 (older) and HEVC (newer) recordings. Re-encoding the whole set to a single codec makes a library indexable and predictable in Final Cut or Premiere, where codec mismatches force per-clip transcodes during import.

MOV Codec Comparison: H.264 vs H.265 vs AV1 vs MPEG-4

CRF Quality Quick Guide (H.264/H.265 inside MOV)

Frequently Asked Questions

Why would I convert MOV to MOV instead of just keeping the original?

The container stays .mov, but the codec, bitrate, resolution, and length inside can all change. An iPhone HEVC MOV at 4K/60fps and an H.264 MOV at 1080p/30fps are both valid .mov files but differ massively in size and compatibility. Re-encoding lets you swap codec (H.265 ↔ H.264 ↔ AV1), drop bitrate, downscale, or trim — all while keeping the extension QuickTime, Final Cut, iMovie, Apple Photos, and AirDrop expect.

Should I keep H.265 (HEVC) or switch to H.264 inside the MOV?

Keep HEVC if every device that needs to play the file is recent — iPhone 7 or newer, M-series Mac, recent Windows with the HEVC Video Extension, recent smart TV. HEVC saves ~40-50% size at the same quality. Switch to H.264 when the file needs to play anywhere — older Macs (pre-2017), Windows machines without the codec extension, older Android phones, web browsers without HEVC support, or any system where compatibility matters more than size.

Can I re-encode a MOV that won't play normally?

Often yes. MOV files with corrupted index atoms (moov atom issues) can frequently be re-encoded by reading the valid frames and writing a fresh container. The output gets clean index data and seekability restored. Re-encoding cannot recover frames that are physically missing or unreadable in the source — it can only rebuild the wrapper around what's still decodable.

Will re-encoding reduce quality?

Every lossy re-encode loses some data. The loss is small at low CRF settings (17-20) and barely visible at CRF 23 or below for H.264. Re-encoding from an already-compressed source (an iPhone HEVC clip) and dropping the bitrate further compounds the loss. For best results, re-encode from the highest-quality source you have, and stay at CRF 23 or below if quality matters more than size.

Will iPhone Live Photo motion, HDR, and Dolby Vision survive?

Standard MOV metadata (creation date, GPS, orientation, basic codec parameters) carries through re-encoding. Live Photo pairing — the still JPEG bundled alongside the MOV — is a Photos-app-level link, not part of the MOV file itself, and is not preserved by a standalone re-encode. HDR10 metadata generally does not survive a re-encode, and no tone-mapping is applied — an HDR HEVC source re-encoded to H.264 gets a plain colour conversion and can come out looking flat or washed out. Dolby Vision metadata is typically dropped, so keep the original file if the HDR grade matters.

What audio codec should I use inside MOV?

AAC is the safe default — it's what every iPhone, iPad, Mac, and AirDrop recipient expects inside MOV. Switch to AC3 if you're producing for a workflow that prefers Dolby surround, or PCM (uncompressed) when feeding into a video editor that prefers raw audio. MP3 inside MOV works but is uncommon; Opus, FLAC, and Vorbis are available when a specific tool requires them.

Is there a file size limit?

XConvert processes files on its servers and deletes them automatically after a few hours. Most modern laptops handle 1080p MOV files up to 2-4GB without trouble. For multi-gigabyte 4K iPhone or camera footage, downscale resolution first, trim to the segment of interest, or split into chunks before re-encoding.

How is this different from converting MOV to another format?

Re-encoding MOV to MOV keeps the .mov extension that QuickTime, Final Cut, iMovie, and Apple's apps prefer. If you don't need to stay in MOV, Convert MOV to MP4 gives you the universal modern container, Convert MOV to AVI targets older video editors, Convert MOV to HEVC extracts to a raw HEVC stream, or Compress MOV is a guided flow when you have a specific size target.

Does the converter work offline once the page loads?

No. The page and its controls load once, but the actual conversion runs on our servers, so an active internet connection is required for the upload, the processing, and the download.