An absent SRT import control is a capability and workflow question before it is an encoding problem. Identify the exact editor and platform, then check whether that environment accepts subtitle files. A desktop tutorial does not establish that the mobile application has the same route. Keep the reviewed SRT while you find a supported way to use it.
Establish which environment the instructions describe
CapCut’s subtitle import help distinguishes supported workflows by platform. The page describes CapCut, including its international products; it is not evidence that Jianying in mainland China offers identical menus. Record the product name, operating system, application version and whether you are using a browser or an installed app. Read the current import controls for that combination.
Checked on October 14, 2026, that official page says CapCut Mobile has no direct SRT or TXT import. It describes SRT-only input on Web through Captions → Upload caption file, and SRT or timed TXT on Desktop through Captions → Add Captions → Import file. These are the documented routes at the check date; verify the current interface when using them.
Separate importing a timed subtitle document from adding a text box. An editable text box can reproduce a sentence visually without preserving the document’s cue numbers, timings or language track. Similarly, a video that already contains burned-in wording does not supply an editable SRT merely because the words are visible.
Make a three-cue test before moving the whole project
Create a copy of the project and a short test document. Use three approved sentences in the target language at 0–2, 3–5 and 6–8 seconds. Leave a gap between cues so an overlap is easy to detect. Open the SRT in a text editor to confirm that it is a timed document, not an image or a renamed word-processing file.
You can use this three-cue English test input to exercise the import route. It is an original test file, not an exported CapCut project or proof that a test has passed.
- Look for a subtitle-file import action in the current editor. Check the supported extensions shown there.
- If the action exists, import the small test and inspect each cue as an editable object.
- Change one word in the second cue and move its start slightly. Confirm that the change reaches the rendered test.
- If the action does not exist, keep the SRT and use a documented supported environment, or plan a reviewed manual text workflow.
- Record the chosen route before importing the full transcript. Do not spend time converting encodings to solve a missing feature.
Moving to another environment can involve a separate account, project transfer or export. Verify those requirements before relying on that route for a deadline. Importing a flattened video into a new project will not recreate all the original layers.
Verify the data as well as the picture
This is a proposed test, not a reported product benchmark. Acceptance means all three sentences have independent time ranges and their wording matches the test input, the intended objects remain editable, and the downloaded test plays with the expected wording. If the workflow produces only visual text, label that limitation in the handoff rather than promising a reusable subtitle track.
Keep the approved SRT, the environment record and the test export together. Artwork prepared through Imagild Skills can join the external editing project, but subtitle import and rendering depend on that editor. Once the supported route works, investigate character encoding only if readable input becomes garbled; that is a different failure from an unavailable import control.