As of 2026, CapCut Mobile does not allow importing .srt or .txt subtitle files. CapCut's help center states it directly: "As of 2026, CapCut Mobile does NOT allow importing .srt or .txt subtitle files. You cannot directly load external multilingual subtitles."
That is the part most articles stop at. The more useful half of the same page is this: "Even though mobile lacks import, it fully supports viewing and editing subtitles imported elsewhere—just not initiating the import itself."
So the job is not "make the phone accept an SRT." The job is to move the import step onto a platform that supports it, and keep everything else on your phone. This guide walks that route, including the one file-type restriction that catches people out on CapCut Web.
Before you start
You need three things:
- A subtitle file that CapCut will accept. CapCut's help center describes external subtitle import as "primarily in SRT (.srt) or TXT (.txt) format." The accepted set is narrower on Web — see the table below.
- UTF-8 encoding. The Desktop instructions say: "Ensure encoding is UTF-8 to support special characters (e.g., Chinese, Arabic, Cyrillic)."
- Access to CapCut Desktop or CapCut Web for the import step itself, because the mobile app does not perform it.
Here is the official statement that governs all of this, quoted in full because the qualifiers matter: "CapCut supports importing external subtitle files—primarily in SRT (.srt) or TXT (.txt) format—so you can use subtitles in any language, including those not covered by its built-in auto-captioning system. 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."
Step 1: Pick the platform that will do the import
The three CapCut surfaces do not accept the same things, and the difference is not cosmetic.
| Platform | Subtitle file import | File types CapCut names |
|---|---|---|
| CapCut Mobile App | Not supported as of 2026 | — |
| CapCut Web | Supported | SRT only — "TXT files are not supported on Web—only SRT." |
| CapCut Desktop | Supported | ".srt format (recommended) or plain .txt with timecodes" |
If your only file is a .txt, Web is out. Either convert it to a proper SRT or do the import on Desktop, where plain text is allowed — but only in a specific shape, covered in Step 4.
Step 2: Make sure the file is actually an SRT
This is where the browser tool below earns its place. If what you have is a .vtt file — the format most web players and a lot of transcription services hand you — CapCut's help center does not name it anywhere in its subtitle instructions. The formats it names for subtitle import are SRT and TXT, and for caption export it says "Must choose SRT or TXT format (other formats not supported)."
Converting VTT to SRT is a text transformation, not a re-encode, so there is no reason to upload the file anywhere:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs inside your browser tab — the subtitle file is read from disk, rewritten locally, and handed back. Nothing is uploaded, which matters when the file is a transcript of something private. If you need the trip in the other direction later, SRT to VTT is the same tool reversed. For how the two formats actually differ, see SRT vs VTT captions.
Step 3: Import on CapCut Web
On Web, the step CapCut documents is blunt: "Choose a .srt file from your device."
Two conditions from the same page are worth knowing before you blame the file:
- Connection matters during import. "CapCut Web requires a stable internet connection during import."
- Big files take a moment. "Large SRT files (>1000 lines) may take a few seconds to process." A few seconds of nothing happening is documented behaviour, not a failed import.
Step 4: Or import on CapCut Desktop
Desktop is the more permissive of the two. CapCut's first instruction is: "Save your subtitles in .srt format (recommended) or plain .txt with timecodes."
Note with timecodes. A plain text file of dialogue lines will not do. The help center is explicit about the required shape: plain .txt "must follow basic SRT-like structure" to work on Desktop, and the example it gives is a timecode line such as 00:00:01,000 --> 00:00:04,000 with the subtitle text on the line beneath it.
If the import fails outright, CapCut points at formatting first: "If your SRT uses non-standard formatting (e.g., missing timecodes), import may fail. Validate your file using free tools like Aegisub or online SRT checkers."
Step 5: Finish the job on your phone
Once the subtitles are in the project, the mobile app stops being the blocker. Per CapCut, mobile "fully supports viewing and editing subtitles imported elsewhere—just not initiating the import itself."
That means timing tweaks, wording fixes, and styling are all available on the phone. What is not available is the act of loading the file. For how projects move between CapCut Desktop, Web, and the mobile app on your account, check the official documentation — the help center pages covering subtitle import do not describe that mechanism.
One upside of going the import route at all, in CapCut's own words: "CapCut's auto-captioning supports ～30+ languages (e.g., English, Spanish, Japanese, Arabic), but imported SRT files bypass this limit entirely—you can use any language, including constructed ones (e.g., Klingon) or minority scripts." The approximation in that number is CapCut's, not ours.
Common mistakes
- Dropping a
.txtonto CapCut Web. Desktop takes it; Web does not. CapCut's Web step says "TXT files are not supported on Web—only SRT." - Assuming export ability implies import ability. The mobile app does have documented caption export steps — CapCut tells mobile users to "Uncheck "Video Export," select only "Caption Export"" and that you "Must choose SRT or TXT format (other formats not supported)." None of that grants import.
- Leaving the file in a non-UTF-8 encoding. If your subtitles contain Chinese, Arabic, or Cyrillic characters, CapCut's Desktop instruction to ensure UTF-8 is the fix to try before anything else.
- Sending a text file with no timecodes. On Desktop, plain
.txtstill has to follow SRT-like structure. Without timecodes, CapCut lists import failure as a likely outcome. - Expecting hand-typed text layers to come back out as an SRT. CapCut's caption-export troubleshooting names this as a root cause: "only automatically recognized captions can be exported."
FAQ
Can I import an SRT file into CapCut on my phone? No. CapCut's help center states that as of 2026 the mobile app "does NOT allow importing .srt or .txt subtitle files," and that subtitle import "is only available on CapCut Desktop and CapCut Web." Do the import on one of those two, then edit on mobile.
Why did CapCut Web reject my .txt subtitle file? Because Web accepts only SRT. CapCut's Web instructions say plainly: "TXT files are not supported on Web—only SRT." Desktop is the platform that accepts plain text, and only when it carries timecodes.
Can CapCut Mobile export subtitles even though it cannot import them? CapCut documents caption export steps for mobile — uncheck video export, select caption export, and choose SRT or TXT. Import and export are separate capabilities here, and the help center only rules out the import side.
Can I import a VTT file into CapCut? CapCut's subtitle import pages name SRT and TXT, and its caption export guidance says other formats are not supported. Convert VTT to SRT first — the VTT to SRT converter above does it in your browser.
My SRT imported but nothing appears. What now? Start with formatting. CapCut's own note points at "non-standard formatting (e.g., missing timecodes)" as a cause of failed import and suggests validating the file with "free tools like Aegisub or online SRT checkers." Check the encoding is UTF-8 while you are there.
Getting captions in and out of an editor is mostly a file-format problem, not an editing problem. Browse all Clapr tools for the conversions that clear it, or read more how-to guides.
Quotes above are from CapCut's official help center article "How Do I Import Subtitles?" (www.capcut.com/help/how-to-import-subtitles) and "Why Do the Captions Fail to Export?", checked 16 September 2026. CapCut has changed platform behaviour before — verify against the official pages before relying on them.
