If your CapCut caption export gives you an empty file — or no file at all — the most likely reason is that CapCut never counted your text as a caption. That distinction is buried in one parenthesis on CapCut's help page, and it rules out the most common way people put words on screen.
Once you know it, the rest of the troubleshooting gets short: there are only four things CapCut's own documentation blames, and you can check all four in a couple of minutes.
What CapCut's help page actually blames
CapCut's page "Why Do the Captions Fail to Export?" lists four root causes. Quoted as written:
"Text not generated through "Auto Caption Recognition" (only automatically recognized captions can be exported)" "Incorrect export settings" "File encoding or path issues" "Software version limitations: Update to the latest version"
Read the first one literally. Only automatically recognized captions can be exported. Text layers you typed yourself — a title, an on-screen label, a line you transcribed by ear into a text element — are text, not captions. The caption exporter has nothing to collect from them, so you get an empty or missing .srt while the words are still sitting there in your preview, perfectly visible.
This single sentence explains the overwhelming majority of "my SRT is empty" reports. It is also the one cause you cannot fix in the export dialog, which is why it is worth checking before anything else.
CapCut's help center does not publish a step-by-step procedure for turning existing text layers into recognized captions, so do not expect a toggle. On the related subtitle-import page, CapCut notes that its auto-captioning "supports ～30+ languages (e.g., English, Spanish, Japanese, Arabic)" — if your language falls outside that, check the official documentation for what is available in your version before assuming the feature is broken.
Fix 1: you are probably in the wrong export panel
The second root cause, "Incorrect export settings," has a precise meaning in CapCut's own instructions. For CapCut Desktop, the export settings check is two lines:
"Confirm "Caption Export" is selected, not "Video Export"" "Must choose SRT or TXT format"
On mobile, CapCut words it as an explicit toggle-off:
"Uncheck "Video Export," select only "Caption Export"" "Must choose SRT or TXT format (other formats not supported)"
So the failure mode is mundane and extremely common: you hit the normal export button, CapCut renders a video, and no subtitle file is ever written. Caption Export is a separate selection, not a side effect of exporting the video. If both are checked on mobile, uncheck the video one and run the caption export on its own — that is the official instruction, verbatim.
The format dropdown matters too. CapCut lists exactly two caption formats, SRT and TXT, and the mobile page adds "other formats not supported" to that pair.
Fix 2: encoding and file path
The third root cause — "File encoding or path issues" — is where CapCut gets unusually specific, and these two requirements are easy to violate without noticing.
For CapCut Desktop, the official resolution is:
"Convert SRT files to UTF-8 without BOM format (using Notepad++)" "Use English paths like
C:\CapCut\subtitles.srt"
For CapCut Online, the rule is phrased as a path standard:
"Export path must use ASCII characters only; avoid special symbols to prevent encoding errors"
Two practical consequences:
- "UTF-8" is not what CapCut asks for — it asks for UTF-8 without BOM. The byte-order mark is an invisible marker some editors write at the start of a UTF-8 file, and the wording of CapCut's instruction excludes it. The page even names the tool for the conversion, Notepad++, so treat "I saved it as UTF-8" as an unfinished check rather than a passed one.
- Your destination folder is part of the problem. If you are exporting into a path with accented characters, non-Latin script, emoji or unusual punctuation, move the export to a plain ASCII path first.
C:\CapCut\subtitles.srtis the example CapCut itself gives.
If a caption export fails on a folder you have used a hundred times, check whether a synced-folder path or a renamed user directory quietly introduced a non-ASCII character.
Fix 3: the documented fallback, and what to do with SRT afterwards
For CapCut Online, the help page gives a fallback that is worth knowing because it turns a dead end into a two-step process:
"If export issues occur, first export as TXT format, then convert to SRT using external tools"
That is CapCut's own recommendation, not a workaround someone invented: export the plain-text version, then convert outside CapCut.
The same logic applies if your destination needs WebVTT. The formats CapCut lists for caption export are SRT and TXT, with the mobile page adding "other formats not supported" — so a .vtt is something you produce after the fact, not something you select in the dialog. If the player or platform you are feeding wants WebVTT, the conversion is the last step, not a setting you missed:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That converter runs inside your browser tab — the subtitle file is read locally and handed back to you, never uploaded — and lives permanently at SRT to VTT. If you are not sure which format your player wants, subtitle formats compared lays out the differences.
Fix 4: version
The fourth root cause is the shortest one CapCut lists: "Software version limitations: Update to the latest version." There is no version number attached to it in the documentation, so treat it as the last thing to try rather than the first.
Where the exported file will — and will not — go back in
Plenty of people export an SRT in order to fix it and bring it back. CapCut's subtitle-import page sets two boundaries on that round trip, and both are worth knowing before you plan a workflow around it.
First, platform: "subtitle import functionality is only available on CapCut Desktop and CapCut Web. The Mobile App does not support direct subtitle file import as of 2026." The same page repeats it for emphasis — mobile "does NOT allow importing .srt or .txt subtitle files" — while noting that mobile "fully supports viewing and editing subtitles imported elsewhere," just not starting the import.
Second, format: on Web, CapCut states "TXT files are not supported on Web—only SRT." So the TXT fallback from the section above is genuinely a one-way street on Web: you can export TXT, but you cannot hand TXT back to the same editor. Convert it to SRT first.
On Desktop, CapCut also asks that you "ensure encoding is UTF-8 to support special characters (e.g., Chinese, Arabic, Cyrillic)" — the same encoding concern that shows up on the export side.
How to tell it worked
Open the exported file in a plain text editor rather than trusting the file size. A usable SRT has numbered blocks with timecodes; on its subtitle-import page, CapCut shows the structure it expects from a plain .txt on Desktop as 00:00:01,000 --> 00:00:04,000 followed by the line of text.
If the file opens empty, you are back at root cause one: the text on your timeline was never a recognized caption. If it opens with content but a player rejects it, CapCut's import page suggests validating subtitle files "using free tools like Aegisub or online SRT checkers" — the same check works on a file you just exported.
FAQ
Why is my exported CapCut SRT file empty? Because CapCut exports only captions produced by Auto Caption Recognition. Its help page states it directly: "only automatically recognized captions can be exported." Manually typed text layers are not captions, so the exporter has nothing to write.
Can I export subtitles I typed by hand in CapCut? CapCut's help center does not describe a way to do this — the documented limit is that only automatically recognized captions can be exported. It does not publish a conversion path for existing text layers, so check the official documentation for your version rather than assuming a hidden setting exists.
Can CapCut export captions as VTT? The formats CapCut lists for caption export are SRT and TXT, and its mobile instructions add "other formats not supported" to that pair. If you need VTT, export SRT and convert it afterwards.
Why does caption export keep failing on CapCut Web? Two documented reasons. The export path "must use ASCII characters only; avoid special symbols to prevent encoding errors," and CapCut's own fallback is to "first export as TXT format, then convert to SRT using external tools."
I exported the video but got no subtitle file. What did I miss? Caption Export is a separate selection. CapCut Desktop's instruction is to confirm that "Caption Export" is selected, not "Video Export"; on mobile it says to uncheck "Video Export" and select only "Caption Export."
All quoted text comes from CapCut's official help center, checked 16 September 2026. CapCut revises these pages regularly — verify against the current version before relying on them. More export troubleshooting in the fix archive, and the rest of the browser-based converters are in all Clapr tools.
