All Tools View Categories About Contact Privacy

HTML Tag Adder

Bulk-add italics, bold or underline to subtitle text.

Runs entirely in your browser — no data is uploaded or stored.

Add italics for song lyrics or thoughts; remember some players ignore inline tags.

About this tool & how to use it
  • Three choices in the Tag dropdown: Italic, bold and underline cover the inline styles that mainstream subtitle renderers actually understand.
  • One pair per cue: The opening tag goes before the cue text and the closing tag after it, so a multi-line caption is wrapped once rather than tagged on each line.
  • Whole-file consistency: Every cue in the SRT Content box receives the same treatment in one run, which is what italicised lyric and forced-narrative tracks require.
  • Timings and numbering preserved: Only the text changes, so the tagged file remains frame-accurate against the same video without any re-sync.
  • Line structure kept: Existing line breaks inside a cue survive the wrap, so your two-line balance is not disturbed by adding emphasis.
  • Reversible with the stripper: Because the tags are ordinary inline markup, the HTML Tag Stripper removes them cleanly if you change your mind or need a plain delivery.
  • Predictable output for QC: Every cue comes out in the same shape, which makes a visual check of the tagged file quick and unambiguous.
  • No upload required: The file is parsed and rewritten locally in the browser, keeping unreleased material off any server.
  1. Click Load sample to place an example subtitle file in the SRT Content box and see how the wrapping looks.
  2. Paste your own file into the SRT Content box, keeping the numbering and timing lines exactly as they are.
  3. If the file already contains markup, run it through the HTML Tag Stripper first so that the new tag is not nested inside an old one.
  4. Choose italic, bold or underline in the Tag dropdown according to the convention your delivery requires - italics is the usual choice for lyrics and foreign dialogue.
  5. Press Run and inspect the output, confirming that each cue opens and closes with the tag and that no timecode has moved.
  6. Click Copy or Download to save the styled file as an .srt.
  7. Play the file in the target player before delivery, since some hardware decoders ignore inline styling and will simply show plain text.

Example 1 - italicising a song lyric track. With Tag set to italic, every cue in the lyric file is wrapped in one pass.

Before:
5
00:01:30,000 --> 00:01:33,500
And the tide came in
like it always does

After:
5
00:01:30,000 --> 00:01:33,500
<i>And the tide came in
like it always does</i>

One tag pair spans both display lines, the internal line break is kept, and the timecodes are identical, so the lyric track stays in sync while reading as italics throughout.

Example 2 - a bold second-language track. Choosing bold turns Please remain seated. into <b>Please remain seated.</b> in every cue, giving a whole subtitle stream a distinct look next to the primary language track without touching a single timecode.

About HTML Tag Adder

The HTML Tag Adder applies one inline style tag to every cue in a SubRip file at once. Paste the subtitles into the SRT Content box, pick italic, bold or underline from the Tag dropdown and press Run; you get a complete SRT, downloadable as an .srt file, in which each cue's text is wrapped in an opening and closing tag such as <i> and </i>, with numbering and timecodes unchanged.

Uniform emphasis is a delivery requirement, not decoration. Forced-narrative and foreign-dialogue tracks are conventionally italic, song lyric subtitles are usually italicised throughout, and some house styles ask for bold or underline to separate one language track from another. Subtitlers, release groups, e-learning producers and localisation vendors all need to tag a whole file consistently.

The mechanics are deliberately predictable: the opening tag goes before the first character of the cue and the closing tag after the last, so a two-line caption is enclosed by a single pair spanning both lines. Existing markup is not inspected, so running the tool twice nests tags - strip a styled file first, then apply the tag you want. Timings, cue order and line breaks are all preserved.

Everything happens in your browser with no upload, and whole-file tagging is instantaneous even on long tracks.

Features

  • Three choices in the Tag dropdown: Italic, bold and underline cover the inline styles that mainstream subtitle renderers actually understand.
  • One pair per cue: The opening tag goes before the cue text and the closing tag after it, so a multi-line caption is wrapped once rather than tagged on each line.
  • Whole-file consistency: Every cue in the SRT Content box receives the same treatment in one run, which is what italicised lyric and forced-narrative tracks require.
  • Timings and numbering preserved: Only the text changes, so the tagged file remains frame-accurate against the same video without any re-sync.
  • Line structure kept: Existing line breaks inside a cue survive the wrap, so your two-line balance is not disturbed by adding emphasis.
  • Reversible with the stripper: Because the tags are ordinary inline markup, the HTML Tag Stripper removes them cleanly if you change your mind or need a plain delivery.
  • Predictable output for QC: Every cue comes out in the same shape, which makes a visual check of the tagged file quick and unambiguous.
  • No upload required: The file is parsed and rewritten locally in the browser, keeping unreleased material off any server.

How to Use

  1. Click Load sample to place an example subtitle file in the SRT Content box and see how the wrapping looks.
  2. Paste your own file into the SRT Content box, keeping the numbering and timing lines exactly as they are.
  3. If the file already contains markup, run it through the HTML Tag Stripper first so that the new tag is not nested inside an old one.
  4. Choose italic, bold or underline in the Tag dropdown according to the convention your delivery requires - italics is the usual choice for lyrics and foreign dialogue.
  5. Press Run and inspect the output, confirming that each cue opens and closes with the tag and that no timecode has moved.
  6. Click Copy or Download to save the styled file as an .srt.
  7. Play the file in the target player before delivery, since some hardware decoders ignore inline styling and will simply show plain text.

Examples

Example 1 - italicising a song lyric track. With Tag set to italic, every cue in the lyric file is wrapped in one pass.

Before:
5
00:01:30,000 --> 00:01:33,500
And the tide came in
like it always does

After:
5
00:01:30,000 --> 00:01:33,500
<i>And the tide came in
like it always does</i>

One tag pair spans both display lines, the internal line break is kept, and the timecodes are identical, so the lyric track stays in sync while reading as italics throughout.

Example 2 - a bold second-language track. Choosing bold turns Please remain seated. into <b>Please remain seated.</b> in every cue, giving a whole subtitle stream a distinct look next to the primary language track without touching a single timecode.

Benefits

  • Convention-compliant tracks in one click: Forced-narrative, lyric and voice-over subtitles that must be fully italicised are produced instantly instead of cue by cue.
  • Visual distinction for viewers: A consistently styled track helps the audience tell sung lyrics, inner thoughts or a second language apart from ordinary dialogue.
  • No hand-editing errors: Tagging hundreds of cues manually reliably produces a few unclosed tags; a mechanical pass never does.
  • Sync is guaranteed safe: Since timecodes and cue order are untouched, styling can be applied at the very end of the process with no re-check against picture.
  • Easy to undo: If a platform turns out to reject markup, the stripper returns the file to plain text with no loss of words or timing.
  • Keeps work private: Styling runs in the browser, so pre-release episodes and client tracks are never uploaded anywhere.

Frequently Asked Questions

Which tags can I add?
Italics <i>, bold <b> or underline <u>, wrapped around each cue’s text.
Will every player show it?
Support varies; many web players and editors honor it, while some ignore inline tags.
Can I combine with stripping?
Yes — strip first, then add the style you want for a consistent result.
Is my file uploaded?
No, adding runs locally.