TikTok Transcript Exporter: What You Get (TXT, SRT, VTT)

An exporter hands you the words. Not a subtitle file, not a timed track — the words. That gap trips up almost everyone who searches for a "TikTok transcript exporter" and expects an .srt file to drop out of the other end.

The gap matters the moment you try to burn captions back onto a video, translate a script, or cut a clip into a longer edit. So here's what an export really contains, why renaming a file never works, and the shortest honest route from plain text to a timed subtitle file.

What a TikTok Transcript Exporter Actually Returns

The output object is smaller than most people expect. Ours holds two fields: the transcript as one plain string, and a word count. No segment array, no per-line timing, no cue list. The download button is labeled .txt because that is the only file it writes.

What that buys you is real: copyable text, the word count already done, an editable box where you can fix misheard names before saving, and 20 free exports a day with no account. What it can't buy you is anything a subtitle player understands. Subtitles need a start and end time for every line. A string of words carries none.

• Included: the spoken script, word count, inline editing, a .txt file on your disk.
• Missing: timestamps, speech-matched line breaks, speaker labels, any .srt or .vtt output.

One loss the export can't recover: on-screen text. Punch-in captions, hashtags, and styled overlays never appear, because extraction reads the audio or TikTok's auto-caption data — not the pixels. Our TikTok caption download guide covers where that boundary sits and why a burned-in caption is invisible to every extractor on the market.

Why "Export as SRT" Is Not a Rename

This is the failure that eats an afternoon. You take your .txt transcript, rename it to .srt, drop it into a player, and get nothing. Or the file loads and every cue sits blank.

Renaming changes the extension and stops there. A WebVTT file must open with the literal line WEBVTT, and per the W3C's WebVTT specification a browser rejects the entire track when that header is missing or misspelled. SRT does the reverse: no header at all, but each cue needs a sequential number. The two formats even disagree on the punctuation inside every timestamp.

SRT — comma separator, index required
1
00:00:01,000 --> 00:00:04,000
Text goes here

VTT — WEBVTT header required, dot separator, index optional
WEBVTT

00:00:01.000 --> 00:00:04.000
Text goes here

Format	Header line	Milliseconds	Cue numbers	Opens in
.txt	none	no timing at all	none	Any editor. No player reads it as captions.
.srt	none	comma: 00:00:01,000	required	VLC, desktop editors, most upload forms
.vtt	WEBVTT (required)	dot: 00:00:01.000	optional	HTML5 video, web players, streaming platforms

If you need VTT and only have SRT, the conversion is three edits: add the WEBVTT header, swap commas for dots in every timestamp, drop the index numbers. Going the other way adds the numbers back and reverses the punctuation. Both directions keep the cue text untouched — which is why a script that does only the rename keeps failing.

Building a Timed Subtitle File From an Exported Transcript

Since nothing hands you timings, you generate them. The method is arithmetic, and it takes about ten minutes for a one-minute video.

Start from the word count your export already gave you, and a speaking rate. TikTok delivery runs fast; we calibrate at roughly 2.5 words per second (150 words per minute) as a working assumption and then correct it against the real video length. Ten words per cue puts each line on screen for about four seconds, which sits inside the comfortable reading range and matches how short-form captions are normally chunked.

A 60-second TikTok returns about 150 words at that rate — fifteen cues of roughly four seconds each. The first two blocks of the SRT you'd write look like this:

1
00:00:00,000 --> 00:00:04,000
first ten words of the script

2
00:00:04,000 --> 00:00:08,000
next ten words of the script

Real talk: constant-rate timing drifts, every time. Creators pause, hold a beat for a punchline, or let a b-roll stretch run with no speech — and your cue clock keeps marching. The fix is one correction pass, not a rewrite. Compare your last cue's end time to the actual video duration, then scale every timestamp by the ratio. A transcript whose final cue lands at 4:10 on a 4:00 video is 4% long, so multiply the value by 0.96 and the file snaps back into sync.

Run the drift check before you polish anything else. Fixing punctuation on a file with wrong timing wastes the pass.

When Timestamps Are Worth the Extra Work

Three situations justify building the timeline. Re-uploading a clip with burned-in subtitles, running a translation workflow where a translator needs cue boundaries, and cutting timecoded notes for a client review. Everything else — writing, research, repurposing a script into an article, analyzing hooks — is better served by plain text, because a subtitle file only adds obstacles for a writer.

Not sure which one you're in? If the file's destination is a person reading it, .txt wins. If the destination is software that renders text over video, you need timings, and there is no way around generating them.

Export the Text First

Every route to a subtitle file starts with clean text, so get that part out of the way in seconds. CapFetch's TikTok transcript exporter returns the full script, an editable box, and a .txt download with no sign-up — paste a link and the words are yours. For the surrounding workflow, the TikTok transcript generator guide covers transcript quality and failure modes, and the three-platform caption comparison shows what changes when the same script lives on Reels or Shorts instead.