How to Import SRT Captions in CapCut and Check Timing

Prepare a UTF-8 file for CapCut SRT captions, import timed blocks, inspect representative timing, and record corrections before continuing with project edits.

SRT Captions cover with a paper file and caption handoff cards
CapCut
CapCut
Sep 10, 2026

Use SRT as a timing handoff for an image to video ai project. Prepare a UTF-8 file with sequential blocks, valid start and end timecodes, and caption text. On CapCut Web, the documented route imports an .srt file; Desktop documents .srt and .txt handling through a separate menu. After import, check the first, middle, and last blocks before correcting either the source file or one project block. Keep the original file so you can compare any timing changes.

This guide covers subtitle-file preparation, import routing, and representative timing checks. Use the auto-caption correction workflow for captions created from spoken audio.

Prepare a valid SRT file

Each block should contain a number, a start and end timecode, one or more lines of text, and a blank line before the next block. Keep timecodes in order and make each end later than its start. Use UTF-8 so names and punctuation are not damaged. Remove hidden formatting and check that the file extension is .srt.

Before opening CapCut, use this short source-file check:

  • Confirm the numbering is sequential.
  • Confirm each timecode uses HH:MM:SS,mmm and the end is later than the start.
  • Check the first, middle, and last block for text, line breaks, and special characters.
  • Save a separate copy of the original file before making any repair.

A minimal block looks like this:

1 00:00:01,000 --> 00:00:03,500 First spoken line.

Add a blank line before the next numbered block. Check the first, middle, and last block in the source file before importing; a valid-looking extension cannot correct an invalid timecode or wrong encoding.

A physical SRT source-file check with timing marks and representative review cards

CapCut's subtitle import help documents the surface-specific routes. Do not infer that a TXT file imports on Web or that the menus have identical names. The same caution applies when an ai video generator workflow moves from creation into caption handoff.

Import and inspect the first blocks

For an image to video ai project, use the Web or Desktop route described in the Help workflow:

    1
  1. Web: Open the existing project, choose Captions on the left toolbar, and select the prepared .srt file. Do not substitute .txt on Web based on the Desktop instructions.
  2. 2
  3. Desktop: Open the existing project, choose Captions > Add Captions, and select the .srt or .txt file supported by that surface.
  4. 3
  5. Both surfaces: Inspect the first, middle, and last blocks for text, timing, line breaks, and character encoding. If the blocks share an offset, compare the original timecodes with the parsed blocks before editing the whole project.

If the import option or listed file type is not visible, do not switch formats by guesswork. Keep the original SRT, record the visible message, and use the Help route before changing formats.

Correct the source or the project

Use the scope of the mismatch to choose where to repair it:

What you see
Where to correct it
Check before continuing
Several blocks share the same offset or encoding problem
The source SRT
Compare the repaired file with the original, then use the documented import route again.
One block has the wrong wording or time range
That caption block in the project
Recheck the neighboring blocks so the local fix did not hide a wider offset.
The control or file type is missing
Stop and verify the surface
Do not rename the extension or assume the other surface uses the same menu.

Keep a note of which version is the source of truth so a later project edit does not overwrite a corrected timeline. This gives an image to video ai project a clear caption handoff before the next edit.

Keep a three-point timing log

Record the first, middle, and last imported blocks before correcting the whole file. A compact log makes a local error easier to separate from a file-wide offset:

Checkpoint
What to record
Decision
First block
Caption text, start time, end time, and the first spoken word
Keep if the caption begins with the intended scene
Middle block
Whether the text follows the spoken line and remains within the scene
Repair the source or block that shows the mismatch
Last block
Whether the caption clears before the final action or cut
Check the end time before changing the full file

For example, if the first block is correct but the middle and last blocks are shifted by the same amount, inspect the source timecodes before editing each caption. If only the middle wording is wrong, fix that block and recheck its neighbors. This log is the smallest useful check before you decide between a source-file repair and a project-level edit.

Keep the imported captions ready for the next edit

After correcting the imported blocks, keep the original SRT beside the project notes and record which blocks changed. If you later need a subtitle-file export, check that option separately because import and export may use different menus or file types. CapCut's AI caption generator is a separate caption workflow for creating captions from audio. For delivery settings after caption review, continue with CapCut AI video export settings.

The CapCut AI video generator page is the related creation starting point. Validate three representative blocks before relying on the whole file.

For caption correction inside the project, use fix wrong auto captions, then return to the AI video workflow map for the next editing or delivery route.

Hot and trending