Turn SRT subtitles into JSON. It is converted in your browser, so the file never leaves your device.
Drop SRT files here
or choose from your computer paste with Ctrl V
from Photos or Files
Ready · other file types work too0 bytes uploaded, ever
Drop SRT (SubRip) files onto the box above, or click it to choose them. ToAny reads the file's contents to detect the type, so a wrong extension does not matter.
Press Convert. There is nothing else to set. The work happens in this tab.
Save the JSON, or download everything as one ZIP if you converted several files.
The SRT to JSON converter is part of this page and runs inside your browser. Your subtitles are never sent to ToAny or to anyone else.
Nothing has to travel to a server and back, so the conversion starts the moment you press Convert, even on a slow connection.
No sign-up, no email address and no watermark. Add several files and download them together as a ZIP.
SRT has almost no styling or positioning, and character encoding problems are common. JSON is what APIs and most programming languages read natively. SRT is at home in subtitles that must work almost everywhere; JSON is the usual choice for APIs and data exchanged between programs.
The text is read as UTF-8 or UTF-16, whichever the file is. An older file in another code page is read using the charset it declares, or as Windows-1252 if it declares none, so accented letters in an unlabelled legacy file can come out wrong. A file that is not text, such as the picture-based subtitles of a DVD, is refused instead of being converted to nonsense. The result is a JSON list with one object per cue: its number, start and end as clock times and in milliseconds, and its text.
SRT is the plain subtitle format nearly every player accepts: a number, a time range such as 00:01:02,500 --> 00:01:04,000 and one or two lines of text. It has no official specification and only basic styling, which is why it travels so well.
Opens in VLC, YouTube, Plex, most players and video editors
SRT converterJSON represents data as nested objects and lists in plain text. It is the default language of web APIs. Unlike a spreadsheet it can be nested to any depth, which is also why turning it into rows and columns takes a decision about how to flatten it.
Opens in Any text editor, every programming language, browser developer tools
JSON converter| SRTSubRip subtitles | JSONJSON data | |
|---|---|---|
| Stands for | SubRip subtitle | JavaScript Object Notation |
| Type | Subtitles | Structured data (text) |
| Compression | None | None |
| Introduced | Around 2000, by the SubRip program (no formal standard) | 2001, by Douglas Crockford |
| Opens in | VLC, YouTube, Plex, most players and video editors | Any text editor, every programming language, browser developer tools |
| Best for | Subtitles that must work almost everywhere | APIs and data exchanged between programs |
| File extension | .srt | .json |
No. The SRT to JSON conversion runs inside your browser, on your own phone or computer. The file is not sent to ToAny or to anyone else.
The content is carried over as faithfully as JSON allows; features that JSON does not have are left out.
Yes. Add as many as you like, convert them together and download each result or all of them as one ZIP.
The steps are the same everywhere because ToAny runs in the web browser: open this page in a current version of Chrome, Edge, Safari or Firefox, add the SRT file, press Convert and save the JSON. There is nothing to install.
Yes, but a subtitle file is small. Files up to 50 MB are accepted, far more than any real subtitle file. Beyond that the limit is your device's memory, since nothing is uploaded; a computer copes with large files better than a phone.