Convert HEVC to H.264 on Windows

iPhone AirDrops and newer camera exports often arrive as HEVC (H.265) MOV or MP4 files. Older Windows laptops, some LMS tools, and strict upload pipelines expect H.264 instead. You notice when Movies & TV shows a codec error, when SharePoint preview fails, or when a client on an older PC cannot scrub the timeline. Converting HEVC to H.264 locally fixes playback; output files are usually larger unless you trim or lower resolution.

HEVC vs H.264

HEVC compresses more efficiently than H.264 at the same visible quality. H.264 remains the safe choice for unknown recipients and corporate machines that lag on codec updates.

	HEVC (H.265)	H.264 (AVC)
Common source	iPhone HEVC, newer cameras	Web uploads, broad Windows playback
File size at same quality	Usually smaller	Usually larger
Compatibility	Good on recent devices	Universal on Windows apps
Best first step	Re-encode to H.264 when playback fails	Already widely accepted

In practice, HEVC appears in phone clips from Mac colleagues, drone exports, and screen recordings using efficiency presets. H.264 is what you send for Teams, Slack, CMS uploads, and client review on mixed hardware.

See H.264 vs H.265 codecs for when keeping HEVC makes sense. For container changes without codec swaps, see MOV to MP4 on Windows .

Export in Clipchamp

Clipchamp (built into Windows 11) re-encodes HEVC imports to H.264 on export when you need one or two clips.

1. Open the HEVC file in Clipchamp.
2. Trim the timeline to remove dead air.
3. Export at 1080p (or 720p for chat attachments).

Export produces H.264 video. Expect larger files than the HEVC original unless you choose 720p.

Situation	Export choice
Client on older hardware	1080p export
Teams or ticket attachment	720p after trim
Portal with a hard MB cap	720p, then compress further

Clipchamp does not batch a folder of HEVC clips with CRF control. Use FFmpeg or GetCompress for that.

Convert with FFmpeg

FFmpeg in PowerShell handles batch HEVC folders. Install with winget:

winget install --id Gyan.FFmpeg -e

Standard re-encode:

ffmpeg -i input.mov -c:v libx264 -crf 22 -preset medium `
  -c:a aac -b:a 128k -movflags +faststart output.mp4

Check the source codec:

ffprobe -v error -select_streams v:0 -show_entries stream=codec_name -of csv=p=0 input.mov

Batch MOV files in a folder:

mkdir h264-out
Get-ChildItem *.mov | ForEach-Object {
  ffmpeg -i $_.Name -c:v libx264 -crf 22 -preset medium `
    -c:a aac -b:a 128k -movflags +faststart `
    "h264-out\$($_.BaseName).mp4"
}

Symptom	Likely cause	Fix
Slow encode on laptop	Software libx264	Use -preset veryfast for drafts
Huge output	HEVC was very efficient	Lower -crf or export 720p
No audio	Exotic audio track	Add -c:a aac explicitly

For AVCHD already encoded as H.264, you may only need remux; see AVCHD to MP4 on Windows .

Using GetCompress

GetCompress fits recurring convert HEVC to H.264 on Windows work when iPhone clips arrive daily and teammates on older PCs need playable files.

Drop HEVC MOV or MP4 files into the app. Choose H.264 output, set resolution and quality, or use target file size when SharePoint states a limit. Trim in the preview before export when the recording includes idle time at the start.

Useful workflow pieces in GetCompress:

• Batch queue: process an imports folder of HEVC clips without opening each in Clipchamp.
• Presets: save “1080p H.264 client” or “720p H.264 Teams” and reuse weekly.
• Preview and trim: confirm UI text stays readable before sending a screen recording.
• Folder monitoring: watch a sync folder and auto-transcode new HEVC phone clips when they appear.
• Local processing: keep unreleased demos on your machine instead of uploading HEVC originals online.
• Target file size: balance compatibility and megabytes when the portal caps uploads.

After conversion, if the H.264 file is still too large, lower quality or resolution in the same window rather than starting over in PowerShell.