Choose the export by where the file goes next
Start with the destination app and the timing detail you need to preserve. There is no single caption format that keeps every feature for every player.
Try this in the assistantThis guide is in English. The assistant supports 83 interface languages.
A practical format decision
Use this as a starting point, then check the importing application's supported formats.
- Music-player lyrics: consider LRC or enhanced LRC when the player supports word timing.
- Video-editor subtitle import: SRT is a common cue-based handoff.
- Web-player captions: WebVTT fits web timed-text workflows.
- Further processing: keep structured JSON or the original detailed timing source.
Know what the conversion may discard
Styling, word boundaries, positioning and metadata do not have equivalents in every format. A simple delivery file can be perfectly useful while still containing less information than the original. Save the source alongside the export.
Ask a question with a destination
'Convert my captions' leaves several choices open. 'I have enhanced LRC and need editable subtitles in my video editor' gives the assistant a source, a destination and an editing constraint. Mention whether the result must be a separate text track or burned into the picture.
Questions about this workflow
Which format is best?
The format your destination supports and that retains the information you need. Keep a richer source file if you expect to edit again.
Can a conversion add missing timing detail?
It can adapt structure, but it cannot recover exact word boundaries that were never in the source.
Should I download more than one format?
That can help when delivering to several apps. Label each file clearly and preserve a source version before later repairs.