HEVC to MOV Converter

How to Convert HEVC to MOV Online

1. Upload Your HEVC Files: Drag and drop or click "+ Add Files" to load .hevc (raw H.265 bitstream) or .h265 files from your computer, Google Drive, or Dropbox. Batch conversion is supported.
2. Pick File Compression: Default is Quality Preset set to "Very High (Recommended)" which keeps the H.265 stream visually intact. Drop to "High" or "Medium" to shrink output, or switch to Specific File Size, Constant Bitrate, Variable Bitrate, Constant Quality, or Constraint Quality if you need a precise target. Video Codec defaults to H.265 (matches the source — fastest path); pick H.264 if your downstream tool refuses HEVC.
3. Set Resolution and Trim (Optional): Use Preset Resolutions (2160p, 1440p, 1080p, 720p, etc.), Resolution Percentage, Width × Height, or keep "Keep original". Trim with a Time Range (HH:MM:SS.mmm) if you only need a portion of the clip.
4. Convert and Download: Click "Convert", then download the .mov files. Files process in your browser session — no sign-up, no watermark, no email required.

Why Convert HEVC to MOV?

A raw .hevc file is just an H.265 elementary bitstream — no container, no timing metadata, no audio track. Most Apple software (Final Cut Pro, iMovie, QuickTime Player) expects video to arrive inside a .mov, .mp4, or .m4v container. Wrapping the H.265 stream in a MOV container makes the same video data playable and editable on macOS and iOS without changing a single frame.

• Match what iPhone records natively — Since iOS 11 and iPhone 7 (per Apple Support), the Camera app's High Efficiency setting writes HEVC video into a .mov container. Converting a loose .hevc to .mov reconstructs that native pairing.
• Final Cut Pro / iMovie / Motion ingest — Apple's NLEs accept HEVC, but only inside a recognized container. A raw .hevc will usually fail import, while the same stream rewrapped to MOV imports cleanly.
• QuickTime Player playback — macOS plays HEVC in MOV without third-party codecs. Double-clicking a raw .hevc typically opens nothing.
• AirDrop and Photos compatibility — Photos.app, AirDrop, and Messages all treat .mov as a first-class video; raw HEVC streams are not recognized by these apps.
• Smaller files than re-encoding to H.264 MOV — Keeping the H.265 codec inside MOV typically gives 40–50% smaller files than H.264 at the same visual quality, per Apple's own HEVC documentation.
• DaVinci Resolve and Premiere Pro on Mac — Both accept HEVC-in-MOV directly; raw .hevc requires a separate rewrap step in tools like ffmpeg or Subler.

HEVC vs MOV — Codec vs Container

A common confusion: HEVC and MOV are not alternatives — they describe different layers of the file. HEVC (H.265) is the video codec. MOV is the container. A .mov can hold H.264, H.265 (HEVC), ProRes, or other codecs. This conversion changes the wrapper, not (necessarily) the codec.

MOV Codec Compatibility — What Goes Inside

When you save HEVC to MOV here, the codec stays H.265 by default (fastest, no quality loss). If your destination tool struggles with H.265, switch the Video Codec dropdown to H.264.

Note on the hvc1 vs hev1 codec tag: Apple's QuickTime and Final Cut Pro prefer the hvc1 tag for HEVC tracks (Bitmovin community discussion). XConvert writes Apple-compatible tagging when targeting MOV, so files play in QuickTime without "media that isn't compatible" errors.

Frequently Asked Questions

Is this a true remux, or a re-encode?

When you leave Video Codec at its default (H.265, matching the source), the conversion writes the same H.265 bitstream into a MOV container — effectively a remux with no quality loss and very fast processing. If you change codec, drop quality preset, or set a smaller target file size, the H.265 is decoded and re-encoded, which is slower and introduces minor generational loss.

Why won't my raw .hevc file open in QuickTime or Final Cut Pro?

Raw .hevc (and .h265) files are elementary bitstreams without a container — no audio, no timing, no muxing. macOS and Apple's editors need the video wrapped in MOV, MP4, or M4V. After converting to .mov here, the file opens by double-click and imports into Final Cut Pro 10.4+.

Will the MOV file be larger than the HEVC source?

For a pure remux (default settings, same codec), the MOV is within a few KB of the original — the only added bytes are container atoms and timing metadata. If you switch the Video Codec to H.264 at the same visual quality, expect roughly 1.5–2× the file size, since H.265 compresses about 40–50% better than H.264 at equivalent quality.

My HEVC clip has no sound — will MOV add audio?

No. The conversion can only carry forward what's in the source. A raw .hevc bitstream contains no audio track, so the resulting MOV will also be silent. To pair an audio file with video, use a tool like ffmpeg locally — XConvert's .hevc input expects a video-only stream.

Does this work on iPhone HEVC recordings?

iPhone recordings are already .mov (HEVC inside MOV). You don't need this converter for iPhone video — load them into Photos, Final Cut Pro, or iMovie directly. This tool is for loose .hevc / .h265 files (encoder dumps, OBS recordings configured to raw bitstream, downloads from compliance archives). If you have iPhone footage already in MOV but want to recompress, see Compress MOV or Trim MOV.

What if I need MP4 instead of MOV?

MP4 and MOV are very closely related — both descend from the ISO Base Media File Format (ISO/IEC 14496-12). MP4 has broader Windows, Android, and web compatibility; MOV is preferred for Apple editing workflows. If you're targeting Windows or web playback, use Convert HEVC to MP4 instead; the conversion choices are nearly identical.

Can Windows play HEVC inside MOV?

Yes, with codecs installed. Windows 10/11 plays MOV through the Films & TV app once the HEVC Video Extension is installed from the Microsoft Store. VLC plays HEVC-in-MOV on all platforms without extra setup. For pure Windows targeting, MP4 is the safer container.

Is there a file size limit?

XConvert handles large videos in-browser, but practical limits depend on your device's RAM. A 4K 10-bit HEVC file remuxing to MOV is fast and memory-light because no decoding happens; re-encoding 4K to H.264 is far more demanding. For repeatable large conversions, work with files under 2 GB or split with Trim MOV first.

Will my video metadata (timecode, rotation, HDR) survive?

A remux preserves the H.265 stream and most stream-level metadata (color primaries, transfer characteristics, HDR10 mastering display info) because the bytes aren't re-encoded. Container-level metadata like timecode tracks or rotation flags is reconstructed in the MOV wrapper. If you're working with Dolby Vision profile 8.4 or other proprietary metadata, verify on a single test clip first — those layers depend on whether your source .hevc carried the SEI messages.