Report a bug

Last updated 2025

If a tool is not working as expected, please send a report to bugs@subtitle-convert.pages.dev with the details below. The more specific you are, the faster we can fix it.

What to include

Which tool — the tool name or URL (e.g. SRT to VTT, /tools/srt-to-vtt.html).
What you did — the steps you took (e.g. pasted an SRT file, clicked "Convert").
What happened — the observed behaviour (e.g. output was empty, error message appeared).
What you expected — the correct behaviour (e.g. output should contain VTT cues).
Browser — name and version (e.g. Chrome 121, Firefox 122, Safari 17).
Operating system — Windows, macOS, Linux, iOS, Android.
A description of the file — approximate size, cue count, whether it uses unusual formatting. Do NOT attach the full file.

How to describe file structure without sending the file

We do not accept subtitle files over email (privacy reasons). Instead, describe the structure:

"SRT with 250 cues, all comma-separated timestamps."
"VTT with header and NOTE blocks; some cues have position settings."
"File uses only ASCII characters except a few emoji in cue 42."

If you believe the bug requires a specific file, create a minimal reproduction by extracting just the cues that trigger the issue.

What we will do

Acknowledge receipt within a few business days.
Reproduce the bug and identify the cause.
Fix and deploy. Since Subtitle Convert is a static site, fixes deploy immediately.
Update the tool's documentation or known limitations if the behaviour is intentional.

Security issues

For security issues (vulnerabilities, XSS, etc.), please see the security policy and use a private disclosure channel rather than public bug reporting.

What is not a bug

Unsupported formats (ASS, SSA, SBV, SUB) — intentional, documented in format guide.
Very large files (>15 MB) being slow — documented limitation.
Files with exotic encodings displaying incorrectly — documented limitation.
Subtitle positioning being lost on VTT → SRT conversion — SRT does not support positioning.