When HandBrake hands you a .m4v instead of the .mp4 you expected, you have not encoded to a different format. HandBrake's own documentation says it about as directly as documentation ever says anything: "They are the exact same file, the only difference is the extension."
So the fix is trivial. The part worth knowing — and the part almost every answer skips — is why it happened, because HandBrake does not do this at random. Three specific settings trigger it, they are named in the official docs, and once you know which one you switched on you can decide whether to turn it off or leave it alone.
What the .m4v extension actually is here
HandBrake outputs three containers. In its words, it "creates the widely supported container formats MKV and MP4 (sometimes seen as M4V), in addition to the WebM container format, which is subset of MKV."
Note the parenthetical: M4V is not a fourth option. It is the MP4 container with a different four letters after the dot. HandBrake spells out the consequence: "You can simply change the file extension between .mp4 and .m4v as the file is exactly the same. There are no differences in the content or container itself."
One caveat before you build a workflow on any of this: HandBrake marks the container documentation page as a draft, with a banner that reads "This article is a draft and may contain incomplete or incorrect information." The M4V behaviour described below is what that page states — treat it as the official description, not as a guarantee that will never change.
The three settings that trigger it
Here is the sentence that answers the question. HandBrake's documentation:
"For MP4 files, HandBrake will automatically use the extension M4V when you pass-through audio (AC3), use SRT subtitles or have chapter markers enabled."
That is the whole list. Three triggers, and at least one of them is on in your job:
| Trigger | Where it lives | How it usually gets switched on |
|---|---|---|
| AC3 audio passthrough | Audio tab | A preset that includes surround sound, on a source that has a surround track |
| SRT subtitles | Subtitles tab | An SRT read from the source, or one you imported as a separate file |
| Chapter markers enabled | The chapter markers option for the job | The official docs do not state when this is on by default — check it in the app |
Why the audio one catches people out
The AC3 trigger is the sneakiest of the three, because you can switch it on without ever opening the Audio tab.
HandBrake's MP4 container supports passing audio through rather than re-encoding it: "It is also possible to pass through Dolby Digital 5.1 Surround Sound (AC3) audio from a DVD or Blu-ray, and E-AC3 and TrueHD." And the preset documentation explains what a surround preset does with your source's audio — "When selecting a Preset that includes surround sound, stereo audio is encoded and surround audio is 'passed through' if possible (or encoded to a compatible format)."
Put those together and the mechanism is clear. Pick any preset whose audio column reads "AAC stereo; Dolby Digital (AC-3)" — that covers the HQ and Super HQ presets and a large share of the Devices presets — feed it a source that actually has a surround track, and passthrough happens on its own. The extension follows. If the source has no surround audio, nothing gets passed through and the same preset gives you .mp4.
The fastest fix: rename the file
Since the bytes are identical, renaming is not a workaround — it is the documented solution:
"You can simply change the file extension between .mp4 and .m4v as the file is exactly the same. There are no differences in the content or container itself."
Change myvideo.m4v to myvideo.mp4 and you are done.
There is exactly one situation where you should not do it, and HandBrake calls it out: "QuickTime 7 or any QT 7 based application will not be able to play a MP4 file with these features enabled, unless it has the extension '.m4v'. This limitation does not apply to QuickTime X or iOS." If anything in your chain is QuickTime 7-era, the .m4v name is doing real work and renaming it will break playback of those features.
If what you actually want is a plain .mp4 out of a QuickTime source and you would rather not open HandBrake at all, the converter below does that job in the browser tab:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
Your file is read from disk, converted locally and handed back — nothing is uploaded. The rest of the set lives at all Clapr tools, including MOV to MP4 as a full page if you want it outside this article.
How to stop it happening at all
Two routes, depending on whether you care about the features or only about the extension.
Route 1 — turn off whichever trigger you do not need.
- Audio: set the track to an encoded format rather than passthrough. For MP4, HandBrake recommends AAC anyway: "AAC is recommended for better compatibility on most players." Each track is configured individually on the Audio tab.
- Subtitles: drop the SRT track from the job. Worth knowing before you do: HandBrake can either burn subtitles in permanently or keep them as selectable soft tracks, and dropping the track removes both.
- Chapters: disable chapter markers for the job.
Route 2 — keep the features and turn off the automatic rename. HandBrake documents a preference for this: the extension switch happens automatically "although this can be disabled in the preferences if you really want .mp4 at the end of the name." That gives you an .mp4 file that still contains the chapters, the AC3 track or the SRT subtitles — which is the same file the rename gets you, just produced without the extra step.
Route 2 is the better default: dropping a feature you actually wanted just to get a nicer filename is a bad trade.
Why HandBrake does this at all
The reason is compatibility with an old Apple player, not anything about the container. From the MP4 section of the same page: "Be aware that chapters and AC3 audio can only be seen by QuickTime 7 and earlier if you change the file extension from .mp4 to .m4v." And: "QuickTime X and later don't require the extension change."
So the automatic rename is HandBrake pre-emptively making the file readable by QuickTime 7 in the cases where the extension mattered. On anything current, it does not.
One honest wrinkle in the source material: the passage explaining the QuickTime rationale mentions chapters and AC3 audio, while the M4V passage lists three triggers including SRT subtitles. The docs do not reconcile the two lists, and they do not say whether burned-in SRT and soft SRT behave differently. If that distinction matters for your workflow, check the official documentation rather than trusting a third-party reading of it — including this one.
How to tell it worked
If you renamed: open the file. Everything plays as before, because it is the same file — the documentation's "no differences in the content or container itself" means the content is untouched by the rename.
If you turned off a trigger instead, that is a fresh encode, so check the new output rather than assuming.
FAQ
Is M4V the same as MP4? For files HandBrake produces, yes. The documentation says they are "the exact same file, the only difference is the extension," and that there are no differences in the content or the container itself.
Can I just rename .m4v to .mp4?
Yes — HandBrake documents renaming in either direction as safe, because the file is identical. The single exception is QuickTime 7 and QuickTime 7-based apps, which cannot play an MP4 with these features enabled unless the extension is .m4v.
Why did HandBrake make an M4V when I selected an MP4 preset? Because one of three things was on: AC3 audio passthrough, SRT subtitles, or chapter markers. All of the MP4 presets still write the MP4 container — only the extension changes.
How do I stop HandBrake saving as M4V? Either remove the trigger (encode the audio instead of passing AC3 through, drop the SRT track, or disable chapter markers), or leave the features on and disable the automatic extension in HandBrake's preferences.
Will renaming to .mp4 lose my chapters or my AC3 track?
No. The file is unchanged, so the chapters and the audio track are still in it. What changes is that a QuickTime 7-era player will no longer see those features without the .m4v name.
Does the same thing happen with MKV output? No. This behaviour is described for MP4 files only. MKV and WebM are separate containers with different capabilities — MKV, for instance, can pass through DTS, which the MP4 section does not list.
Related reading: the HandBrake presets that got renamed explains why the preset in your tutorial may not exist any more, and HandBrake RF value explained covers the quality control that decides how big the output gets. More troubleshooting write-ups live in the fix archive.
Quotes above are from HandBrake's official documentation on output containers, which HandBrake itself labels a draft. Check the current page before relying on this behaviour.
