Export & Codecs

Convert HEVC to MP4 [2026]: Remux vs H.264, 5 Tools

Convert HEVC to MP4 [2026]: Remux vs H.264, 5 Tools

To convert HEVC to MP4 from an iPhone clip, first decide whether you need a new container or a new codec. Moving the video into an MP4 wrapper (a remux) keeps the HEVC stream exactly as it is. Making an H.264 file that plays on older TVs, browsers and editors means a full re-encode. No tool, free or paid, can skip that step.

This comparison sorts five routes by what they do to the video stream: FFmpeg, HandBrake, VLC, QuickTime Player with iMovie, and online converters. HandBrake’s own news page lists version 1.11.2 as the current release, and the Apple, FFmpeg and VideoLAN pages we checked on November 18, 2026 agree on the core rule. Our earlier five-method guide to converting MOV to MP4 covers the click-by-click basics. This piece goes deeper on the codec question that decides whether your file looks identical or gets softer.

Tables come first, explanation second. Where a vendor publishes a spec or a price, we name the source and the date checked. Where nobody publishes a number (speed, for example), we say so and give you a way to measure it on your own footage instead of inventing one.

Remux vs re-encode: what actually changes in the file

OperationVideo streamAudio streamQuality effectResult plays on
Remux (stream copy) MOV to MP4Copied untouched (HEVC stays HEVC)Copied untouchedNone, bit-identical streamsOnly devices that already decode HEVC
Re-encode to H.264 in MP4Decoded, then compressed again as H.264Usually AAC againSome loss, controlled by the quality settingNearly everything
Re-encode to HEVC in MP4Decoded, then compressed again as HEVCUsually AAC againSome loss, no compatibility gainSame as the source, so rarely useful

The sources we checked state the distinction the same way. A remux changes the container without changing the encoded streams, so it cannot turn HEVC video into H.264. Producing a broadly compatible H.264 MP4 requires a re-encode, no matter which application performs it. FFmpeg, VideoLAN and HandBrake documentation all describe the two operations as separate jobs.

MOV and MP4 are both containers built on the same underlying box structure. That is why a remux is so fast. The tool copies the compressed frames from one box layout into another, and a short clip can finish in seconds. A re-encode has to decode every frame and compress it again, which is why it takes longer and why it can cost quality. Our MP4 vs MOV comparison goes through the container differences in detail, including why the extension alone never sets quality.

A remux also carries along everything else that lives in the container. iPhone clips store portrait orientation as a rotation flag instead of rotated pixels, and they often use a variable frame rate. A remux preserves both quirks exactly. Most modern players honor the rotation flag, but a few editors and web tools ignore it, and a variable-frame-rate clip can drift against separate audio. A re-encode lets you fix both, because the encoder writes fresh frames at whatever rotation and frame rate you ask for.

Check what is inside your iPhone MOV first

An iPhone MOV can hold either HEVC or H.264 video, depending on the camera format setting at the time of recording. Apple’s setting names are High Efficiency and Most Compatible, and you can check which one a phone uses in Settings under Camera, then Formats. The phone lineup Apple lists today includes iPhone 17, iPhone 17e, iPhone Air, iPhone Duo, iPhone 18 Pro and iPhone 18 Pro Max (checked on apple.com on November 17, 2026), so you may be dealing with several generations of files in one library.

Do not guess from the file extension. Probe the file instead. FFmpeg ships with a companion tool called ffprobe, and this command prints the video codec, the codec tag, the frame rate and the pixel format in a few lines.

ffprobe -v error -show_entries stream=codec_name,codec_tag_string,width,height,r_frame_rate,pix_fmt -of default=nw=1 input.mov

If the video line says hevc, you have HEVC. If it says h264, a remux alone gives you a universally playable MP4 and no re-encode is needed. That single check saves most people an unnecessary quality hit. If the pixel format line shows a 10-bit format, the clip is likely an HDR recording, which changes the re-encode advice later in this article.

Convert HEVC to MP4: the five routes side by side

Spec (checked Nov 18, 2026)FFmpegHandBrakeVLCQuickTime Player / iMovieOnline converters
PriceFree, open sourceFree, open sourceFree, open sourceBuilt into macOS (QuickTime Player is not sold standalone)Free tier plus paid plans
PlatformsWindows, macOS, Linux (command line)Windows, macOS, LinuxDesktop, Android, iOS and iPadOS appsMac onlyAny browser
Newest version in our sources9.0.2 and 8.1.3 in the repository, 9.1 branch in preparation1.11.23.0 branch (reportedly 3.0.23, January 2026)Not listedNo versions published
Lossless remux to MP4Yes, with stream copyNo, video is always encoded againLimited, not documented as a copy workflowNo documented MP4 remuxRarely documented, one service lists a Copy option
H.264 re-encodeYes, full controlYes, presets and slidersYes, through Convert/Save profilesiMovie re-exports, QuickTime offers presetsYes, settings usually hidden
Quality controlCRF, preset, profile, tagsConstant quality slider, encoder presetsBasic profile editingQuality menu in iMovieOften none, or a size slider
Batch conversionYes, via shell loopYes, via queueAwkwardOne file at a time in QuickTimeLimited by free daily allowance
Files leave your machineNoNoNoNoYes, uploaded to a third party
Handles HDR iPhone clipsYes, if you set flags yourselfPartly, check tone mapping optionsNot designed for itiMovie handles it inside its own projectUnclear, most do not say
Learning curveSteep for first useModerateLow, but the menu is hiddenLowest on a MacLowest anywhere
Best single jobFast lossless remux, scripted batchesPredictable H.264 re-encode with a GUIFallback when it is already installedQuick Mac conversions and editsOne small file on a machine you cannot install on

Two cells deserve a flag. The VLC and QuickTime rows reflect gaps in the documentation, not proven failures. The VideoLAN and Apple pages we read describe those apps as playback and basic-editing tools, and neither one documents a dependable HEVC-to-H.264 workflow. We treat that silence as a reason to prefer FFmpeg or HandBrake when the job matters.

The “Files leave your machine” row is the one creators skip. Camera footage often shows faces, addresses and client material. An online service has to receive the whole file before it can convert it, so a one-off privacy decision hides inside what looks like a harmless drag-and-drop.

FFmpeg: the fastest way to remux, and a precise H.264 encoder

FFmpeg is a free, open-source multimedia framework, and it is the engine under several of the other tools in this article. The official site lists FFmpeg 8.1 “Hoare” with a March 16, 2026 news entry. The project repository we checked on November 18, 2026 reportedly shows 9.0.2 and 8.1.3 maintenance releases from around October 2026 and an active 9.1 branch, with FFmpeg’s generated source documentation reflecting code changes through November 17. Treat 9.1 as in development, not as a release you can download today.

The remux command is one line. It copies the streams and rewrites only the container.

ffmpeg -i input.mov -map 0:v:0 -map 0:a:0 -c copy -tag:v hvc1 -movflags +faststart output.mp4

Three flags carry the weight here. The -map pair keeps the first video and audio stream and drops the extra data tracks that iPhone MOV files carry, such as metadata and timecode tracks, which the MP4 muxer can reject. The -tag:v hvc1 flag matters for HEVC, because Apple’s players expect the hvc1 sample entry and an MP4 with the alternative tag can refuse to play in QuickTime or on an iPhone even though the video data is fine. The -movflags +faststart flag moves the index to the front of the file so web players start sooner. If the source is already H.264, drop the tag flag.

For the compatibility route, re-encode the video to H.264 and the audio to AAC.

ffmpeg -i input.mov -map 0:v:0 -map 0:a:0 -c:v libx264 -crf 18 -preset slow -pix_fmt yuv420p -c:a aac -b:a 192k -movflags +faststart output.mp4

CRF 18 is our suggested starting point for footage you plan to edit further, and CRF 20 to 23 is the usual range for files you only plan to upload or share. These are practical starting values, not vendor-published benchmarks. Lower numbers keep more detail and make bigger files. The slower preset spends more encoding time to shrink the file at the same visual quality.

For a folder of clips, wrap the remux in a loop. This version writes the MP4 files into a separate folder and never touches the originals.

mkdir -p mp4
for f in *.MOV; do
  ffmpeg -i "$f" -map 0:v:0 -map 0:a:0 -c copy -tag:v hvc1 -movflags +faststart "mp4/${f%.MOV}.mp4"
done

Render settings

SettingRemux for HEVC-capable targetsRe-encode for maximum compatibility
ContainerMP4MP4
Video codecHEVC, copied from sourceH.264 (libx264), High profile
ResolutionSame as sourceSame as source
Frame rateSame as sourceSame as source, constant if your editor drifts
Pixel formatSame as sourceyuv420p for SDR, tone-mapped for HDR
AudioCopiedAAC
Tag and indexhvc1 tag, faststartfaststart

FFmpeg has known rough edges. An official issue we found reports an HEVC decoder flush regression that affects active releases from 7.1 through 9.0. Another reports problems with the concat demuxer when audio carries priming samples, which matters if you join several iPhone clips in one command. These are single-source reports, so check the issue tracker for your build before relying on them. They also argue for testing one clip before you convert a whole card.

Audio deserves a line of its own. iPhone MOV files normally carry AAC audio, and AAC is a native fit for MP4, so a remux copies it untouched and there is nothing to decide. In a re-encode you can still choose to copy the audio and only touch the video, which avoids a second generation of lossy audio compression. FFmpeg does this with -c:a copy, and HandBrake exposes an audio passthrough option for compatible tracks. If your target needs a specific audio codec, convert it. Otherwise leave it alone.

File size is the other trade you should expect. HEVC is the more efficient codec, so an H.264 re-encode at matching visual quality is normally larger than the HEVC original. That is the price of compatibility, and it is why archiving the original MOV and delivering an H.264 copy is better than replacing one with the other. Plan storage for both versions if you keep both, and budget the extra upload time when the H.264 copy goes to a client.

HandBrake 1.11.2: the GUI re-encoder that never copies video

HandBrake is a free, open-source transcoder for Windows, macOS and Linux. The release notes announce 1.11.2, 1.11.1 and 1.11.0 as successive releases, with 1.11.2 the newest. The project does not publish a fixed support lifecycle for individual versions, so the practical rule is simple: install the newest one.

HandBrake writes a new video stream every time. It decodes your HEVC and compresses it again, so it is the wrong tool when you want a bit-identical remux. It is the right tool when you want H.264 and prefer sliders to flags. The workflow takes four steps:

  1. Open the MOV and pick a general-purpose MP4 preset that matches the source resolution.
  2. On the Video tab, set the encoder to H.264 and use the constant quality slider rather than a fixed bitrate.
  3. Set frame rate to Same as source and choose Constant, which sidesteps most audio drift in editors when the iPhone clip uses variable frame rate.
  4. Pick an output name ending in .mp4, add the job to the queue, and run the batch.

The queue is the real advantage over a one-off converter. You can load a whole folder, apply one preset and walk away. HandBrake also exposes hardware encoders on supported machines, which cuts encode time at some cost in file efficiency compared with the software encoder. The project’s documentation describes which hardware options each platform offers, and we did not find a vendor-published speed table to quote.

HDR iPhone footage needs a decision. If the final video goes to SDR platforms, an H.264 SDR output needs tone mapping or the picture can look flat and grey. If you skip the conversion and keep the HDR clip in HEVC, a remux preserves the HDR metadata that the container carries. FFmpeg’s issue tracker also shows ongoing Dolby Vision muxing work, and the sources do not establish what has shipped, so verify a sample before batch-processing HDR clips.

VLC: a fallback that is already on the machine

VLC media player is free and open source, and VideoLAN’s site presents desktop, Android and iOS-iPadOS-tvOS products. The VideoLAN code host lists the 3.0.22 tag as the 23rd release of the 3.0 branch, and reports we found put 3.0.23 in January 2026, while one weekly check listed 3.0.24. The sources conflict on the exact newest number, so we name the branch and leave it there.

VLC can convert through Media, then Convert / Save. You add the file, choose a video profile (the H.264 plus AAC or MP3 MP4 profile is the one you want), set a destination and start. It works, and for one short clip it is quick. The VideoLAN pages describe VLC as a player and framework, but none of the pages we read document a dependable HEVC-to-H.264 conversion workflow.

Three limits show up in practice. The conversion dialog has few controls, so you cannot easily set a constant quality target. Progress feedback is thin, and a failed conversion sometimes produces an empty or tiny file with no error. And the same iPhone playback quirks that affect other tools, such as rotation metadata, may carry through without warning. Use VLC when it is the only thing installed. Move to HandBrake or FFmpeg the moment you need predictable results.

QuickTime Player and iMovie: the Mac-native path

QuickTime Player is bundled with macOS and is not sold as a standalone product. Apple’s QuickTime Player guide for version 10.5 documents trimming and opening movies, and we saw help pages updated in September and October 2026. We found no Apple page that documents QuickTime Player as an HEVC-to-H.264 converter or as a remux tool for iPhone files, so it is a playback and trimming tool first.

iMovie is the practical Mac option for HEVC and ProRes sources because it re-exports the video as a new file rather than relabeling the container. That makes it a re-encode, with the usual trade: a small quality cost for broad compatibility. If you already live in iMovie, exporting from it is easier than learning a command line. If you plan to batch dozens of clips, it is slower than HandBrake or FFmpeg.

One related Apple change affects screen recordings, not iPhone files. Apple’s documentation describes the newer Screenshot recording options on macOS Tahoe 26 or later, where SDR capture uses H.264 for compatibility and HDR capture uses HEVC. Apple also still documents the New Screen Recording command in QuickTime Player. If you record the Mac screen and hit an HEVC file you cannot open elsewhere, check which of those two capture paths made it.

Do not forget Apple’s own transfer setting. In Photos settings on the iPhone, the Transfer to Mac or PC option can convert HEVC to a compatible format automatically as you move the files. It is a re-encode you did not have to start, and it hides the decision, so check the setting before you assume a file arrived untouched.

Online converters: free-tier limits and the upload trade-off

Browser converters exist for one-off jobs on a machine where you cannot install software. The sources we reviewed confirm they convert common containers and codecs. They do not confirm that CloudConvert, Convertio, Zamzar or FreeConvert offers a documented lossless MOV-to-MP4 remux mode. Assume an H.264 re-encode unless the service says it copies the video stream, and assume your file is uploaded to a third-party server.

Service (checked Nov 2026)Free tier as reportedPaid plans as reportedCopy / remux option
FreeConvert1 GB maximum file, 20 conversion minutes per day, files deleted after 8 hoursBasic $12.99/mo, Standard $24.99/mo, Pro $29.99/moA Copy option reuses the video stream when the output format supports it
ConvertioFree tier exists, limits not confirmed herePro $44.99/mo or $25.99/mo billed yearlyNot documented in our sources
CloudConvertReportedly about 10 conversions a dayCredit packages and subscriptionsNot documented in our sources
ZamzarReportedly about 2 files per 24 hours and about 50 MB per uploadTiered plans reportedNot documented in our sources
Online-ConvertFree tier reportedPay-as-you-go credits and a monthly plan reportedNot documented in our sources

The FreeConvert and Convertio figures come from third-party comparison pages dated November 2026, because the vendors’ own pricing pages were not available to our check. Confirm them on the vendor’s site before you pay. We reproduce them here as reported numbers, not as vendor commitments.

The free daily caps matter more than they look. An iPhone clip a few minutes long can exceed a 50 MB upload cap on its own. A 4K clip is large enough to hit the 1 GB ceiling quickly, and upload time on a home connection adds to the wait before the conversion even starts. If the total shoot is more than a handful of clips, the free tier stops being free in time terms.

Before you upload anything, run a short checklist. Confirm the file is under the service’s size cap. Read how long the service keeps the file (FreeConvert is reported to delete after 8 hours, and other services differ). Make sure the clip has no client-confidential material. And look for any option that says copy or passthrough for the video stream, because that is the only setting that avoids a silent re-encode.

What each route costs in money and time

RouteMoneyHidden costSetup time
FFmpeg$0Command-line learning, flag mistakes can silently re-encodeMinutes once installed
HandBrake 1.11.2$0Always re-encodes videoMinutes
VLC$0Sparse controls, unclear failuresAlmost none if installed
QuickTime Player / iMovie$0 with a MacMac-only, one file at a timeNone
FreeConvert free tier$0 up to 20 minutes a dayUpload time, third-party storage for up to 8 hoursNone
FreeConvert paid$12.99 to $29.99 a month as reportedRecurring cost for a one-off jobNone
Convertio paid$25.99 to $44.99 a month as reportedPriciest of the groupNone

The money column is almost flat at zero, so choose on time and control. The one scenario where paying makes sense is a creator who occasionally needs a converter on a locked-down work laptop and does not want to ask IT for software. For everyone else, the free local tools beat the paid online ones on speed, privacy and control.

Benchmarks: what the sources publish and what they leave out

We looked for conversion-speed and quality benchmarks across the FFmpeg, HandBrake, VideoLAN and Apple documentation and found none that compare a remux and an H.264 re-encode of the same iPhone clip. The honest summary is that vendors publish no figures, and third-party blog numbers vary with hardware, so we do not quote any. What the documentation does support is a ranking of behavior.

QuestionWhat the sources supportSource type
Is a remux faster than a re-encode?Yes, because streams are copied and not decoded and compressed againFFmpeg documentation
Does a remux change quality?No, the encoded streams are untouchedFFmpeg and VideoLAN documentation
Does a re-encode change quality?Yes, normally some loss, controlled by the encoder settingFFmpeg and HandBrake documentation
Can any tool remux HEVC into H.264?No, a codec change always means re-encodingFFmpeg, VideoLAN and Apple pages
Which hardware encoder is fastest?Not published, depends on your machineHandBrake documentation lists options only

You can build your own benchmark in five minutes. Pick one representative clip, run the remux command and the re-encode command with the shell’s time prefix, and compare the output file sizes. Then play both outputs on the weakest device you care about. The result tells you more than any published table, because the iPhone clip, your CPU and your target device are the variables that matter.

time ffmpeg -i clip.mov -c copy -tag:v hvc1 remux.mp4
time ffmpeg -i clip.mov -c:v libx264 -crf 20 -preset medium -c:a aac reencode.mp4
ls -l clip.mov remux.mp4 reencode.mp4

For visual quality, scrub both outputs at the same frames, with extra attention to dark gradients and fast motion, where H.264 shows banding and blocking first. If you need a number, FFmpeg’s SSIM and VMAF filters can score an output against the source, but the scores only hold for the clip and settings you ran. Keep your own log of results per phone and per preset, and the next conversion becomes a lookup instead of an experiment.

Six real-world examples

1. A vlogger sending raw clips to an editor on Windows. The editor’s older Premiere install struggles with HEVC. The vlogger runs one HandBrake batch to H.264 MP4 and sends the folder. The files are bigger than the HEVC originals, but they scrub smoothly on the editor’s machine, and the editor stops asking for re-sends.

2. A wedding videographer on a Mac with a Final Cut library. Final Cut reads the iPhone MOV natively, so no conversion is needed for editing. The client wants a web preview, so the videographer exports one H.264 MP4 from the editor and leaves the camera originals alone. The lesson is that sometimes the right conversion is none.

3. A podcaster posting clips to a CMS that rejects MOV. The CMS accepts MP4 but not MOV, and the clips are H.264 because the phone was set to Most Compatible. A remux with FFmpeg is enough. It takes seconds, changes nothing in the picture, and the upload works.

4. A teacher on a locked school laptop. No installs are allowed, and the clip is small. An online converter is the only option. The teacher checks that the clip is below the free-tier file cap, accepts the upload, and deletes the source from the converter afterward where the service allows it.

5. A streamer cutting highlights from phone footage. The streamer needs the phone clip to match the frame rate of the stream recording. A variable-frame-rate iPhone clip drifts against audio in the editor, so the streamer re-encodes with a constant frame rate in HandBrake. For the stream’s own recording, our guide to OBS recording settings explains which encoder to pick.

6. A small studio joining an intro to phone footage. The studio renders an intro clip and wants to join it to iPhone clips without a second re-encode. Joining without re-encoding only works when codec, resolution, frame rate and pixel format match. Vipid’s intro themes page lists resolution, length and frame rate for each theme, which gives you the numbers to match before you stitch.

Pros and cons of each route

RouteProsCons
FFmpegOnly true lossless remux, scriptable, full encoder control, no uploadCommand line, easy to mistype a flag, needs the hvc1 tag for Apple playback
HandBrakeClear GUI, batch queue, presets, free on three platformsAlways re-encodes video, HDR handling needs checking
VLCProbably already installed, no costFew controls, weak failure reporting, no documented HEVC workflow
QuickTime / iMovieBuilt into the Mac, simple exportNo documented remux, one file at a time, Mac only
Online convertersNo install, works in any browserUpload privacy, daily caps, usually a silent re-encode, paid tiers cost more than local tools

The pattern is consistent. Control and privacy sit with the local tools, and convenience sits with the online ones. Between the two local leaders, FFmpeg wins on lossless speed and HandBrake wins on comfort, and they do not compete for the same job. Many creators end up using both, FFmpeg for the quick remux and HandBrake for the occasional H.264 delivery file.

Use-case recommendations

  • You need a lossless MP4 wrapper and the target plays HEVC: use the FFmpeg remux with the hvc1 tag. It is the fastest route and changes no pixels.
  • You need an old TV, an old browser or an old editor to play the file: re-encode to H.264 with HandBrake or FFmpeg, and test on the weakest device first.
  • You edit on a Mac and never leave Apple’s tools: keep the MOV for editing and export from iMovie or your editor at the end.
  • You have a folder of clips from several shoots: use the HandBrake queue or an FFmpeg shell loop so every file gets the same settings.
  • You have one tiny file and no install rights: use an online converter after checking its file-size cap and where the file goes.
  • You shoot HDR and publish to an SDR platform: do a short test conversion with tone mapping and compare it to the source before processing the batch.
  • You are archiving originals: keep the untouched MOV, and make MP4 delivery copies from it instead of replacing it.

Migration guide: moving from MOV-only to an MP4 workflow

Most creators drift into conversions one panic at a time. A tidy migration replaces the panic with a repeatable setup. Follow these steps once and later jobs take minutes.

  1. Audit your sources. Run the ffprobe command on one clip from each phone you shoot with. Write down the codec, frame rate and pixel format for each.
  2. Decide your delivery format. If every destination plays HEVC, plan to remux. If any destination does not, plan to re-encode to H.264 and say so in your file naming.
  3. Set the phone once. If compatibility matters more than storage, switch the camera format to Most Compatible so new clips are H.264 from the start and need no re-encode.
  4. Install the tools. Put FFmpeg and HandBrake 1.11.2 on the machine you edit on, and leave online converters for emergencies.
  5. Save a preset. In HandBrake, save the exact H.264 settings you tested. In FFmpeg, save the command in a text file or a shell script.
  6. Convert a copy. Never overwrite the original MOV. Write MP4 files to a separate folder, and keep the originals until the project is delivered.
  7. Spot-check the output. Play the first, middle and last clips on your slowest target device and check audio sync, rotation and color.
  8. Document the rule. A one-line note such as “remux if H.264, re-encode if HEVC” keeps a team consistent.

If you are moving off an online converter, the main change is trust in your own machine. A local tool needs no upload, has no daily cap and gives you the same result every time. If you are also choosing a delivery codec for new work, the codec comparisons in our export and codecs section cover H.264, HEVC, AV1 and the container choices around them. For title cards and intros that sit alongside phone footage, the Vipid intro maker renders them as video files, so the same codec-matching rules apply when you join them.

Verdict: remux when you can, re-encode when you must

Start with the ffprobe check. If the video is H.264, remux with FFmpeg and stop, because nothing is gained by re-encoding. If the video is HEVC and every device on your delivery list plays it, remux with FFmpeg and the hvc1 tag. If any device cannot play HEVC, re-encode to H.264, and use HandBrake 1.11.2 unless you are comfortable with FFmpeg flags.

SituationPickReason
Source is H.264 alreadyFFmpeg remuxNo codec change needed, no quality cost
Source is HEVC, HEVC-capable targets onlyFFmpeg remux with hvc1 tagLossless and fast
Source is HEVC, older targets involvedHandBrake or FFmpeg re-encode to H.264Only way to reach old devices
Mac user, light needsiMovie exportAlready installed, simple
One file, no install rightsOnline converterLast resort, accept the upload

The data we could verify supports one firm conclusion and leaves one open question. The firm conclusion is that a remux is lossless and a codec change always costs a re-encode. The open question is speed and exact quality on your hardware, where no vendor publishes figures. Run the five-minute test above and let your own clip settle it.

A last point on keeping options open. Software versions move quickly, and the numbers in this article reflect what the vendors’ pages and repositories showed when we checked them. HandBrake and FFmpeg both publish release notes, and a new build can change defaults, fix a decoder bug or add hardware support. When a conversion that worked last month starts producing odd results, check the release notes for your build before you blame the clip. Re-run the one-clip test from the benchmark section with the new version and compare it to the old output.

Finally, remember that conversion is a delivery step, not an editing step. Cut, color and mix in the format your editor handles best, and convert once at the end. Every extra generation of lossy compression adds a little damage, and the cleanest MP4 is the one that went through exactly one H.264 encode or none at all.

Common questions

Can I convert HEVC to MP4 without losing quality?

Yes, if the target plays HEVC. A stream-copy remux with FFmpeg keeps the HEVC video untouched inside an MP4 container. If you need H.264, you must re-encode, and some quality loss is normal even at a high quality setting.

Is renaming a .mov file to .mp4 a valid conversion?

No. Renaming changes the label, not the container structure. Some players cope, and others fail. A proper remux rewrites the container, and a codec change needs a re-encode.

Why does my HEVC MP4 not play on an iPhone or in QuickTime?

The likely cause is the sample tag. FFmpeg can write HEVC into MP4 with a tag Apple players reject. Rerun the remux with the hvc1 tag flag and test again.

Does HandBrake remux video?

No. HandBrake encodes the video into a new stream, so a conversion through it is always a re-encode. Use FFmpeg when you want a lossless copy into MP4.

Is it safe to use a MOV to MP4 converter free online?

It works for small, non-sensitive files. The service receives your whole video, and the free tiers carry daily and file-size caps. FreeConvert’s free tier is reported at 1 GB per file and 20 conversion minutes a day, so check current limits on the vendor’s page before you start.

Which is newer, HandBrake 1.11.2 or an FFmpeg 9.x build?

They are different projects with separate numbering. HandBrake 1.11.2 is the release the maker’s site announces, and FFmpeg’s repository shows 9.0.2 with a 9.1 branch in preparation. Neither number tells you which converts your clip better.

Should I change my iPhone to record H.264 instead of HEVC?

Only if compatibility matters more than storage. The Most Compatible setting records H.264 and avoids later re-encodes. High Efficiency saves space, and you convert only when a destination demands it.

More from the Vipid blog

Make it with Vipid

Jonah Reyes

Editing & Export Editor · Vipid Team

Jonah Reyes is the Editing & Export Editor at Vipid. He covers editing software, export settings and codecs, and the video specs of YouTube, Shorts, TikTok and Reels, plus OBS and screen recording. He builds Vipid’s spec tables from the platforms’ own documentation and re-checks them every 60 to 90 days, so the numbers in a guide match what the upload dialog actually accepts.

All articles by Jonah Reyes ›   How we check tools ›

Keep reading

AV1 vs HEVC [2026]: 30.6% Fewer Bits, 1 Vendor Test
Export & Codecs

AV1 vs HEVC [2026]: 30.6% Fewer Bits, 1 Vendor Test

Jonah Reyes·10 Nov 2026
AV1 vs H.264 [2026]: Smaller Files, 3 Conditions
Export & Codecs

AV1 vs H.264 [2026]: Smaller Files, 3 Conditions

Jonah Reyes·8 Nov 2026
WebM vs MP4 [2026]: 3 Codecs, 1 Safe Default
Export & Codecs

WebM vs MP4 [2026]: 3 Codecs, 1 Safe Default

Jonah Reyes·5 Nov 2026

Blog

Intros & Templates
Titles & Motion
Streaming
Editing & Export
AI Video

Vipid

About Vipid
Themes
News archive 2011–2016
Vipid Team

Editorial

Editorial policy
How we check tools
Corrections

Legal

Privacy policy
Terms of service
Making video intros since 2010.
The Vipid blog covers the tools behind them.