Skip to content
CutConvert
Post-production file converter

Convert EBU-STL to SRT

Decode binary EBU-STL subtitle files into clean, timed SRT. Full ISO 6937 character set including combining accents, at 25 or 30 fps.

Convert your files

Drop files here

browseEBU-STL subtitle filesConverted in your browser. Files never leave your device.About an hour of footage is free. Larger files: $3 each, or Pro $9/month for everything up to 50 MB.

up to 2 files · 200 KB each

free to start · project to project: $5 · every other conversion: $3 · Pro $9/month · pricing

Converting as a guest. A free account has no monthly cap on files within the free size limit.

Queue
0/2
No files queued yet — drop something above to begin.

How to convert STL to SRT

Convert STL to SRT online. CutConvert decodes binary EBU-STL subtitle files (EBU Tech 3264) into clean, numbered SRT subtitles you can edit or upload anywhere: GSI header, TTI blocks, teletext control codes, and the ISO 6937 character set all handled.

  1. Add your STL file

    Drag the .stl onto the drop zone. STL25.01 and STL30.01 formats are read; 3D-printing .stl models are politely rejected.

  2. Convert STL to SRT

    Press Convert. Subtitle blocks are decoded with frame-accurate timing: extension-block chains reassembled, comment blocks skipped, teletext codes stripped, combining accents composed.

  3. Download your result

    Download the converted file instantly, or a single ZIP archive when you convert a batch of files.

EBU-STL file and SRT subtitles, explained

An EBU-STL file is binary: a 1024-byte header followed by fixed-size subtitle blocks whose text uses ISO 6937, where accented letters are stored as two bytes (combining accent + base letter). This converter decodes all of it, including umlauts, ß, and the teletext control bytes other tools leave as garbage, and writes standards-compliant SRT. Decoding is verified cue-for-cue against the reference conversion pipeline published by IRT, the German broadcast research institute: identical text and frame-exact timing on a real broadcast file.

Decode binary EBU-STL subtitle files into clean, timed SRT. Full ISO 6937 character set including combining accents, at 25 or 30 fps. It is free to start, encrypted in transit, and converts a whole batch into one ZIP — sign in when you need large, high-volume jobs.

STL to SRT FAQ

Which STL variants are supported?

STL25.01 (25 fps) and STL30.01 (30 fps), open or teletext subtitles, with the Latin character table. Non-Latin character tables (Cyrillic, Greek, Arabic, Hebrew) decode on a best-effort basis with a warning.

Do German umlauts and French accents decode correctly?

Yes. ISO 6937 stores them as combining sequences (diaeresis + u = ü) and this decoder composes them properly, verified against a German-language broadcast file including ß.

What happens to subtitler comments in the file?

STL files can carry comment blocks (notes between subtitlers) that are not meant for air. They are skipped, and a warning tells you how many were found.

How accurate is the timing?

TTI in-cues and out-cues are converted at the file's own frame rate. On the IRT reference file, every cue matched the published reference timing to the millisecond.

Is it free?

Free to try on short files (about 10 minutes of program). Full-length subtitle files need a one-time $3 conversion or a paid plan.

Guides for this workflow

More converters

Why editors trust it

Free to start

Convert everyday batches for free. Create an account when you need large, high-volume jobs.

Batch in, one ZIP out

Convert a batch within your allowance and download a single ZIP, or one file if that is all you need.

Made for editors

Whole timelines from Premiere, Final Cut and Avid with transitions, markers, titles, keyframes, levels, nests and bins; captions that keep their italics, colour, placement and speakers across SRT, VTT, ASS, TTML, iTT, SCC and STL, any of them in, any of them out; transcripts into Premiere with the words the engine timed. Frame rates and timecode handled the way post expects.

Private by design

Files are converted in your browser. Queued files can be saved locally to restore your job after checkout. Conversion metadata helps us diagnose errors; file contents are not uploaded.

Questions, answered

Where are my files processed?

In your browser. The converter runs on your own machine and the file never leaves it; the site only records that a conversion happened. CutConvert never sees, stores, sells or shares your media.

Is it free? Do I need an account?

About an hour of footage per file is free, on every converter: 100 KB of subtitles or captions, 500 KB of Word transcript, 2 MB of transcript JSON, 1 MB of Resolve project, 5 MB of Final Cut XML, with Premiere projects and Avid AAF a little under the hour. Guests get five conversions a month, a free account has no monthly cap within those sizes, and above that project-to-project transfers are $5 per file. Every other conversion is $3, including project files to captions, reports or cut lists, and captions or transcripts into an editor. Pro is $9 a month ($90 a year) for every file type up to 50 MB; Studio is $19 a month ($190 a year) for files up to 500 MB. Paid-file access lasts 24 hours.

What do I get when I convert multiple files?

Drop several files and you get back one ZIP archive containing every converted file. Convert a single file and you get that one file back, no ZIP. Tick extra formats under the output chips and the same ZIP carries every one of them, and a file counts as one conversion whatever it is written to.

Which formats are supported?

Timelines: Premiere .prproj, DaVinci Resolve .drp (as exported, or gzip- or Zstandard-wrapped), Avid AAF and Final Cut FCPXML in; FCP7 XML, FCPXML, Resolve .drp, CMX 3600 EDL and shot-list CSV out. A Premiere or Final Cut edit travels with its transitions, markers, titles, opacity and scale keyframes, clip volume, speed changes, nested sequences, bins, audio channel routing and each file's own frame rate, wherever the output has a place for them; an Avid AAF brings its transitions, markers, clip levels with their keyframes, muted tracks, nested stacks and each clip's own rate. Captions and transcripts, read and written: SRT, WebVTT, SBV, ASS, TTML, DFXP, iTT, SCC, MCC (a second 608 channel comes out as its own file), EBU-STL, Avid caption TXT, CapCut drafts of any size, timed CSV, Word, plain text, Whisper, WhisperX, AssemblyAI, Deepgram, Rev.ai and CapCut JSON, TwitchDownloader chat logs as a chat replay, Premiere transcript JSON and .prtranscript, Rev, Otter and Word-style transcripts, with italics, colour, placement and speakers kept where the output can hold them and measured word timing into Premiere. EDLs become event CSV reports. The capability table lists what every pair keeps.

Can I pick a frame rate?

Yes. For EDL and Avid caption output you can choose 23.976, 24, 25, 29.97, or 30 fps, or let CutConvert auto-detect it from your source.