TEMPORARY MEDIA WORKSPACE / VTT TO SRT

VTT to SRT

Convert validated WEBVTT cue timing and text into sequential UTF-8 SRT blocks for editors and platforms that require SubRip.

Request-scoped temporary processingAdd one UTF-8 VTT file up to 2 MB containing no more than 10,000 valid, ordered subtitle cues.No account required

Local API readinessMedia service ready

The processor required by this tool is available, and this worker can accept a temporary job.

One bounded job runs per API worker by default.

Step 1 / source

Add the source media

1 VTT / 2 MB

Source intake

Drop one media file here

Choose the VTT track needed in an SRT-only editing or delivery workflow.

Browse media

UTF-8 VTT1 VTT / 2 MB

Checking publication status before file selection...

Temporary server workspace

The selected bytes are sent only to the Nirmion media API for this request. Processing uses a private temporary workspace rather than permanent catalogue storage.

Request-scoped cleanup

Server-side source and result files are removed when the response stream closes. Re-downloads use the result Blob retained only in this browser tab.

Original stays unchanged

Nirmion writes a separately named result containing nirmion_tools and never overwrites the selected source file.

Know the product contract

What goes in, what changes, what comes back

Every media page documents the accepted source, the selected FFmpeg transformation, the output container, and the limits that can affect the job.

Prepare the source

Use a cue-focused VTT that you have checked for unsupported STYLE or REGION blocks, unusual positioning, and platform-specific metadata.

Apply one operation

The WEBVTT header and cue identifiers are removed, timestamps use commas, and cues receive sequential SRT numbers.

OUT

Receive a separate file

Import the SRT into the target application and review tags, line breaks, and timing.

Plain-language method

How WebVTT cues map to SRT

SRT has fewer layout capabilities than WebVTT, so advanced VTT presentation cannot be represented by this conversion.

01
Choose valid source media
Use a cue-focused VTT that you have checked for unsupported STYLE or REGION blocks, unusual positioning, and platform-specific metadata.
02
Review the operation settings
No settings are required; unsupported layout blocks are rejected to avoid silent data loss.
03
Inspect and download the result
Import the SRT into the target application and review tags, line breaks, and timing.

Useful when

Practical jobs this tool handles

Import web captions into an SRT editor.
Prepare captions for an SRT-only upload.
Create a portable review copy.

Before processing

Check the source and output choices first

Check for VTT layout blocks.
Retain the original VTT.
Test the SRT in the target app.
Review timing against media.

Container and codec

Understand the output format

NOTE blocks are omitted. STYLE and REGION blocks are rejected rather than silently discarded.

Know the boundary

VTT-only layout is not portable to SRT

Positioning, regions, styles, and platform-specific settings may need manual recreation after conversion.

Quick answers

Questions before you process media

These answers describe the actual upload, FFmpeg processing, download, and temporary-retention contract.

Are NOTE blocks included?

No. They are non-caption comments.

What happens to STYLE blocks?

The request is rejected so the loss is visible.

Does cue text remain?

Yes, for supported cue blocks.