Adding captions and subtitles to HTML5 video

This article is also available on MDN.

With the introduction of the <video> and <audio> elements to HTML5, we finally have a native way to add video and audio to our websites. We also have a JavaScript API that allows us to interact with this media content in different ways, be it writing our own controls or simply seeing how long a video file is. As responsible web developers, we should also be constantly thinking about making our content more accessible, and this doesn’t stop with video and audio content. Making our content accessible to all is an important step, be it for someone who is hard of hearing or someone who doesn’t understand the language that the content is delivered in, inclusion can be paramount.

Thankfully HTML5 also provides us with a native way of making our media content more accessible by adding subtitles and captions via the <track> element. Most major browsers support this natively to varying degrees, which the first part of this article shows, but it also provides a JavaScript API, with which we can access and use the text tracks (e.g. subtitles) that are available. This article also shows how this API can be used to detect what captions/subtitles have been added to a HTML5 video, and how that data can be used to build a selectable menu of available text tracks and ultimately provide a more consistent interface across the various browsers.

In articles on MDN, we have looked at how to build a cross browser video player using the HTMLMediaElement and Window.fullScreen APIs, and also at how to style the player. This article will take the same player and show how to add captions and subtitles to it, using Web_Video_Text_Tracks_Format and the <track> element.

subtitled video example

In this article, we will refer to the Video player with subtitles example. This example uses an excerpt from the Sintel open movie, created by the Blender Foundation.

Video player with stand controls such as play, stop, volume, and subtitles on and off. The video playing shows a scene of a man holding a spear-like weapon, and a subtitle reads "Esta hoja tiene pasado oscuro."

Note: You can find the source on Github, and also view the example live.

HTML5 and Video subtitles

Before diving into how to add subtitles to the video player, there are a number of things that we will first mention, which you should be aware of before we start.

Captions versus subtitles

Captions and subtitles are not the same thing: they have significantly different audiences, and convey different information, and it is recommended that you read up on the differences if you are not sure what they are. They are however implemented in the same way technically, so the material in this article will apply to both.

For this article we will refer to the text tracks displayed as subtitles, as their content is aimed at hearing people who have difficulty understanding the language of the film, rather than deaf or hard-of-hearing people.

The <track> element

HTML5 allows us to specify subtitles for a video using the <track> element. The various attributes of this element allow us to specify such things as the type of content that we’re adding, the language it’s in, and of course a reference to the text file that contains the actual subtitle information.


The files that contain the actual subtitle data are simple text files that follow a specified format, in this case the Web Video Text Tracks (WebVTT) format. The WebVTT specification is still being worked on, but major parts of it are stable so we can use it today.

Video providers (such as the Blender Foundation) provide captions and subtitles in a text format with their videos, but they’re usually in the SubRip Text (SRT) format. These can be easily converted to WebVTT using an online converter such as srt2vtt.

Modifications to the HTML and CSS

This section summarises the modifications made to the previous article’s code in order to facilitate the addition of subtitles to the video. If you are not interested in thism and just want to get straight into the JavaScript and more relevant CSS, skip to the Subtitle implementation section.

In this example we are using a different video, Sintel, as it actually has some speech in it and therefore is better for illustrating how subtitles work!

HTML Markup

As mentioned above, we need to make use of the new HTML5 <track> element to add our subtitle files to the HTML5 video. We actually have our subtitles in three different languages — English, German, and Spanish — so we will reference all three of the relevant VTT files by adding <track> elements inside our HTML5 <video> element:

<video id="video" controls preload="metadata">
   <track label="English" kind="subtitles" srclang="en" src="subtitles/vtt/sintel-en.vtt" default>
   <track label="Deutsch" kind="subtitles" srclang="de" src="subtitles/vtt/sintel-de.vtt">
   <track label="Español" kind="subtitles" srclang="es" src="subtitles/vtt/sintel-es.vtt">

As you can see, each <track> element has the following attributes set:

  • kind is given a value of subtitles, indicating the type of content the files contain
  • label is given a value indicating which language that subtitle set is for for example English or Deutsch — these labels will appear in the user interface to allow the user to easily select which subtitle language they want to see.
  • src is assigned a valid URL pointing to the relevant WebVTT subtitle file in each case.
  • srclang indicates what language each subtitle files’ contents are in.
  • The default attribute is set on the English <track> element, indicating to the browser that this is the default subtitle file definition to use when subtitles have been turned on and the user has not made a specific selection.

In addition to adding the <track> elements, we have also added a new button to control the subtitles menu that we will build. As a consequence, the video controls now look as follows:

<div id="video-controls" class="controls">
   <button id="playpause" type="button">Play/Pause</button>
   <button id="stop" type="button">Stop</button>
   <div class="progress">    
         <span id="progress-bar"></span>
   <button id="mute" type="button">Mute/Unmute</button>
   <button id="volinc" type="button">Vol+</button>
   <button id="voldec" type="button">Vol-</button>
   <button id="fs" type="button">Fullscreen</button>
   <button id="subtitles" type="button">CC</button>

CSS Changes

The video controls have undergone some minor changes in order to make space for the extra button, but these are relatively straightforward.

No image is used for the subtitles button, so it is simply styled as:

.controls button[data-state="subtitles"] {

There are also other CSS changes that are specific to some extra JavaScript implementation, but these will be mentioned at the appropriate place below.

Subtitle implementation

A lot of what we do to access the video subtitles revolves around JavaScript. Similar to the video controls, if a browser supports HTML5 video subtitles, there will be a button provided within the native control set to access them. However, since we have defined our own video controls, this button is hidden, and we need to define our own.

Browsers do vary as to what they support, so we will be attempting to bring a more unified UI to each browser where possible. There’s more on browser compatibility issues later on.

Initial setup

As with all the other buttons, one of the first things we need to do is store a handle to the subtitles’ button:

var subtitles = document.getElementById('subtitles');

We also initially turn off all subtitles, in case the browser turns any of them on by default:

for (var i = 0; i < video.textTracks.length; i++) {
   video.textTracks[i].mode = 'hidden';

The video.textTracks property contains an array of all the text tracks attached to the video. We loop through each one and set its mode to hidden.

Note: The WebVTT API gives us access to all the text tracks that are defined for an HTML5 video using the <track> element.

Building a subtitle menu

Our aim is to use the subtitles button we added earlier to display a menu that allows users to choose which language they want the subtitles displayed in, or to turn them off entirely.

We have added the button, but before we make it do anything, we need to build the menu that goes with it. This menu is built dynamically, so that languages can be added or removed later by simply editing the <track> elements within the video’s markup.

All we need to do is to go through the video’s textTracks, reading their properties and building the menu up from there:

var subtitlesMenu;
if (video.textTracks) {
   var df = document.createDocumentFragment();
   var subtitlesMenu = df.appendChild(document.createElement('ul'));
   subtitlesMenu.className = 'subtitles-menu';
   subtitlesMenu.appendChild(createMenuItem('subtitles-off', '', 'Off'));
   for (var i = 0; i < video.textTracks.length; i++) {
      subtitlesMenu.appendChild(createMenuItem('subtitles-' + video.textTracks[i].language, video.textTracks[i].language,         video.textTracks[i].label));

This code creates a <a href=”” title=”The DocumentFragment interface represents a minimal document object that has no parent. It is used as a light-weight version of Document to store well-formed or potentially non-well-formed fragments of XML.” documentFragment, which is used to hold an unordered list containing our subtitles menu. First of all an option is added to allow the user to switch all subtitles off, and then buttons are added for each text track, reading the language and label from each one.

The creation of each list item and button is done by the createMenuItem() function, which is defined as follows:

var subtitleMenuButtons = [];
var createMenuItem = function(id, lang, label) {
   var listItem = document.createElement('li');
   var button = listItem.appendChild(document.createElement('button'));
   button.setAttribute('id', id);
   button.className = 'subtitles-button';
   if (lang.length > 0) button.setAttribute('lang', lang);
   button.value = label;
   button.setAttribute('data-state', 'inactive');
   button.addEventListener('click', function(e) {
      // Set all buttons to inactive, i, a) {
         subtitleMenuButtons[i].setAttribute('data-state', 'inactive');
      // Find the language to activate
      var lang = this.getAttribute('lang');
      for (var i = 0; i < video.textTracks.length; i++) {
         // For the 'subtitles-off' button, the first condition will never match so all will subtitles be turned off
         if (video.textTracks[i].language == lang) {
            video.textTracks[i].mode = 'showing';
            this.setAttribute('data-state', 'active');
         else {
            video.textTracks[i].mode = 'hidden';
      } = 'none';
   return listItem;

This function builds the required <li> and <button> elements, and returns them so they can be added to the subtitles menu list. It also sets up the required event listeners on the button to toggle the relevant subtitle set on or off. This is done by simply setting the required subtitle’s mode attribute to showing, and setting the others to hidden.

Once the menu is built, it is then inserted into the DOM at the bottom of the videoContainer.

Initially the menu is hidden by default, so an event listener needs to be added to our subtitles button to toggle it:

subtitles.addEventListener('click', function(e) {
   if (subtitlesMenu) { = ( == 'block' ? 'none' : 'block');

subtitle menu CSS

We also added some rudimentary styling for the newly created subtitles menu:

.subtitles-menu {

.subtitles-menu li {

.subtitles-menu li button {
    padding:2px 5px;

Styling the displayed subtitles

One of the less well known about and supported features of WebVTT is the ability to style the individual subtitles (something called text cues) via CSS Extensions.

The ::cue pseudo-element is the key to targetting individual text track cues for styling, as it matches any defined cue. There are only a handful of CSS properties that can be applied to a text cue:

For example, to change the text colour of the text track cues you can write:

::cue {

If the WebVTT file uses voice spans, which allow cues to be defined as having a particular “voice”:

00:00:00.000 --> 00:00:12.000

Then this specific ‘voice’ will be stylable like so:

::cue(v[voice='Test']) {

Note: Some of the styling of cues with ::cue currently works on Chrome, Opera, and Safari, but not yet on Firefox.

Browser Compatibility

Browser support for WebVTT and the <track> element is fairly good, although some browsers differ slightly in their implementation.

Internet Explorer

Since Internet Explorer 10+ subtitles are enabled by default, and the default controls contain a button and a menu that offers the same functionality as the menu we just built. The default attribute is also supported.

Note: IE will completely ignore WebVTT files unless you setup the MIME type. This can easily be done by adding an .htaccess file to an appropriate directory that contains AddType text/vtt .vtt.


Safari 6.1+ has similar support to Internet Explorer 11, displaying a menu with the different available options, with the addition of an “Auto” option, which allows the browser to choose.

Chrome and Opera

These browsers have similar implementations again: subtitles are enabled by default and the default control set contains a ‘cc’ button that turns subtitles on and off. Chrome and Opera ignore the default attribute on the <track> element and will instead try to match the browser’s language to the subtitle’s language.


Firefox’s implementation was completely broken due to a bug, leading to Mozilla turning off WebVTT support by default (you can turn it on via the media.webvtt.enabled flag.) However, this bug looks to have been fixed and WebVTT support re-enabled as of Gecko 31, so this will not be a problem for Firefox final release users for much longer (on Gecko 29 as of the time of this writing.) this has been fixed as of Firefox 31, and everything works as it should.


If, after reading through this article you decide that you can’t be bothered to do all of this and want someone else to do it for you, there are plenty of plugins out there that offer caption and subtitle support that you can use.

This small plugin implements subtitles, captions, and chapters as well as both WebVTT and SRT file formats.
This video player is very extensive and does a lot more than simply support video captions. It supports WebVTT, SRT, and DFXP file formats.
Another complete video player that also support video captions, albeit only in SRT format.
LeanBack Player
Yet another video player that supports WebVTT captions as well as providing other standard player functionality.
This player also supports captions through WebVTT and SRT files.
Supports WebVTT video subtitles.

Note: You can find an excellent list of HTML5 Video Players and their current state at HTML5 Video Player Comparison.


Comments are now closed.

  1. Eld wrote on July 10th, 2014 at 05:09:

    will firefox 31 can finally support the new 60fps youtube?

    1. Robert Nyman [Editor] wrote on July 10th, 2014 at 10:41:

      I don’t see why it wouldn’t, but I haven’t tested that. Best place to ask for feature support like that is Firefox Support.

  2. alexander farkas wrote on July 10th, 2014 at 08:17:

    Maybe, you want to add webshim’s mediaplayer, which also not only supports subtitles, captions and chapters including a menu, but also the textTrack API. To add, read change textTracks of a medialement.

    Here is a small example using subtitles and chapters:

    And here is one using the textTrack API:

    1. Robert Nyman [Editor] wrote on July 11th, 2014 at 00:59:

      Thanks for the suggestion!

    2. Junior wrote on July 12th, 2014 at 18:02:

      @alexander: just awesome…

      I have no flash installed and watch youtube videos via html5 player… And it’s so terrible… I thought it happened because my mid-notebook-specs, but obviously it’s wrong… Your examples play fluid here…

      Congratulations for the job!

  3. alexander farkas wrote on July 10th, 2014 at 19:17:

    Something about your code:

    You do set all textTracks initially to hidden, in case the browser has set it to showing. But the normal mode is disabled. hidden means, that they are not showing but proccessed. Especially, if you have a lot of different tracks, this can add some needless pressure to the browser. Maybe it would better to set them to disabled, or only to hidden, if it was showing before.

    Another point, I always hated those videoplayer code tutroials, where the script changed the visual state of the play button because the play button was clicked. The UI should reflect the state of the video/textTracks. And only change the visual change according to the states and the events comming form the video element. In case of the textTracks object, there is a change event, which is dispatched the mode state of an textTrack is changed. This way the menu stays in sync with the right mode state, even if the mode is changed by another script.

    1. Robert Nyman [Editor] wrote on July 11th, 2014 at 01:01:

      Appreciate the feedback, valid things to think about!

Comments are closed for this article.