SRT Tools

Contact & Help — Self-Serve, Like the Tools

SRT Tools has no accounts, no database and no uploads — and that extends to support. This page maps every help resource we publish, explains how to report problems effectively, and documents exactly what happens (and does not happen) to your files and data.

Reviewed by the SRT Tools team · Updated

14
free tools
6
languages
0
file uploads, ever
2 MB
max file size
10,000
cues per file

Where to Get Help Fastest

Because every tool runs locally and deterministically, most problems resolve in one of three places. First: the FAQ section on the page you are using — each of the 14 tools carries six questions answered for that exact tool, including its known limits. Second: the worked example on each page — loading the built-in sample proves the engine works and isolates whether the issue is with a specific file. Third: the format explainer pages, What is an SRT file and the VTT file viewer, which cover the structural rules that most broken files violate.

If a file fails to parse, the tool itself tells you why: invalid timestamps report their line numbers, missing WEBVTT headers are named explicitly, and ASS files without an [Events] section are rejected with an explanation rather than a mystery error. Those messages are the first thing to read — they usually point at the exact line to fix in your subtitle file.

Per-tool FAQs

Every tool page ends with six tool-specific answers — start there; they cover the failure modes we see.

Try the sample

One click loads a known-good file. If the sample works and yours does not, the file is the difference.

Format explainers

The SRT and VTT anatomy pages show the exact block structure a valid file must follow.

Universal converter

Not sure what format your file even is? The SRT converter page auto-detects it from content.

Why There Is No Support Inbox (for Now)

Deliberately, SRT Tools currently publishes no support email and operates no ticket queue. The site holds no user data, processes no uploads and runs no accounts — an inbox would be the only place personal data could accumulate, and we chose not to create one until there is a real need and a real policy behind it. Everything we can help with today is published on the pages themselves: usage steps, format rules, failure messages and honest limits.

This is also why our privacy statement is short enough to verify: files are read by your browser with the File API, parsed in the page, and downloaded back to your device. No subtitle content, file name or parse result is transmitted anywhere. The site loads no third-party trackers beyond optional, privacy-respecting analytics that never touch file content.

Reporting a Problem Usefully

If you plan to report a bug — through whatever channel the site lists at that time — three pieces of information turn a report into a fix. One: the exact tool page URL (each page is a separate tool, so 'the converter' is ambiguous across 14 pages). Two: the notice text the tool showed, including line numbers — the messages are keyed to the parser's internal error codes and pinpoint the cause immediately. Three: whether the built-in sample worked on the same page, which cleanly separates a site bug from a file issue.

Never paste confidential subtitle content into a public report. A description of the structure — 'cue numbering starts at 0', 'timestamps use dots', 'file has a UTF-16 BOM' — is enough for almost every parsing issue, and the error messages usually already name the line.

Troubleshooting the Three Most Common Failures

Garbled characters almost always mean the file was saved in a legacy encoding instead of UTF-8; the tools read UTF-8 and UTF-16 with a BOM and warn when replacement characters appear, so re-saving the file as UTF-8 in any editor resolves it. A VTT that refuses to load is usually missing the WEBVTT first line — required by the W3C specification — or is actually SRT wearing a .vtt extension, which the viewer names explicitly. And conversions that come out empty are blocked on purpose: downloads stay disabled until the source parses cleanly, because shipping an empty file with a success message is worse than an honest error.

For timing questions — LRC last-line duration, TXT estimated pacing, the 10-millisecond tolerance when converting to and from ASS — each tool's settings panel and FAQ state the exact defaults and bounds. Those numbers are enforced in the shared engine's code, so the documentation and the behavior cannot drift apart.

Sources & specifications