• Documentation
  • File formats
  • Subtitles (srt, sub, sbv)

Subtitles (srt, sub, sbv)

  • File extensions: .srt, .sub, .sbv
  • i18n type: SRT, SUB, SBV respectively

Transifex supports three subtitle file formats: SubRip, SubViewer, and YouTube captions. With the Video Subtitle Editor you can translate SubRip and SubViewer files while watching the video play in the translation editor.

SubRip (.srt)

SubRip is the native subtitle format of the SubRip program. It is one of the most used formats for subtitles, supported by most software video players, many subtitle creation/editing tools and some hardware home media players. YouTube also supports .srt files.

An entry in a .srt file may contain certain HTML tags, like <i>.

Titles and descriptions in .srt

If you need to translate titles and descriptions in SRT files, please follow the steps below:

  • Include both title and description in your localization file as follows:


    [1.IntroductionV2.srt_title] 1.Introduction V2

    [1.IntroductionV2.srt_description] This video explains.....{end of description}

    [2.DesireV2.srt_title]  2.Desire V2

    [2.DesireV2.srt_description] This video explains...{end of description}

    [3.ResponsibilityV2.srt_title] 3.Responsibility V2

    [3.ResponsibilityV2.srt_description] This video explains...{end of description}

  • In order to prevent translators from editing the text inside brackets, you can:

    • visit your translation checks settings page
    • Click SubRip subtitles (.srt) checks
    • Click Set up placeholder delimiters
    • Create a new placeholder as follows:


  • As a result, you will have the strings in the Editor like this:

    Subtitles in editor with Placeholder

SubViewer (.sub)

SubViewer files (.sub) are the native subtitle format of the SubViewer utility.

YouTube Captions (.sbv)

.sbv is the file format outputted by YouTube's Automatic Timing feature which creates automatically timed captions based on a transcript

Download Modes

  • The following table outlines what occurs to untranslated, unreviewed and un-proofread strings when using the API, CLI or UI to manipulate translation files:


* Proofreading needs to be enabled as an option for this logic to take effect. To learn how to enable proofreading click here.