CapCut Bilingual Subtitles: Two Languages on Screen

Checked 13 September 2026.

Two visible languages, not two selectable tracks

A bilingual layout keeps the original words and their translation on screen at the same time. That is different from supplying two subtitle files so a viewer can choose one language in a player. Decide which result you need before editing.

This guide covers the paired on-screen layout. If you want translated speech or just one translated subtitle track, use the CapCut Video Translator guide. Changing the app’s menu language does not translate the video.

Finish the rough cut first, keep an untouched editable copy and retain the source media. Test with a short clip containing a name, a number and normal speech; a separate 20–30-second project is a useful sample, not a CapCut limit. Check permission before uploading client recordings or transcripts to a cloud caption or translation tool. A Desktop app is not a guarantee of offline processing.

Create bilingual subtitles on Desktop

CapCut’s bilingual subtitle instructions document a source language and one translation target. The Desktop panel below shows the relevant controls:

1. Open your short test project or an editable working copy, then choose Captions → Auto captions.
2. Set Spoken language to the language of the speech. If an audio-source selector is available, choose the source containing that speech.
3. Open Bilingual captions and select the target language.
4. Leave Delete current captions unchecked when existing captions must remain. Turn off optional processing you do not need, read any access prompt and select Generate in the copy.
5. Play the result and check that both languages are visible. Correct the source transcript, then revise each translation against the corrected meaning. Check the timing of the complete pair.

The pictured panel has Pro badges and optional filler-word identification. Read the prompt for the options selected in your account; the image does not establish a universal price or free allowance. An unchecked deletion box also does not replace a backup.

If you still need to generate and correct the first language, the Auto Captions guide covers that stage. Do not keep generating over a transcript you have already reviewed.

Translate captions on Web, then check what remains visible

CapCut has an editor and separate browser tools, so their menus are not interchangeable. Its translated-subtitles walkthrough shows a standalone AI captions tool: generate the source captions, open Subtitles, then use the translation shortcut. This is not proof that the same button exists in every open Web editor project.

1. Open the AI captions tool from CapCut’s available tools and upload a short clip you are allowed to share.
2. Generate the source captions and correct their wording before translation.
3. Open Subtitles and the translate control in the shortcuts area. Set From and To to the intended languages.
4. Read the warning, then choose Translation. In the illustrated interface, translating removes previously applied word highlights; finish the translation before rebuilding that styling.
5. Inspect the result. If only the target language remains visible, it is not yet a bilingual layout. Keep your approved source text and use the paired-file method below on Desktop or the Web editor.

If you are already editing a project in CapCut Web, open its Captions panel and check the controls offered there. Use an available translation action on reviewed captions rather than starting another recognition pass. If that action is missing, a reviewed SRT is the more direct route.

Use Mobile translation, or time a short pair manually

CapCut documents Captions → Auto Captions, a spoken-language choice and Translate to on Mobile. If your generation sheet offers the target selector, choose the pair and test it in a separate short project. Correct both languages afterward. The target selector is not visible in every supporting help image, so do not assume it is hidden under a particular submenu when your app does not show it.

For a short clip, manually timed text avoids depending on a missing translation control. CapCut’s subtitle import help documents Text → Add text as a Mobile alternative; it does not document direct SRT import in the Mobile app.

1. Work in a copy and move to the beginning of the first spoken phrase.
2. Choose Text → Add text. Enter the approved source phrase, insert a line break, then type its translation.
3. Adjust the text clip’s start and end on the timeline so the pair appears with that phrase. Play it with the audio and correct the boundaries.
4. Position the pair where both rows are readable. If you need a different font or position for each language, use two text clips with matching start and end times instead.
5. Repeat for the next phrase, then watch a short export before timing the rest. Keep your approved text outside the project too.

This is practical for a few captions, but slow for a long interview. For longer work, use Desktop or Web with the paired file below. Do not assume a locally saved phone project has transferred to another device; verify an editable copy and its media before continuing there.

Put both languages in one SRT file

An SRT cue can hold multiple text lines under one start and end time. Put the source phrase on the first line and its translation on the next. The Library of Congress description of SRT explains the numbered cues, timestamps and blank-line separators.

Here is a small English–Spanish example. Replace the words and times with those for your video:

1
00:00:01,000 --> 00:00:04,000
We meet at six.
Nos vemos a las seis.

2
00:00:04,500 --> 00:00:07,500
Bring your camera.
Trae tu cámara.

Keep the comma before milliseconds, both hyphens in -->, and a blank line between cues. Do not insert a blank line between the two languages inside a cue. If you are combining two existing files, match phrases by meaning and timing—not cue number alone. Different sentence splits can make “cue 12” refer to different speech.

Save it as plain text, not a word-processing document

• Windows: paste the cues into Notepad and use File → Save as. Select UTF-8 encoding and All files as the file type, then name the file bilingual.srt.
• Mac: in TextEdit, choose Format → Make Plain Text before pasting. Save as bilingual.srt with UTF-8 plain-text encoding. If TextEdit adds .txt, change the extension to .srt; do not merely rename an RTF document. Apple’s TextEdit settings guide explains the plain-text encoding and automatic .txt options.

Check the complete filename and reopen the saved file in the text editor. It must contain ordinary readable cues, preserve accents such as cámara, and end in .srt, not .srt.txt. Check that smart punctuation has not replaced the two hyphens in the timestamp arrow with a long dash. Save confidential text only in an approved location.

Import the pair into Desktop or Web

1. Open a separate short test project with the matching video. This keeps an earlier caption layer from covering the imported pair.
2. On Desktop, use Captions → Add captions → Import file. In the Web editor, open Captions → Upload caption file. Select your SRT.
3. Play every imported cue. Check both language lines, special characters and start/end times. Both lines share a cue; do not count on independent styling for each row.
4. Style the captions and export a short video. Confirm that neither line is missing or clipped before importing the full file into your working copy.

If the file is rejected or its timing is wrong, the subtitle import guide covers format and import checks. Keep the original SRT: imported captions and manual text may not qualify for CapCut’s native caption-file export later.

Check the meaning before polishing the style

Read the source while listening to the speech, then compare its translation. Names, dates, numbers and negatives deserve a deliberate second look. A fluent sentence is still wrong if “do not share” becomes “share.” Keep a short terminology list for names and specialist terms.

If you translate in a separate step, correct the source first. If the bilingual generator has already produced both languages, fix the source and then update the target yourself. Do not assume later edits stay linked across languages.

Mixed-language speech needs its own check. Choosing English as the source and Spanish as the target does not prove that recognition captured a Spanish phrase spoken halfway through an English sentence. Listen to those switches and supply any missing words and timing. Have a competent bilingual reviewer check important translations; specialist material also needs subject knowledge.

Keep both rows readable, then check the export

Start with a consistent order—source above translation, for example—and keep both rows large enough to read at phone size. When a translation runs long, split the thought or rephrase it without losing meaning. Shrinking the second language until it fits is not a useful solution.

• Use strong contrast and natural phrase breaks. Do not rely on colour alone to identify each language.
• Keep the pair clear of faces, labels and the destination app’s buttons. Check the full video in a private posting preview only when uploading is authorized.
• Inspect the actual scripts: missing-character boxes, detached Arabic letters, reversed punctuation or awkward Chinese breaks need a font and layout check.
• Review timing with speech, not word-for-word translation order. If captions drift, use the caption timing guide before redesigning them.

If captions serve accessibility, retain speaker identification and meaningful sound cues. W3C’s caption guidance distinguishes those needs from translating dialogue alone. Two languages on screen do not make an inaccurate transcript accessible.

When both rows move together

Check whether both layers are selected and whether an Apply to all option is active. Try one small position change in a copy with broad selection or automatic application off, where offered. Inspect neighboring captions too. An older discussion about simultaneous captions describes this trap; it is not a guarantee that every current build has the same fix. A paired SRT intentionally keeps both lines in one cue. Use separately timed text clips when you need independent placement.

Deliver the right files

For two rows that must always look the same, export a video with both burned into the picture. Viewers cannot switch those rows off. Watch the exported file, not only the editor preview, and check the entire video for cropping, unreadable text and missing translations.

For selectable languages, retain separate reviewed subtitle files. A single bilingual SRT is still one track containing two text lines. YouTube’s supported subtitle formats specify plain UTF-8 for SRT and do not support its style markup; do not expect CapCut fonts, colours, animation or positions to carry over.

CapCut’s caption export help limits native subtitle-file export to eligible recognized captions. Check the actual export options and the complete contents of each resulting file rather than promising two separate SRT downloads. The SRT export guide covers those checks. Edits inside CapCut do not update an older external SRT; keep your delivered files in sync with the final video.

If the bilingual control is missing or generation fails

First separate a recognition failure from a translation problem. If there are no usable source captions, follow caption-generation troubleshooting. If the source is correct but the translation is wrong, fix the target rather than recognizing the whole project again.

Check the intended account, selected language pair and exact availability or upgrade message. Test a short separate project. Preserve the editable master and media before updating through an official store; an update does not guarantee access. Do not clear app storage or delete drafts to find a missing control.

If the option remains absent, use the paired-file or manual-text method above. For an unresolved error, send CapCut the app version, platform, language pair and exact message through its support route; on Mobile, the documented route is Settings → Feedback → Give feedback. Remove account details, private filenames and project thumbnails from any evidence you share.

Bilingual subtitle questions