Convert SRT to ASS
Turn SRT files into ASS. Every cue becomes a dialogue line in one default style, with its timing, line breaks, italics, bold, font colors and position tags.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop SRT files on the dialor turn it to pick what to do
SRT subtitles in an ASS file.Every cue carries over with its timing, line breaks and styling tags.
What you get
One ASS file in which every SRT cue becomes a dialogue line. All lines use one default style.
Each line keeps its start and end time and its line breaks. Italics, bold, font colors and position tags are kept too.
One default style
The converter does not sort cues into different styles. Every dialogue line uses the same default style. ASS is the format that supports positioning, fonts and effects, but the file you get is built from the cues and tags in your SRT.
When it stops
If the SRT cannot be parsed, the conversion stops with
input_corrupted. No ASS file is made in that case.To go the other way, use ASS to SRT.
SRT and ASS.What each format is.
The formats
SubRip Subtitle
SubRip subtitles. Numbered cues with start and end times, the most common subtitle file.
- Extensions
- .srt
- MIME type
- application
/x -subrip - Kind
- Text and data
SubStation Alpha Subtitle
SubStation Alpha subtitles with positioning, fonts and effects.
- Extensions
- .ass .ssa
- MIME type
- text
/x -ssa - Kind
- Text and data
In your code.The same SRT to ASS conversion through the API, for your app or your agent.
$ cv convert report.srt report.ass$ cv convert report.srt report.assQuestions.What people ask about SRT to ASS.
Yes. Italics, bold, font colors and position tags from the cues are kept on their dialogue lines.
Yes. Each dialogue line has the start and end time of its cue.
No. This conversion has no options, and every cue uses one default style.
The file could not be parsed. The conversion stops and does not produce an ASS file.