SBV to JSON
Or paste subtitle text
What this conversion changes
Nothing is lost in this direction — every feature of the source format has somewhere to go in the target format.
This list comes from the capability matrix for these two formats, not from the particular file you loaded. A specific file may lose more if it uses features the format allows but the matrix does not model.
This page converts SBV to JSON. Drop a file in — or paste the text — and you get the JSON version back. The conversion runs entirely in your browser, so nothing is uploaded and no account is needed.
Nothing is lost in this direction. Every feature SBV can express has an equivalent in JSON, so the output is the same subtitles in a different wrapper — the timeline, the line breaks and the text all survive. That holds for any SBV file, including one that uses every feature the format allows.
One file is fine, and so is a whole season: the queue works through them in order and the results come down together as a single ZIP.
Examples
A typical SBV file, converted to JSON
Input
0:00:01.000,0:00:03.500
The quick brown fox.
0:00:04.000,0:00:06.250
Jumps over the lazy dog.
0:00:07.000,0:00:09.000
Two lines here.
And a second one.
Output
{
"version": 1,
"cues": [
{
"start": 1000,
"end": 3500,
"lines": [
"The quick brown fox."
]
},
{
"start": 4000,
"end": 6250,
"lines": [
"Jumps over the lazy dog."
]
},
{
"start": 7000,
"end": 9000,
"lines": [
"Two lines here.",
"And a second one."
]
}
]
}
Nothing is dropped here: compare the two sides line for line.
The same conversion on an awkward input
Input
0:00:02.000,0:00:04.000
Carriage-return line endings.
0:00:06.000,0:00:08.000
Indented timecode, no final newline.Output
{
"version": 1,
"cues": [
{
"start": 2000,
"end": 4000,
"lines": [
"Carriage-return line endings."
]
},
{
"start": 6000,
"end": 8000,
"lines": [
"Indented timecode, no final newline."
]
}
]
}
This is the kind of damage real files have — mixed line endings, stray whitespace, fields left empty. Compare it with the tidy example above to see what the parser forgives.
Frequently asked questions
What does the output look like when SBV becomes JSON?
Like JSON: an array of cue objects, each with its own `id`, `start` and `end`. Every SBV cue becomes one JSON cue, in the same order, with the same text.
Are the SBV timings exact in the JSON file?
Yes, to the millisecond — which is as fine as either format goes. SBV writes a moment as `0:00:04.126` and JSON writes the same moment as `4126`; nothing is rounded or shifted between the two, and a cue that was on screen for 2.9 seconds still is.
How does a two-line SBV cue come out in JSON?
As two entries in the cue's `lines` array. The pairing survives — the two SBV lines still belong to one subtitle in the JSON output, and a player shows them together.
Do SBV cues keep their order in the JSON output?
Yes, and they are sorted by start time on the way — earliest first, which is how every format here expects them and how players read them. If your SBV file listed its cues out of sequence, the JSON output puts them back in order; that is a change to the file's structure rather than its content, and it is deliberate.
Can I convert the JSON back to SBV?
Yes, and that is the lossy direction: styling, positioning and karaoke have nowhere to go in SBV. This way round nothing is lost, so that cost only appears if you go back.
Does the JSON output keep the SBV file's encoding?
No — the output is UTF-8, with Unix line endings and no byte-order mark, whatever the SBV file used. A file that arrives in UTF-16, or in a Windows single-byte encoding, is decoded on the way in (the result panel says so when that happens); what comes out is always the same UTF-8 JSON.