Request a feature

If an existing tool would be more useful with a small addition, let us know. Feature requests are easier to fulfil than new tool requests because the core functionality already exists.

Types of feature requests

• New option — an additional toggle or setting (e.g. "add option to preserve cue identifiers on VTT → SRT").
• New output format — export in a format that is missing (e.g. "add JSON output to the word counter").
• Better UX — a clearer error message, better layout, keyboard shortcut.
• Performance — handle larger files faster.
• Accessibility — better screen reader support, contrast, keyboard navigation.

How to submit

Email features@subtitle-convert.pages.dev with:

Tool URL:
Current behaviour:
Desired behaviour:
Why it matters:
Frequency of use:

Examples of good feature requests

• "On the SRT to VTT tool, add an option to omit cue identifiers when the source SRT has no cue numbers. Currently the tool always generates cue identifiers from source numbers; but some source files have none, so the output has empty identifiers."
• "On the Line Length Checker, allow setting the limit to a range (e.g. 30-50) and flag lines outside the range. Currently it flags only lines above the max."

Examples of feature requests we are unlikely to fulfil

• Adding a backend API (would break browser-only privacy).
• Adding mandatory AI (would break browser-only privacy).
• Adding ASS/SSA conversion without a specialised parser (feasible but large scope; possible in future).
• Adding tracking or analytics (breaks privacy).

What happens next

• Requests are reviewed monthly.
• We may email you for clarification.
• Small features are typically implemented quickly.
• Large features go on the roadmap.