In CapCut, captions burned into the picture and a separate .srt file are not two settings on one export — they are two different selections in the export panel. CapCut's own help center is explicit about this, and the line it uses is the cleanest official evidence that the two paths exist side by side.
That distinction decides more than file naming. One of the two paths has a hard prerequisite that most people only discover after the export comes back empty.
The official line that separates the two paths
CapCut's help article on captions failing to export lists "Incorrect export settings" as a root cause, and under the CapCut Desktop section it tells you to check exactly this:
Confirm "Caption Export" is selected, not "Video Export"
Must choose SRT or TXT format
The mobile instruction is the same idea stated as an action:
Uncheck "Video Export," select only "Caption Export"
Must choose SRT or TXT format (other formats not supported)
Read what that implies. The subtitle file is not a by-product of exporting your video — it comes from its own selection, and leaving "Video Export" ticked is listed by CapCut as a reason the caption file does not appear. If you exported your project, got an MP4, and then went looking for the .srt next to it, this is why there isn't one.
CapCut's help center does not describe what the video export does with your captions beyond this, so treat "the video path renders what is on the timeline" as the ordinary meaning and not as a documented spec. What it does document, in detail, is the constraint on the caption-file path.
The prerequisite that closes the SRT path
This is the highest-value sentence on that whole help page. CapCut lists as a root cause of caption export failure:
Text not generated through "Auto Caption Recognition" (only automatically recognized captions can be exported)
Only automatically recognised captions can be exported as a file. If you typed your captions in by hand as text layers — which is what most people do when they are styling captions for a specific look — there is nothing for CapCut to write into an .srt. The text exists as graphics on the timeline, not as timed caption data.
That single rule sorts the decision for you:
- You ran Auto Caption Recognition. Both paths are open. You can export the caption file, and you can also export the video.
- You typed the text yourself. The file path is closed. Your captions only exist inside the picture, and if you need a sidecar subtitle file you will have to produce it some other way.
CapCut also lists two more root causes on the same page — "File encoding or path issues" and "Software version limitations: Update to the latest version" — so a failed caption export is not automatically the auto-caption rule. But it is the one that no amount of retrying will fix.
Which path to choose
Pick the caption file when the destination can load subtitles itself and you want them switchable, searchable, or editable later. Pick captions inside the picture when the destination is a player or feed you do not control, because a sidecar file that nobody loads is the same as no captions at all.
One CapCut-specific wrinkle is worth knowing before you hand an .srt to a collaborator. CapCut's subtitle import page states:
However, 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.
And more bluntly:
As of 2026, CapCut Mobile does NOT allow importing .srt or .txt subtitle files. You cannot directly load external multilingual subtitles.
So if your editing partner works on the phone, the caption file you send them is not something they can pull into a project — although CapCut adds that mobile "fully supports viewing and editing subtitles imported elsewhere—just not initiating the import itself."
There is one more argument for keeping a caption file around: language coverage. CapCut states that its auto-captioning supports roughly 30-plus languages, while imported SRT files "bypass this limit entirely—you can use any language, including constructed ones (e.g., Klingon) or minority scripts."
If you need the captions inside the picture
If you already have a subtitle file and what you actually need is a video with the text rendered into the frames, you do not have to rebuild the project in CapCut to get there.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs in your browser tab: your video and your .srt are read from disk, the subtitles are drawn into the frames locally, and you get the file back. Nothing is uploaded, which matters for client footage and anything unreleased. It is also the practical answer to the auto-caption rule above — hand-typed CapCut captions can't come out as a file, but a subtitle file you wrote elsewhere can go into the picture here.
For the reverse situation — a subtitle file in the wrong format for its destination — SRT to VTT converts between the two text formats, and all Clapr tools lists the rest.
What breaks the caption file export
CapCut's guidance here is specific, and the fixes are unglamorous.
Encoding. For Desktop, CapCut says to "Convert SRT files to UTF-8 without BOM format (using Notepad++)". Anything with accented characters, Chinese, Arabic or Cyrillic is where this bites. On the import side CapCut gives the same advice in advance: "Ensure encoding is UTF-8 to support special characters (e.g., Chinese, Arabic, Cyrillic)."
Paths. Desktop guidance is to "Use English paths like C:\CapCut\subtitles.srt". For CapCut Online it is stricter and stated as a rule: "Export path must use ASCII characters only; avoid special symbols to prevent encoding errors". A folder named after a client in a non-Latin script is enough to trip this.
Format fallback. If the SRT export itself misbehaves on the web version, CapCut's own suggestion is to go around it: "If export issues occur, first export as TXT format, then convert to SRT using external tools". A related requirement sits on the import side rather than the export side: CapCut's subtitle import page states that a plain .txt "must follow basic SRT-like structure (e.g., 00:00:01,000 --> 00:00:04,000 Hello) to work on Desktop". That is a condition for loading a .txt back into CapCut Desktop, not a rule CapCut states about the export itself.
Version. The fourth root cause on that page is simply "Software version limitations: Update to the latest version".
The formats CapCut lists: SRT and TXT (no VTT)
The format options CapCut names for caption export are SRT and TXT, with the mobile page adding "(other formats not supported)". There is no VTT option listed anywhere in the official caption export instructions.
Be precise about what that means: CapCut's help center lists SRT and TXT as the choices, rather than publishing a statement that VTT is unsupported. Either way, if your destination wants WebVTT, plan on converting after the export rather than looking for a setting. The differences between the two formats are small but not zero — see SRT vs VTT captions and the broader subtitle formats compared for what actually changes.
FAQ
Can I export captions and video separately in CapCut? Yes, and CapCut treats them as separate selections. Its help page tells desktop users to "Confirm "Caption Export" is selected, not "Video Export"", and tells mobile users to "Uncheck "Video Export," select only "Caption Export"".
Why is my CapCut SRT export empty? The most likely reason is the auto-caption rule. CapCut states that only captions generated through "Auto Caption Recognition" can be exported; text you typed as layers has no timed data behind it. Encoding, export path and an outdated app version are the other three causes CapCut lists.
Does CapCut export VTT subtitles? The formats CapCut names for caption export are SRT and TXT, and its mobile instructions add "(other formats not supported)". Export SRT and convert it afterwards if you need WebVTT.
Can I import an SRT back into CapCut? On CapCut Desktop and CapCut Web, yes. CapCut states that subtitle import "is only available on CapCut Desktop and CapCut Web" and that the mobile app does not support direct subtitle file import as of 2026.
Are burned-in captions reversible? No. Once text is drawn into the frames it is part of the picture, which is exactly why the choice matters at export time rather than afterwards. Keep the caption file if you have one, even when you ship a version with the text burned in.
Quotes from CapCut's official help center, checked 16 September 2026 — see Why Do the Captions Fail to Export? and How Do I Import Subtitles?. More CapCut export behaviour is covered in CapCut export settings explained, and the rest of these walkthroughs live in the guides hub.
