HEVC to H.264: Convert iPhone Videos for Universal Playback

You record a video on your iPhone, AirDrop it to a friend with a Windows PC, and they get an error. You open it in an older video editor, the timeline is blank. You upload it to a CMS, the preview is broken. Welcome to HEVC, the format Apple decided was the future of video back in 2017 and that the rest of the world is still catching up to.

Since iOS 11, iPhones default to recording in HEVC (also known as H.265) when the camera setting "High Efficiency" is enabled, which it is on every new iPhone out of the box. HEVC files are about half the size of equivalent H.264 at the same quality. That's great for storage. It's terrible for compatibility, because lots of software, devices, and platforms either don't support HEVC at all or require special licensing.

This guide covers exactly when you need to convert HEVC to H.264, how to do it without losing quality, and the gotchas nobody tells you about (audio codec mismatches, HDR metadata, frame rate weirdness).

Why HEVC Breaks Things

HEVC is genuinely better than H.264 at compression. The MPEG group's official HEVC overview describes about 50% bitrate reduction at equivalent visual quality. The catch is that decoding HEVC requires either a hardware decoder (built into modern Apple silicon, Intel chips from 2015+, AMD chips from 2018+, and most current Android SoCs) or a software decoder with proper licensing.

H.264 decoders, by contrast, are everywhere. Every browser, every OS, every video editor going back ten years, every smart TV, every game console, every digital signage box. H.264 is the lowest common denominator of video, and that's exactly what you want when "will this play?" needs to be a yes.

Specific places HEVC fails:

• Windows 10 and 11: Native HEVC playback requires the HEVC Video Extensions package ($0.99 from the Microsoft Store, free if your PC ships with a hardware HEVC decoder). Without it, Windows Media Player, the Photos app, and many editors fail.
• Android (older devices): Pre-2018 phones often lack hardware HEVC decoders. Software decoding is slow and battery-eating.
• Browsers: Chrome added HEVC playback in 2022, but only on systems with hardware HEVC support. Firefox supports HEVC only on Windows 10+ with the same extensions package. Safari handles it natively.
• Older video editors: Premiere Pro 2017 and earlier, Final Cut Pro X 10.3 and earlier, and most free editors below DaVinci Resolve 14 don't import HEVC reliably.
• Web platforms: WordPress, Wistia, many CMS video uploaders re-encode HEVC anyway, sometimes badly.

If your video has to "just work" on someone else's machine, H.264 is the answer.

Photo by Jan Kopriva on Pexels

How to Tell if Your Video Is HEVC

Before converting, confirm you actually have an HEVC file. Three quick ways:

On a Mac: Right-click the file in Finder, choose "Get Info," and look for "Codecs" under "More Info." If it lists "HEVC" or "H.265," that's your culprit.

On Windows: Right-click, "Properties," "Details" tab, look at "Video codec." If you see "HEVC" or the four-character code "hev1" or "hvc1," it's HEVC.

With ffprobe (any OS): If you have FFmpeg installed:

ffprobe -v quiet -print_format json -show_streams yourfile.mov | grep codec_name

You'll see "codec_name": "hevc" if the video stream is HEVC.

iPhone videos typically come as .mov (QuickTime container) holding HEVC video plus AAC audio. The container being .mov instead of .mp4 doesn't matter for playback compatibility, but converting to .mp4 H.264 fixes both issues at once.

Method 1: Convert HEVC to H.264 Online (Easiest)

The simplest approach is uploading to a converter. Our HEVC to MP4 converter and MOV to MP4 converter both handle iPhone HEVC files and output H.264 MP4 by default. Workflow:

1. Drag the file onto the page (works for files up to 5GB on the free plan)
2. Output is set to MP4 with H.264 video and AAC audio out of the box
3. Choose a quality preset (the "Best Quality" preset matches source bitrate, "Smallest File" cuts it about 30%)
4. Convert and download

The conversion happens server-side so it doesn't drain your phone's battery, and the output is universally compatible MP4 (H.264 + AAC). On a typical 1-minute 4K iPhone clip the round trip takes under a minute.

For batch conversion (a vacation's worth of clips, say), our batch processing workflow lets you queue dozens of files at once.

Method 2: FFmpeg (Best Quality Control)

If you have FFmpeg installed (brew install ffmpeg on Mac, winget install Gyan.FFmpeg on Windows, apt install ffmpeg on Linux), the command line gives you fine-grained control.

The Quality-Preserving Conversion

ffmpeg -i IMG_1234.MOV -c:v libx264 -crf 18 -preset slow -pix_fmt yuv420p -c:a aac -b:a 192k output.mp4

What each part does:

• -c:v libx264: Re-encode video to H.264. This is required since the codec is changing. There's no "copy" shortcut for HEVC-to-H.264.
• -crf 18: Constant Rate Factor 18 is visually lossless for most viewers. CRF 23 is the FFmpeg default and acceptable for general use, CRF 18 is "you need a side-by-side comparison to see a difference."
• -preset slow: Slower preset means better compression efficiency (smaller file at same quality). medium is the default. slow is worth it for archival; fast if you're in a hurry.
• -pix_fmt yuv420p: Forces 8-bit 4:2:0 chroma sampling. iPhone HEVC is sometimes 10-bit (especially in HDR or Dolby Vision modes). 10-bit H.264 exists but isn't widely supported. Convert to 8-bit unless you have a specific reason not to.
• -c:a aac -b:a 192k: AAC audio at 192 kbps. iPhone audio is already AAC, so this re-encode is mild. You could use -c:a copy to skip re-encoding entirely if the source AAC is already at a reasonable bitrate.

The Hardware-Accelerated Version

On a Mac with Apple silicon, you can use the hardware H.264 encoder for 5-10x faster conversion:

ffmpeg -i IMG_1234.MOV -c:v h264_videotoolbox -b:v 8M -pix_fmt yuv420p -c:a aac -b:a 192k output.mp4

h264_videotoolbox uses Apple's Video Toolbox API, which talks directly to the hardware encoder. Quality is slightly worse than libx264 at the same bitrate, but the speed is dramatic. For a 4K 60fps clip, libx264 with -preset slow might take 10 minutes. videotoolbox finishes in under 60 seconds.

Windows users with Nvidia GPUs can use -c:v h264_nvenc, AMD users -c:v h264_amf, Intel users -c:v h264_qsv. Same idea, hardware-accelerated H.264 encode.

Stripping HDR (Important for iPhone Videos)

iPhones since the 12 Pro record Dolby Vision HDR by default. If you're converting an HDR HEVC file to standard H.264, the colors will look washed out unless you tonemap explicitly:

ffmpeg -i IMG_HDR.MOV -vf "zscale=t=linear:npl=100,format=gbrpf32le,zscale=p=bt709,tonemap=tonemap=hable:desat=0,zscale=t=bt709:m=bt709:r=tv,format=yuv420p" -c:v libx264 -crf 18 -c:a aac output.mp4

This is verbose but it's the standard FFmpeg HDR-to-SDR pipeline. The zscale filter does color space conversion, tonemap=hable is a tone mapping operator that preserves highlight detail. Skipping this on an HDR source produces noticeably flat, undersaturated results. We covered the deeper version of this workflow in our HDR to SDR conversion guide.

Photo by Orlando Allo on Pexels

Method 3: macOS Built-In Tools

If you're on a Mac and don't want to install anything, two options.

QuickTime Player

Open the HEVC file in QuickTime, choose File > Export As > 1080p (or 4K, etc.). QuickTime exports H.264 in an .mov container. The output is reliable H.264, but you don't have control over CRF or bitrate, and QuickTime tends to use generous bitrates (large files).

Photos App (for camera roll videos)

Plug your iPhone into your Mac, open Photos, drag the video out to your desktop. By default, Photos converts HEVC to H.264 during export if the destination ("Most Compatible" setting in iPhone Camera settings) requires it. Caveat: this happens at iPhone-chosen quality, not yours.

For control, use FFmpeg or our online converter.

Bitrate Cheat Sheet for HEVC to H.264

When you transcode HEVC to H.264, the H.264 file will be roughly 2x larger at equivalent visual quality. Plan for this. Approximate bitrate targets:

These match Apple's documented iPhone recording bitrates and YouTube's recommended H.264 upload bitrates. CRF-based encoding usually gets you in the right neighborhood without picking a target bitrate manually, but if you need a specific file size, two-pass encoding is the right approach (see our video bitrate explainer).

Quality vs. File Size: What to Expect

A representative example. A 60-second 4K 30fps iPhone clip recorded in HEVC:

• Source HEVC: 380 MB
• H.264 at CRF 18 (slow preset): 720 MB
• H.264 at CRF 20 (medium preset): 480 MB
• H.264 at CRF 23 (fast preset): 280 MB

CRF 20 is the sweet spot for most cases: file size close to source, quality essentially identical at normal viewing distance. CRF 18 is overkill unless you're planning further editing. CRF 23 introduces visible compression artifacts in dark scenes and high-motion sequences, but it's fine for social media uploads where the platform will re-encode anyway.

Common Pitfalls

Audio out of sync after conversion

Usually a frame rate issue. iPhone Slo-Mo footage is 240fps in HEVC. If your converter doesn't handle the variable frame rate properly, audio drifts. Force constant frame rate:

ffmpeg -i input.mov -c:v libx264 -crf 20 -r 30 -vsync cfr -c:a aac output.mp4

The -r 30 -vsync cfr pair forces 30 fps constant frame rate. If audio is still drifting, our audio sync fix guide covers deeper diagnostics.

Output is bigger than source

Expected. HEVC is roughly 2x more efficient than H.264 at equal quality. If you're converting for compatibility, accept the file size increase. If file size is critical, lower CRF (raise the number to 23-26) or reduce resolution.

Colors look "off"

Almost always missing tone mapping when converting HDR/Dolby Vision iPhone footage to SDR H.264. Use the zscale + tonemap filter chain shown above, or use a converter that handles this automatically. Our HEVC to MP4 tool detects HDR metadata and applies tone mapping when needed.

"Profile" warning in older players

By default, FFmpeg encodes H.264 to "high profile," which most modern devices handle. If you're targeting truly old hardware (a 2013-era smart TV or budget Android phone), drop to baseline profile:

ffmpeg -i input.mov -c:v libx264 -profile:v baseline -level 3.0 -crf 23 -c:a aac output.mp4

This produces larger files but plays on hardware that doesn't support high-profile features like 8x8 transforms.

When NOT to Convert

A counterargument worth considering: don't convert if the destination supports HEVC. Modern uploads to YouTube, Vimeo, Instagram, and TikTok all accept HEVC. Modern Macs and iPhones obviously play it. If your audience is "people on Apple devices," HEVC is fine and the file is half the size.

Convert when:

• Windows users need to play it without paid extensions
• You're publishing to a CMS that doesn't transcode (some WordPress setups, hand-rolled video pages)
• You're editing in older software
• You're archiving for "decades from now" compatibility (H.264 will outlast HEVC's relevance window)

Don't convert when:

• The destination accepts HEVC
• Storage matters more than universal compatibility
• You'll re-encode again later (each transcode introduces some loss)

FAQ

Is converting HEVC to H.264 lossy?

Yes. Both are lossy codecs, and re-encoding from one to the other compounds the loss. At CRF 18-20 the loss is hard to see at normal viewing distances, but it's there. If you have the original camera file, you can't get back to it from a converted H.264.

Can I batch convert all my iPhone videos at once?

Yes. Our batch conversion tool handles up to 100 files per upload on paid plans. For local FFmpeg batch conversion:

for f in *.MOV; do ffmpeg -i "$f" -c:v libx264 -crf 20 -pix_fmt yuv420p -c:a aac "${f%.MOV}.mp4"; done

How do I stop my iPhone recording HEVC entirely?

In iPhone Settings, go to "Camera," tap "Formats," select "Most Compatible." This makes the camera record H.264 in MP4 directly, no conversion needed. The trade-off is roughly 2x larger files for the same visual quality.

Does iCloud Photos convert HEVC automatically?

Sort of. When you download a photo or video from iCloud.com to a non-Apple device, iCloud transcodes HEVC to H.264 for you. But when you sync photos via the iCloud Drive folder on Windows, you get the original HEVC. The behavior is inconsistent enough that many people just convert manually.

What's the difference between HEVC and H.265?

Nothing. HEVC (High Efficiency Video Coding) is the standards body name. H.265 is the ITU-T name for the same codec. Apple uses "HEVC" in its UI. Most encoders use "h.265" or "x265." Same thing.

Final Thoughts

HEVC is the future of video compression except for the part where the present is still H.264. For another five to ten years, H.264 will remain the format that "just plays" without questions. AV1 is gaining ground but adoption is slow and hardware decoders are still rolling out. HEVC sits in an awkward middle: better than H.264, less universal than H.264, more complex licensing than AV1.

For iPhone users, the practical takeaway is: keep recording in HEVC for storage efficiency, convert to H.264 when sharing with non-Apple users or uploading to platforms that haven't fully embraced HEVC. The conversion is a one-time cost (a couple of minutes per file) that saves hours of "why won't this play?" support questions later.

When in doubt, MP4 with H.264 video and AAC audio is still the format that plays everywhere. That hasn't changed in a decade and isn't changing soon.