HandBrake's official documentation lists four subtitle sources it can read, and WebVTT is not one of them. That is a narrower statement than "HandBrake does not support VTT," and the gap between those two sentences is the whole point of this page.
Most articles on this keyword pick a side and say it confidently. The documentation does not pick a side. It publishes a list, VTT is absent from it, and it never addresses .vtt files anywhere else. Knowing exactly that much is more useful than a guess in either direction, because it tells you what to build your workflow on.
The subtitle sources, at a glance
HandBrake's subtitles page introduces the list with the line "HandBrake can read subtitles from the following sources:" and then gives four entries, quoted verbatim below.
| Source | In the official list? | What the docs say about it |
|---|---|---|
| DVD — embedded VOBSUB or CC tracks | Yes | "From DVD's – Either embedded VOBSUB or CC tracks." |
| Blu-ray PGS subtitles | Yes | "From Bluray - PGS Subtitles." Cannot be passed through into MP4. |
| SRT files you supply yourself | Yes | "User supplied SRT files." Imported on the Subtitles tab. |
| SSA / SRT / CC already inside the file | Yes | "Embedded SSA/SRT/CC within files (such as mkv or mp4)" |
WebVTT (.vtt) | Not listed | Not mentioned on the page — neither listed nor ruled out. |
Three of those four entries describe subtitles that arrive inside your source. Only one describes a separate file you hand to HandBrake yourself, and that one says SRT.
The same page classifies subtitles into three kinds up front: "Bitmaps (Pictures), e.g. DVD VOBSUBs, Bluray PGS", "Text with markup, e.g. Closed Captions and SRT files.", and "Styled SSA, e.g. most anime subtitles in MKV files". WebVTT would sit in the middle category alongside SRT and closed captions, but it is not named there either.
What "not listed" does and does not mean
Two facts have to sit next to each other here without being mashed together.
Fact one: the subtitles page does not include VTT in its read list, and no other page in the documentation says HandBrake imports .vtt.
Fact two: HandBrake's source-formats page says the application "uses FFmpeg libavformat and libavcodec libraries under the hood and generally can open whatever FFmpeg will, in addition to disc-based formats like DVD and Blu-ray." That sentence is written about opening video sources, not about the subtitle import path, and the documentation never extends it to subtitle files.
So the honest reading is: HandBrake's documentation does not state that it can import WebVTT, and it does not state that it cannot. If you need a definitive answer for your exact build, check the official documentation and test with your own file rather than trusting any article — including the ones that assert a yes or a no.
The practical stance that follows from this is simple. Do not build a subtitling workflow on behaviour the documentation does not describe. Convert the VTT to the format the docs name explicitly, and the question stops mattering.
What to do when you have a .vtt file
Convert it to SRT before you open HandBrake. SRT is the one subtitle format the documentation says you can supply as a separate file, and the SRT entry spells out both routes into HandBrake: it "Can be read from your source file or imported through the “Subtitles tab” if you have separate files(s)".
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That runs in your browser tab — the file is read from disk and rewritten locally, so a caption file with client names or unreleased footage in it never travels to a server. The standalone version lives at VTT to SRT, and the reverse conversion at SRT to VTT if you later need the file back in web form for an HTML5 player.
Converting is not lossless in the abstract — VTT can carry things SRT has no way to express — but the timing and the text survive intact. If you want the full accounting of what changes, SRT vs VTT goes through it line by line.
After the import: five things the documentation warns about
Getting the file accepted is only half of it. The subtitles page documents several constraints that produce confusing results afterwards.
-
Set the character encoding, or you may end up with nothing. The docs are unusually blunt about this one: "You should make sure the correct character code is selected from the “Char Code” dropdown. Selecting the wrong code, will result in your output file having no subtitle track, and can cause the player to crash when playing that track." If your encode finished and the subtitle track vanished, this is the first thing to check.
-
Timing drift has a dedicated control. You can "set an offset (measured in milliseconds) to change the start time that the first and subsequent SRT subtitles will appear," and the documented method for finding the right number is trial and error: "Use trial and error encoding a single chapter to obtain the correct offset."
-
You can burn exactly one track. For both PGS and VOBSUB the docs repeat the same ceiling — "you can only burn 1 subtitle track into the file. The rest must be passed through." Plan for one burned language, not two.
-
Your MP4 may come out as .m4v. HandBrake "will automatically use the extension M4V when you pass-through audio (AC3), use SRT subtitles or have chapter markers enabled." Using an SRT file is one of the three documented triggers. The docs also say the files are identical: "They are the exact same file, the only difference is the extension." You can rename it, or turn the automatic behaviour off in preferences.
-
WebM output cannot carry soft subtitles. The containers page states that for WebM, "It can include “hard” burned in subtitles. “Soft” subtitles are currently unsupported." If your target is WebM, burning is the only route.
Hard burn or soft subtitles
HandBrake documents two output methods, and the choice determines which of the above applies to you.
Hard burn — "the subtitles are written on top of the image permanently. They cannot be turned on or off like on the DVD." Maximum compatibility, zero flexibility, and subject to the one-track ceiling.
Soft subtitles — "the subtitles will appear as separate selectable tracks in your output file. With the correct playback software, you'll be able to enable / disable these subtitles as required." Available in MP4 and MKV, not in WebM.
Pick burn when the file is going somewhere you do not control the player — a chat app, a social upload, a client review link. Pick soft when the file stays in a player you trust and you want multiple languages. If burning is all you need and you would rather not install anything, burn subtitles to video does that step in the browser as well.
FAQ
Can HandBrake import .vtt subtitle files? The official documentation does not list WebVTT among the subtitle sources HandBrake can read, and it does not say the opposite either. The documented path for a separate subtitle file is SRT. Convert first.
Does HandBrake support WebVTT at all?
Nothing in the documentation addresses .vtt. It is absent from the read-sources list, from the three-way classification of subtitle types, and from the containers page. Treat it as undocumented, not as confirmed either way.
How do I convert VTT to SRT for HandBrake?
Run the file through the converter above, then load the resulting .srt on HandBrake's Subtitles tab. Check the Char Code dropdown before you start the encode.
Why did my subtitle track disappear after encoding? The documented cause is the wrong character code: selecting the wrong one "will result in your output file having no subtitle track, and can cause the player to crash when playing that track."
Why did HandBrake output an .m4v file instead of .mp4? Using SRT subtitles is one of three documented triggers for the automatic extension switch, along with AC3 pass-through and chapter markers. The file itself is unchanged.
Can I burn two subtitle languages into one video? No. The documentation caps burning at one track per file; additional tracks have to be passed through as soft subtitles, which rules out WebM output.
Behaviour described from HandBrake's official documentation at handbrake.fr, checked 16 September 2026. More format and platform ceilings in the limits archive, and the full browser toolkit at Clapr tools.
