How to Add Bilingual Subtitles in CapCut on Mac Using an SRT File

Decide whether you need an external file

If your project is already in CapCut, first check its caption tools. Its automatic caption help describes a Desktop workflow, and its caption feature page includes bilingual captions. Availability can depend on the installed version, region, and feature.

Use an SRT when the subtitle text is being prepared separately, when a reviewer has already corrected it, or when you need a file you can keep with the project. An SRT is a portable text-and-timing document. It does not preserve an entire editing project's fonts, animations, or separate language controls.

This guide covers CapCut Desktop on Mac. Do not assume that the same instructions apply to CapCut Web, the mobile app, or Jianying; their interfaces and available features need separate checks.

Match the subtitles to the timeline you will actually deliver

Before generating subtitles, decide which edit supplies their timing.

If the video is almost finished, export a local reference copy of that cut and transcribe that copy. Keep the same sequence of shots, opening silence, introductions, and speech pauses in the project. A subtitle generated for the final sequence is easier to align than one generated from a collection of unedited clips.

If you transcribe an individual source clip instead, its SRT times start from that clip's beginning. They do not automatically know where the clip sits in a longer CapCut timeline. Trimming the opening, rearranging sections, or inserting a new introduction can invalidate those times.

Choose a short section first if you are uncertain. Carry it through import and a sample export before preparing a long video. Keep a copy of the original SRT so that timeline corrections do not become your only record of the subtitles.

Generate and review the bilingual SRT

For a video you are allowed to process, open Alison Workspace's Transcribe Files… window and add the local reference video. Select its spoken language and an available translation target, then prepare the requested resources and start transcription.

Review the source and translation before exporting. Correct names, numbers, and technical terms, and check that the record reaches the end of the intended video. Inspect any passages without a translation. An accepted file or a completed opening section is not proof that the full result is ready.

From the record's Export menu, choose Export content → Bilingual, then SRT Subtitle File. Save the file with a name that identifies the video and edit version.

Bilingual export places the source and available translation in the same timed cue. It does not create two independently selectable language tracks. If you need separate language deliverables, export and check the language files separately instead of expecting a combined cue to become two tracks automatically.

The SRT generation guide covers file preparation and export in more detail.

Check what is inside the file

An SRT contains numbered cues, start and end times, and text. For example, this invented English–Spanish cue illustrates the format:

1
00:00:02,000 --> 00:00:05,000
Open the project settings.
Abre la configuración del proyecto.

The line break separates the two languages within one cue. It does not assign an independent font or animation to either line. Plan to check and adjust the presentation in the editor.

Use the actual .srt export, saved as UTF-8 text. A filename ending in .srt.txt, a renamed PDF, or a WebVTT file with its extension changed is not the same thing. If you inspect a copy in a text editor, preserve the cue structure and timecodes.

For a bilingual video, check more than whether both languages exist. A long source sentence plus a long translation may occupy several wrapped lines. Shortening the translation for readability requires a meaning-preserving edit, not deleting a condition or number to make the text fit.

Import the file into CapCut Desktop

CapCut's subtitle import help documents Captions → Add Captions for Desktop, followed by selecting a local subtitle file. It describes the imported cues as editable text blocks on the timeline.

Open your Mac project, use that documented import route, and select the prepared SRT. Then inspect the first imported caption and its position relative to the spoken audio. Menu labels can differ between releases; if the import control is missing, check the Desktop instructions for your installed version rather than following a mobile tutorial.

Confirm the timeline relationship before making widespread edits. The subtitle's first cue may begin several seconds into its source video. Align the source timeline, not merely the first visible word with the start of the project. If there is a consistent offset, determine whether the SRT came from a different cut or was placed at the wrong position.

If both an automatic caption layer and imported captions are visible, identify which one you intend to keep. Edit a project copy while resolving duplicates so you can compare the results.

Make both languages readable in the frame

Play the imported subtitles over the actual footage, including busy slides and bright backgrounds. Check the font's character coverage, contrast, size, line wrapping, and position. Inspect each script you will deliver; a readable Latin font does not establish that every Chinese or Arabic character will display correctly.

Use the same language order consistently. Leave room for faces, software controls, product labels, and other essential visual information. For a vertical version, check a vertical preview instead of assuming that a layout made for a widescreen tutorial will fit.

When a cue is too long, first check whether it contains too much speech for its display time. Increase readability through appropriate cue editing and layout rather than shrinking every subtitle until it is difficult to read. Check any combined bilingual cue after a timing or text change so that the source and translation still refer to the same passage.

Check timing at the beginning, middle, and end

A constant offset and growing drift need different attention.

If every cue is late by roughly the same amount, compare the video's start, any added introduction, and the subtitle placement. If alignment is good at the start but wrong later, inspect cuts, speed changes, and differences between the reference export and current project. A single global move cannot repair a sequence whose edit has changed in several places.

Review passages around every major cut you made after transcription. Also check the final spoken sentence: subtitles ending early may indicate an incomplete source record rather than a CapCut display problem.

After timing edits, export a short sample video and open it in a player outside the editor. Confirm that both languages appear, special characters render correctly, and the text remains on screen long enough to read. Once that sample is sound, export and review the full deliverable.

Keep local transcription and video delivery separate

Alison's supported recognition and translation run locally after the required resources are installed. That statement describes subtitle preparation. It does not establish that every CapCut feature, project-sync option, or publishing destination operates offline.

Keep the reviewed SRT, the reference video used to produce it, and the final project together. If the edit changes substantially, update the subtitles to match instead of treating the earlier file as finished.

The result to judge is the exported video: reviewed wording, synchronized speech, and a readable bilingual layout. A successful import alone establishes none of those three.

CapCut's import instructions, automatic caption instructions, and bilingual caption description were checked on October 24, 2026. The import route above follows those documents; no end-to-end test of a particular CapCut release is claimed.