Export & Codecs

HandBrake vs FFmpeg MOV to MP4 [2026]: 1 Remux Command

HandBrake vs FFmpeg MOV to MP4 [2026]: 1 Remux Command

For most MOV files, the fastest route to an MP4 is not a conversion at all. FFmpeg can copy the video and audio streams into a new MP4 container in a few seconds, with zero quality loss, as long as the codecs inside are ones MP4 accepts. HandBrake is built around re-encoding, so it costs more time and a little quality, but it fixes the files that a straight copy cannot.

That split is the whole comparison, and it holds as of November 19, 2026. The HandBrake team announced HandBrake 1.11.2 as its newest release, and FFmpeg’s own news page lists 8.1 “Hoare” (March 16, 2026) as the most recent release headline. Both tools are open source projects with no price listed on the pages checked, so the choice comes down to what is inside your file and how many files you have.

This article covers one narrow job: turning a MOV into an MP4 with either tool. It does not rank every converter on the market. If you want the wider list of methods, the earlier guide on how to convert MOV to MP4 covers five of them. Here the question is HandBrake versus FFmpeg, and when each one wins.

The short answer: remux first, re-encode second

Try the remux before anything else. A remux changes the wrapper around your video and audio without touching the encoded streams. According to the FFmpeg and HandBrake pages checked on November 19, 2026, it is fast and preserves quality, but it only works when the streams are compatible with MP4. That condition is the only catch, and it is easy to test.

The FFmpeg command for a remux is a single line, and it appears on ffmpeg.org’s own documentation:

ffmpeg -i input.mov -map 0 -c copy output.mp4

If that finishes without errors and the result plays in the player or editor you care about, you are done. You kept every pixel, every audio sample, and the original file’s quality. Nothing in HandBrake can beat that, because HandBrake decodes the video and encodes it again.

When the remux fails or the MP4 will not play, switch to a re-encode. FFmpeg’s documentation states the rule plainly: re-encoding is required when the existing video and audio codecs are not compatible with MP4. At that point both tools do the same job, and HandBrake wraps it in a graphical window while FFmpeg keeps it on the command line.

Here is the decision in one table. Checked November 19, 2026 against the FFmpeg and HandBrake official pages.

Your MOV containsBest first moveWhy
H.264 video and AAC audioFFmpeg remuxBoth streams are already MP4-friendly, so nothing needs re-encoding
HEVC video and AAC audio (typical iPhone clip)FFmpeg remux with the hvc1 tagMP4 can hold HEVC, but older players may not decode it
H.264 video with uncompressed PCM audioFFmpeg, copy video and encode audioOnly the audio needs conversion, so the video stays untouched
ProRes or another editing codecHandBrake or FFmpeg re-encodeDelivery MP4s use H.264 or HEVC, so the video must be re-encoded
Variable frame rate phone footage that stutters in an editorHandBrake with constant frame rateRe-encoding lets you lock the frame rate
One file, no terminal experienceHandBrakePresets and a queue replace flags
A folder of 200 clipsFFmpeg in a shell loopOne loop handles every file with the same settings

Where the versions stand on November 19, 2026

The project’s release announcements name HandBrake 1.11.0, 1.11.1 and 1.11.2, and 1.11.2 is the newest of the three. Treat anything newer as unreleased until the team posts an announcement.

AMD published a post on HandBrake 1.11.0 scaling on Threadripper processors, which tells you that release targeted encode speed on many-core machines. For a MOV to MP4 job on a laptop, you will rarely feel that. The release matters more for the bundled libraries, because HandBrake uses FFmpeg, x264 and x265 under the hood to create MP4 or MKV files. HandBrake 1.11.2 reportedly shipped with FFmpeg 8.0.2 for decoding and filters, and a development commit reportedly updates that to 9.0.2. That second item sits in the development tree, so it does not describe the release you download today.

FFmpeg is messier to pin down. The ffmpeg.org news page I could read lists FFmpeg 8.1 “Hoare” dated March 16, 2026. Other trackers reportedly show 9.0.2 as a stable release from September 2026, and the repository reportedly carries a release/9.1 branch prepared in late October 2026. Where sources disagree, the safe move is to trust your own install. Run ffmpeg -version and read the first line.

One reported issue is worth knowing if you handle iPhone footage. An FFmpeg issue-tracker entry reportedly describes an HEVC regression where avcodec_flush_buffers() did not always clear queued output frames, affecting release branches from 7.1 through 9.0. A remux does not decode frames, so it sidesteps decoder bugs entirely. A re-encode of HEVC footage does decode, so keep your build current and spot-check the output.

ItemHandBrakeFFmpeg
Current line on official pagesHandBrake 1.11.2 announced8.1 “Hoare” on ffmpeg.org news
Release date on the official pageNot shown on the pages checkedMarch 16, 2026
Previous major release listed1.11.1 and 1.11.0 announcementsNot listed
Where to read release newshandbrake.fr/news.phpffmpeg.org news page
Libraries insideFFmpeg, x264, x265Its own libav libraries
Checked onNovember 19, 2026November 19, 2026

HandBrake vs FFmpeg specs for MOV to MP4

The table below compares the two tools on the traits that matter for this specific conversion. It uses only what the official HandBrake and FFmpeg pages state, plus plain descriptions of how each interface works. No benchmark numbers appear here because none of the pages checked published any for this task. A later section explains how to measure on your own files.

TraitHandBrakeFFmpeg
What it isDesktop application that creates MP4 or MKV filesCommand-line programs (ffmpeg, ffprobe) and libraries
Newest release checked1.11.28.1 “Hoare” on its news page
Video remux (no re-encode)Not its main job, built around re-encodingYes, with -c copy
Re-encode to H.264Yes, through x264Yes, through libx264
Re-encode to HEVCYes, through x265Yes, through libx265
Output containersMP4 or MKVMany, including MP4 and MOV
InterfaceWindow with presets, a preview and a queueTerminal, flags and scripts
Quality controlConstant quality slider-crf flag
Audio handlingEncode to AAC or pass through compatible tracks-c:a copy or -c:a aac
Batch workAdd files to the queueShell loop or script
Inspect a file firstSource summary in the appffprobe prints every stream
Learning curveLowSteeper but short for this one task
Odd MOV extras (timecode tracks)Builds a new file from the tracks you pickNeeds explicit stream mapping

Two rows decide most cases. The first is video remux. If the streams already fit MP4, only FFmpeg can finish the job with zero quality change. The second is the interface. If you convert one clip a month, a window with a Start button is easier to trust than a flag you half remember.

The last row needs a short explanation. Cameras and Apple devices sometimes write extra tracks into a MOV, such as timecode or other data streams. A blanket -map 0 copies all of them, and MP4 does not always accept them. FFmpeg then stops with a tag error. HandBrake avoids the problem, because it builds a fresh file from the video, audio and subtitle tracks you pick. The remux section below shows the FFmpeg fix.

What a MOV holds and why that decides the method

MOV is the QuickTime File Format, created by Apple for its QuickTime framework, and Apple documents the format on its developer site. It is a container, which means it is a box with labeled compartments. The video lives in one compartment, the audio in another, and each compartment is encoded with its own codec. MP4 is also a container, and MDN’s guide to media container formats explains how containers like these organize data for playback.

That shared design is why a remux works at all. The encoded video does not care which box it sits in. Moving it from a MOV box to an MP4 box is a bookkeeping operation. FFmpeg reads the stream, writes the same bytes into a new wrapper, and rebuilds the index that tells a player where each frame lives. Nothing is decoded, so nothing is lost.

The trouble starts with the codecs. MOV files from different sources carry very different contents. A screen recording from a Mac usually holds a common delivery codec. An iPhone clip often holds HEVC. A file exported from an editor as a high-quality master may hold ProRes, which is an editing codec rather than a delivery codec. Camera files can carry uncompressed PCM audio. Each of these changes what the right tool does.

The MP4 side has its own limits. Your target decides which codecs are safe. Browsers, phones, social platforms and editors all accept H.264 video with AAC audio. HEVC in MP4 works on many modern devices but fails on some older players and browsers. The earlier MP4 vs MOV comparison covers the container side in detail, including why the file extension alone says nothing about quality.

Check the streams before you pick a tool

FFmpeg ships a companion program called ffprobe, and it answers the only question that matters. Run it against the file and read the codec names:

ffprobe -hide_banner input.mov

The output lists each stream on its own line. Look for lines starting with Stream and note the word after Video and after Audio. If you see h264 or hevc for video and aac for audio, remux. If you see prores, a PCM audio name, or anything unfamiliar, plan a re-encode of that stream. HandBrake shows a similar summary in its source panel after you open the file, though it is less detailed.

Remuxing MOV to MP4 with FFmpeg

The one-line command from the first section is the starting point. Here is what each part does. -i input.mov names the source. -map 0 tells FFmpeg to take every stream from that input. -c copy says copy them without re-encoding. The last argument is the output file, and its extension picks the MP4 container.

That command works for plenty of files, and it fails for some. The usual failure is an extra data track, such as a timecode track, that MP4 has no tag for. FFmpeg prints an error about not finding a tag for a stream and stops. The fix is to map only the streams you need:

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

This takes the first video stream and the first audio stream, copies both, and moves the index to the front of the file with +faststart. That flag matters for web delivery. Without it, a browser must download the whole file before playback can start, because the index sits at the end. With it, playback starts as soon as the first bytes arrive. HandBrake offers the same thing as a checkbox named Web Optimized.

iPhone HEVC clips: add the hvc1 tag

Apple’s players are picky about how HEVC is labeled inside an MP4. When FFmpeg remuxes an HEVC stream, it may label it hev1, and QuickTime Player and some Apple software then refuse to play it. Forcing the hvc1 label fixes that:

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

The video itself is unchanged. Only the label differs. The HEVC to MP4 remux guide goes deeper on this exact iPhone case. If the clip carries HDR data, a remux keeps it. That is a strength when you are going to another HDR-aware editor and a weakness when the viewer’s screen is not HDR, because the colors can look flat. In that second case you need a re-encode with tone mapping, which is outside what a plain remux does.

PCM audio: copy the video, encode the audio

Some cameras and capture tools write uncompressed PCM audio into a MOV. MP4 players do not reliably handle PCM, so the audio should become AAC. The video can still be copied:

ffmpeg -i input.mov -map 0:v:0 -map 0:a:0 -c:v copy -c:a aac -b:a 192k -movflags +faststart output.mp4

The audio bitrate is my own choice, not a value taken from FFmpeg’s reference material. Audio encoding is cheap, so this finishes almost as fast as a pure remux, and the video keeps its original quality. HandBrake can do the same thing in one preset, but it re-encodes the video too.

When a remux goes wrong: symptoms and fixes

Most remux problems repeat. The table lists the ones you are likely to meet, what causes them, and the smallest fix.

SymptomLikely causeFix
FFmpeg stops with a tag error for a streamAn extra data or timecode track MP4 cannot holdMap only video and audio with -map 0:v:0 -map 0:a:0
Video plays but there is no soundAudio codec (often PCM) not supported in the MP4 playerCopy the video and encode the audio to AAC
QuickTime Player refuses an HEVC MP4Stream labeled hev1 instead of hvc1Add -tag:v hvc1 to the remux
Web page waits for the whole download before playingIndex sits at the end of the fileAdd -movflags +faststart
Colors look washed out on a normal screenHDR clip played on an SDR displayRe-encode with tone mapping to an SDR H.264 file
Audio drifts against video in an editorVariable frame rate sourceRe-encode with a constant frame rate
Editor will not import the MP4Codec the editor does not decodeRe-encode to H.264 with AAC audio

Notice how few of these need a full re-encode. Most come down to which streams you map, how you label them, or one audio conversion. Only the last three rows change the picture itself. That is the reason to try the remux first. A failed remux costs a few seconds and teaches you what is inside the file.

Re-encoding MOV to MP4 with HandBrake

HandBrake’s strength is that it removes the guesswork. You open the MOV, pick a preset, set the format to MP4 and press Start. The project’s own description calls it software that uses tools including FFmpeg, x264 and x265 to create new MP4 or MKV files, which is exactly the job here. It is not a remuxer. Every video track it writes is a fresh encode.

That makes HandBrake the right tool when the source codec cannot go into MP4, when you want a smaller file, or when you need to fix timing. A ProRes master becomes an H.264 delivery file. A variable frame rate phone clip becomes constant. A big camera file becomes something that uploads in a reasonable time.

The settings that matter

  1. Open the MOV with Open Source and let HandBrake scan it.
  2. Pick a General preset that matches your target, such as one of the Fast or HQ presets for your resolution.
  3. On the Summary tab, set Format to MP4 and tick Web Optimized if the file will play in a browser.
  4. On the Video tab, choose H.264 for the widest compatibility or H.265 for smaller files on newer devices. Leave the quality mode on constant quality.
  5. Set the frame rate to Same as source and tick Constant Framerate unless you have a reason to change it.
  6. On the Audio tab, keep AAC for the track list. Pass-through only helps when the source audio is already AAC.
  7. Choose a destination file name ending in .mp4 and press Start Encode.

Resolution is the one setting beginners change by accident. Leave the picture size at the source resolution unless you want a smaller file. Enlarging footage adds file size and no detail. Shrinking it, for example from 4K to 1080p, cuts file size sharply but also cuts sharpness, and you cannot get that back from the MP4.

The queue is the feature that FFmpeg users miss. Add ten MOV files, apply one preset, and walk away. For a handful of clips the queue is quicker than writing a script. For hundreds, a loop is better, because the queue needs a person to add each file.

Re-encoding with FFmpeg: the command-line equivalent

FFmpeg does everything HandBrake does for this job, and the reference command from its documentation is short:

ffmpeg -i input.mov -c:v libx264 -crf 18 -preset medium -c:a aac -b:a 192k output.mp4

Read it from left to right. The video codec is x264 through libx264. -crf 18 sets constant quality, where a lower number means higher quality and a bigger file. -preset medium trades encoding time for compression efficiency, and slower presets squeeze the same quality into fewer bytes. Audio goes to AAC at the bitrate you set with -b:a. These are the same four decisions HandBrake asks you to make in its window.

Add -movflags +faststart for web delivery. Add -pix_fmt yuv420p if the source is a 10-bit file and you want the widest player support, because many devices cannot decode H.264 at higher bit depth. For HEVC output, swap in libx265 and add -tag:v hvc1 for Apple compatibility.

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

That longer command is the closest match to a HandBrake run with Web Optimized and Constant Framerate ticked. Older FFmpeg builds use -vsync cfr in place of -fps_mode cfr, so if your build rejects the newer flag, try the older one.

Batch conversion in a loop

FFmpeg’s real advantage shows up with many files. On macOS or Linux, this loop remuxes every MOV in a folder:

for f in *.mov; do
  ffmpeg -i "$f" -map 0:v:0 -map 0:a:0 -c copy -movflags +faststart "${f%.mov}.mp4"
done

On Windows PowerShell, the same idea reads like this:

Get-ChildItem *.mov | ForEach-Object {
  ffmpeg -i $_.FullName -map 0:v:0 -map 0:a:0 -c copy -movflags +faststart ($_.BaseName + ".mp4")
}

Run the loop on a copy of a few files first. A remux never alters the original MOV, but a typo in the output name could overwrite another file.

Speed and quality: the benchmark gap

Readers usually want a number here, such as how many times faster a remux runs than a re-encode. I could not find a published, dated benchmark for HandBrake versus FFmpeg on MOV to MP4 from either project, so this article does not print one. A figure from an unnamed forum post would be worse than no figure. What the official pages do support is the direction of the difference, and the direction is not in doubt.

A remux copies bytes. Its speed is limited by how fast your drive reads and writes, which is why a long clip finishes quickly on an SSD. A re-encode decodes every frame and compresses it again, so its speed depends on your processor or graphics hardware, the preset, and the resolution. A slower preset takes longer and produces a smaller file at the same quality target. A remux has no quality loss by definition. A re-encode always has some, though at a low constant-quality number the difference is hard to see.

Because HandBrake uses x264 and x265 and FFmpeg can call the same encoders, the two tools should land close in output quality when given equivalent settings. Differences come from the settings you choose, not from the program name. That is the most useful point for a decision: do not pick a tool for quality, pick it for workflow.

Measure it on your own files

You can produce your own benchmark in five minutes. Time the remux, time the re-encode, then compare file sizes. On macOS or Linux, wrap each command with time:

time ffmpeg -i input.mov -map 0:v:0 -map 0:a:0 -c copy remux.mp4
time ffmpeg -i input.mov -c:v libx264 -crf 18 -preset medium -c:a aac -b:a 192k encode.mp4
ls -l input.mov remux.mp4 encode.mp4

For a quality score, FFmpeg can compare an encode against its source with the SSIM or VMAF filters when your build includes them. Run the same test on the HandBrake output. If both land close together at the same target size, you have confirmed the point above on your own hardware. The wider export and codecs section has comparisons of the codecs themselves, which is where real size differences show up.

Render settings for a MOV to MP4 job

These are the settings to start from. Resolution and frame rate stay at the source values in every column, because changing them is a separate decision from changing the container. Format is MP4 everywhere. Checked against the FFmpeg and HandBrake documentation on November 19, 2026.

SettingRemux (FFmpeg)Re-encode for compatibilityRe-encode for smaller files
ResolutionSame as sourceSame as sourceSame as source or one step down
Frame rateSame as sourceSame as source, constantSame as source, constant
LengthUnchangedUnchangedUnchanged
Video codecCopiedH.264H.265 for newer devices
QualityUnchangedConstant quality, CRF 18 as a startConstant quality, a higher CRF than 18
AudioCopied if AACAACAAC
Web playbackAdd +faststartAdd +faststartAdd +faststart
Apple HEVC tagAdd -tag:v hvc1 for HEVCNot needed for H.264Add -tag:v hvc1 for HEVC

A few notes on reading the table. CRF 18 comes from FFmpeg’s own reference command and is a conservative starting point, not a rule. Raise the number for smaller files and look at a few seconds of the result before running the full batch. H.265 gives smaller files at similar quality but costs you compatibility, so choose it only when you know where the file will play.

Pricing and licensing

Neither project sells plans. The HandBrake homepage identifies the software as an open source video transcoder, and the HandBrake documentation footer shows a CC BY-SA 4.0 licence for the docs. FFmpeg’s pages list no price, no paid edition and no subscription tier in the sources checked. That makes the comparison simple, because the cost is your time.

ItemHandBrakeFFmpeg
Software priceOpen source, no price on handbrake.frNo price or plan listed on ffmpeg.org
Paid tier or subscriptionNone shownNone shown
Watermark or length capNone shownNone shown
Documentation licenceCC BY-SA 4.0 (docs footer)Not checked
Sponsorship items on the news pageNot checkedCI sponsored by GitHub and Blacksmith (November 10, 2026), server donation from Ampere (June 24, 2026)

The sponsorship items on FFmpeg’s news page matter for one reason. They show that the project’s test infrastructure is funded and active, which supports the general point that FFmpeg is maintained. Neither company sells you anything through those deals.

Third-party MOV to MP4 converters that charge a fee or add a watermark exist, and many web converters cap file size or length. Both HandBrake and FFmpeg run on your own computer, so your footage never uploads anywhere. For client work or unreleased footage, that is a real reason to prefer them over a browser tool.

Six real-world scenarios

These scenarios come from how the tools work, not from test results. Each one names the method that fits and the reason.

1. iPhone clip for a YouTube upload

An iPhone clip is typically a MOV with HEVC video and AAC audio. Many platforms accept HEVC, but check the upload spec of the one you use. If it does, a remux with the hvc1 tag is the cleanest path. You keep full quality and finish quickly. If the clip must also play on an old laptop, re-encode to H.264 instead.

2. Mac screen recording for a tutorial

Screen recordings from macOS land as MOV files, and long ones can be large. A re-encode to H.264 in HandBrake usually shrinks them without visible loss on mostly static screens, since flat interface colors compress well. If the file is already a manageable size, a remux is enough.

3. A ProRes master from an editor

A ProRes MOV cannot be remuxed into a normal delivery MP4. The video must be re-encoded to H.264 or HEVC. Use HandBrake if you want presets, or the FFmpeg re-encode command if the export is part of a script. Keep the ProRes file as your archive and treat the MP4 as a copy.

4. Camera footage with PCM audio

When the video is already H.264 but the audio is uncompressed PCM, FFmpeg’s copy-video, encode-audio command is the efficient fix. HandBrake would re-encode the video as well, which costs time and a little quality for no gain.

5. A phone clip that stutters in the editor

Phones often record variable frame rate video. Some editors handle it badly, producing audio drift or choppy playback. A remux keeps the variable timing, so it does not help. A HandBrake run with Constant Framerate checked, or the FFmpeg command with -fps_mode cfr, rebuilds the file with even timing.

6. A folder of 200 event clips

For a wedding or conference shoot, a shell loop with the remux command converts everything with identical settings and no clicking. If some clips fail on a data track, add the explicit map flags from the remux section. HandBrake’s queue works too, but each file must be added and the settings checked.

Pros and cons of each tool

HandBrake and FFmpeg overlap on re-encoding and diverge on everything else. This list is what stays true across the sources checked.

HandBrake

  • Pro: A graphical interface with presets, a preview and a queue, so a first conversion takes minutes to learn.
  • Pro: It builds a clean new file, so odd data tracks in the MOV do not break the output.
  • Pro: Constant frame rate and web optimization are checkboxes.
  • Con: It re-encodes the video, so it cannot give you a lossless MOV to MP4 move.
  • Con: Large batches need manual queueing.
  • Con: A re-encode takes far longer than a copy on long clips.

FFmpeg

  • Pro: A remux with -c copy keeps quality unchanged and finishes quickly.
  • Pro: It does both remux and re-encode, so one tool covers every MOV.
  • Pro: Shell loops scale to any number of files with identical settings.
  • Con: It has no graphical interface, and a mistyped flag gives a cryptic error.
  • Con: A blanket stream map can fail on timecode or data tracks.
  • Con: Version differences between builds change flag names, such as -vsync and -fps_mode.

Migration guide: moving between HandBrake and FFmpeg

If you already use one tool and want the other, the settings map almost one to one. The table below translates the HandBrake window into FFmpeg flags. Use it in either direction.

HandBrake settingFFmpeg flag
Format: MP4Output file ending in .mp4
Web Optimized-movflags +faststart
Video encoder: H.264 (x264)-c:v libx264
Video encoder: H.265 (x265)-c:v libx265 -tag:v hvc1
Constant quality slider-crf with a number
Encoder preset (speed)-preset medium or slower
Frame rate: same as source, constant-fps_mode cfr
Audio: AAC-c:a aac
Audio: pass-through-c:a copy
Pixel format for compatibility-pix_fmt yuv420p

To move from HandBrake to FFmpeg, start with a file you have already converted in HandBrake. Run the matching FFmpeg command on the same source, then compare size and a few seconds of playback. If they match, copy the command into a script and retire the manual step. Keep HandBrake installed for the odd file that confuses your stream map.

To move from FFmpeg to HandBrake, open your usual file, set the same codec, quality and audio options in the window, and save them as a custom preset. After that, you apply the preset to every new file. The one thing you lose is the zero-loss remux, so decide up front which of your MOV files really need a re-encode.

A middle route works well for many creators. Use FFmpeg’s remux for the files that qualify, and use HandBrake for the rest. A short ffprobe check at the start tells you which pile each file belongs in, and the whole decision takes under a minute.

Which one to pick: use-case recommendations

Match the tool to the job, not to a preference. These are the cases that cover most MOV conversions.

  • YouTuber with iPhone footage: FFmpeg remux with the hvc1 tag. You keep full quality, and the upload works as is.
  • Streamer saving Mac or QuickTime captures: HandBrake re-encode to H.264 with constant quality, to shrink big captures.
  • Editor delivering from a ProRes master: HandBrake or the FFmpeg re-encode command, always keeping the ProRes as the archive.
  • Small studio with hundreds of clips: an FFmpeg shell loop, with explicit stream maps.
  • First-time user with one file: HandBrake. The preset list is the lowest-risk path.
  • Anyone fixing stuttering phone video: a re-encode with constant frame rate in either tool.

The verdict

FFmpeg wins on the one thing that is unique to this task: a lossless MOV to MP4 remux in seconds. If your streams are compatible, it is the better tool, and nothing else matches it. HandBrake wins on ease. It is the better first choice when the file needs re-encoding or when you do not want a terminal.

The evidence behind that call is thin on speed numbers and solid on mechanism. Both projects document that a remux preserves quality and requires compatible streams, and that a re-encode is the fallback. Neither publishes a benchmark for this job, so measure a clip of your own with the commands in the benchmark section. The takeaway: remux when you can, re-encode when you must, and let the ffprobe output decide which one applies.

Common questions

Does converting MOV to MP4 lose quality?

Not with a remux. A remux copies the encoded streams into a new container, so quality is unchanged. A re-encode does lose a little, though a low constant-quality number keeps the loss hard to see.

Can HandBrake remux a MOV without re-encoding?

HandBrake is built around re-encoding the video, so it is not the tool for a zero-loss container swap. It can pass through compatible audio, but the video is encoded again. Use FFmpeg for a true remux.

Why does my FFmpeg remux fail with a tag error?

The MOV probably holds an extra track, such as timecode, that MP4 has no tag for. Replace -map 0 with -map 0:v:0 -map 0:a:0 to copy only the video and first audio stream.

Will the MP4 play on every device?

H.264 video with AAC audio plays almost everywhere. HEVC in MP4 works on many newer devices but may fail on older ones. If you are unsure, re-encode to H.264.

Can I convert a ProRes MOV to MP4 without re-encoding?

No. ProRes is an editing codec, and delivery MP4 files use H.264 or HEVC. The video has to be re-encoded, and you should keep the original ProRes file as your master.

What does faststart do?

It moves the file’s index to the front, so a browser can start playback before the whole file downloads. In HandBrake it is the Web Optimized checkbox. In FFmpeg it is -movflags +faststart.

Which version should I install?

Install the newest release your system offers. As of November 19, 2026, HandBrake 1.11.2 is the newest announced on the project’s pages. For FFmpeg, run ffmpeg -version to see what you have, and update if it predates the 8.1 release on ffmpeg.org’s news page.

Are HandBrake and FFmpeg free?

Neither project lists a price or a paid plan on the pages checked. Both run on your own computer, so your footage stays local and no watermark or length cap applies.

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.