Convert HEVC to MOV — Free Online Tool
Convert HEVC/H.265 video files to QuickTime MOV format, re-encoding the video stream to H.264 (libx264) for maximum compatibility with Apple's ecosystem and professional video editing applications like Final Cut Pro. This tool runs entirely in your browser — no upload required — and displays the exact FFmpeg command for handling larger files locally.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your HEVC file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
HEVC (H.265) achieves its compression efficiency through a more complex encoding algorithm than H.264, which means it is not natively editable in many older Apple and professional workflows despite MOV being an Apple format. During this conversion, the H.265 video stream is fully re-encoded using the libx264 encoder at CRF 23 — a high-quality lossy transcode that produces an H.264 video stream inside a MOV container. Because HEVC files typically contain no audio stream (raw .hevc files are video-only), the AAC audio track is added as a default channel if audio exists; if your source has no audio, FFmpeg will handle that gracefully. The -movflags +faststart flag reorganizes the MOV file's metadata to the front of the file, enabling progressive playback and web streaming. The re-encoding step means this is not a lossless remux — some quality is traded for the dramatically wider compatibility that H.264/MOV offers.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg application — the open-source multimedia processing engine that handles decoding the input HEVC stream and re-encoding it as H.264 inside a MOV container. |
-i input.hevc
|
Specifies the input file — a raw HEVC/H.265 elementary stream. FFmpeg will parse this bitstream directly without a container wrapper, which is typical for .hevc files produced by broadcast encoders, capture cards, or extracted from transport streams. |
-c:v libx264
|
Re-encodes the H.265 video stream using the libx264 encoder to produce H.264 video output. This is a full transcode (not a copy), chosen over keeping libx265 to maximize compatibility with Apple QuickTime, Final Cut Pro, and older Mac hardware that may lack H.265 hardware decoding. |
-c:a aac
|
Encodes any detected audio using the AAC codec, which is the native and preferred audio format for Apple's MOV container. Since raw .hevc files typically have no audio, this flag acts as a safe default if audio is present in the source. |
-crf 23
|
Sets the Constant Rate Factor for the libx264 encoder to 23, which is the standard default producing a good balance of visual quality and file size. Because the source is already a lossy H.265 encode, CRF 23 is chosen to minimize additional generation loss while keeping the output at a manageable size. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, a standard rate that provides transparent-quality stereo audio for most content. This only applies if the source HEVC file contains an audio track. |
-movflags +faststart
|
Moves the MOV container's metadata atom (moov) to the beginning of the output file after encoding, enabling the file to begin playing before it is fully downloaded. This is particularly valuable when the resulting MOV will be served from a web server or shared via cloud storage. |
output.mov
|
Defines the output filename and container format. The .mov extension tells FFmpeg to wrap the encoded H.264 video and AAC audio inside Apple's QuickTime MOV container, complete with the structural features like chapter support and multiple audio track capability that MOV provides. |
Common Use Cases
- Importing HEVC footage from a modern Sony, Canon, or drone camera into Final Cut Pro or Premiere Pro without requiring hardware H.265 decoding support on older Mac hardware
- Preparing H.265 video for delivery to a client or post-production house whose editing suite only accepts H.264 inside MOV or MP4 containers
- Converting HEVC screen recordings or gameplay captures into a MOV format suitable for direct import into Apple iMovie or DaVinci Resolve on macOS
- Archiving a raw .hevc broadcast or streaming capture as a self-contained MOV file with AAC audio for long-term compatibility with Apple QuickTime Player
- Transcoding HEVC content for use in a video editing timeline where proxy workflows require H.264/MOV as the proxy format
- Converting H.265 video captured on an iPhone or action camera into an H.264 MOV file that can be directly embedded in a Keynote or PowerPoint presentation on macOS
Frequently Asked Questions
Yes — this is a lossy transcode, not a lossless remux. H.265 achieves better compression than H.264, meaning an H.264 output at the same visual quality will be larger in file size. The default CRF 23 setting used here produces high-quality H.264 output that looks excellent for most purposes, but since the video stream is fully re-decoded and re-encoded, there is a small generational quality loss compared to the original HEVC source. For archival purposes you may want to keep the original HEVC file.
While MOV containers do support H.265 video streams, H.264 inside MOV is far more universally compatible — particularly with older Macs, Apple editing software versions, and third-party tools that accept MOV files. H.265 in MOV can cause import failures in older versions of Final Cut Pro, iMovie, and many broadcast delivery systems. The tool defaults to libx264 to ensure the output 'just works' across the widest range of Apple and professional environments. If you specifically need H.265 preserved, you can modify the FFmpeg command to use -c:v libx265 instead.
Yes. Raw .hevc files are often video-only with no embedded audio stream. FFmpeg will detect the absence of an audio track and the -c:a aac flag will simply produce no audio stream in the output MOV rather than failing. The resulting MOV file will be a video-only container, which is perfectly valid and will open correctly in QuickTime Player and editing applications. No silent or dummy audio track is artificially added.
The +faststart flag instructs FFmpeg to move the MOV file's metadata (the 'moov atom') to the beginning of the file after encoding is complete. By default, FFmpeg writes this metadata at the end of the file. Moving it to the front allows video players and browsers to begin playing the MOV file before it has fully downloaded, which is essential for web delivery and streaming scenarios. It has no effect on visual quality but makes the output file significantly more practical for online use.
Adjust the -crf value in the command. CRF (Constant Rate Factor) for libx264 ranges from 0 (lossless) to 51 (worst quality), with 23 as the default. Lower numbers mean higher quality and larger file sizes — try CRF 18 for near-visually-lossless output, or CRF 28 if you need a smaller file and can accept slightly lower quality. Since the source is already a compressed HEVC file, going below CRF 18 provides diminishing returns because the original H.265 encoding artifacts are already baked into the source.
Yes. On macOS or Linux, you can use a shell loop: for f in *.hevc; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "${f%.hevc}.mov"; done. On Windows (PowerShell), use: Get-ChildItem *.hevc | ForEach-Object { ffmpeg -i $_.FullName -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart ($_.BaseName + '.mov') }. This is especially useful for converting large batches of drone or camera footage where the browser-based tool's 1GB per-file limit might be a constraint.
Technical Notes
HEVC (.hevc) is a raw elementary stream format — it contains only a naked H.265 video bitstream with no container metadata, chapter markers, subtitle tracks, or audio. This means many quality attributes of the source (HDR metadata, color space tagging, frame rate signaling) may not be reliably preserved during the transcode to H.264/MOV, since libx265's HDR10 signaling does not transfer automatically to libx264. If your HEVC source contains HDR content, the output H.264 MOV will be tone-mapped or may appear washed out unless you explicitly add HDR-to-SDR tone mapping filters. The MOV container supports transparency (via PNG or MJPEG codec), subtitles, chapters, and multiple audio tracks — but none of these are relevant when converting from a raw .hevc elementary stream, which carries none of that metadata. File size will typically increase compared to the HEVC source because H.264 requires more bits to achieve equivalent visual quality. The -x265-params log-level=error flag present on the input side suppresses verbose x265 decoder logging, keeping conversion output clean without affecting the encoded result.