How to Add Hinglish Subtitles in CapCut

The auto-caption button will not do this well. Here is what does.

Blog · 10 August 2026 · 6 min read

Short answer

CapCut auto-captions read one language at a time, so a sentence like "bhai yeh editing software literally free hai" confuses them whichever language you pick.

Do this instead: finish your edit, export the video, make the captions somewhere that handles Hindi and English together, download the SRT, then in CapCut go to Text, Local Subtitle, Import File. Style one caption and use Apply to All.

If your CapCut version has no subtitle import, export the video with captions already burned in and edit around it.

CapCut has auto-captions built in, and for a video entirely in English they are decent. Point them at a sentence like "bhai yeh editing software literally free hai" and the result is usually unusable: half the Hindi is guessed at, English words are attached to the wrong ones, and the timing wanders.

This is not a CapCut flaw exactly. It is what happens when speech recognition tuned for one language meets a sentence that switches languages twice. The fix is to caption outside CapCut and bring the result in, which takes about two extra minutes and gives you captions that actually read.

Why the built-in captions struggle

Speech recognition narrows its guesses using a language model: having heard "bhai yeh editing", it predicts what tends to follow in that language. Code-switching breaks the prediction, because the next word comes from a different language entirely.

Single-language engines resolve this by forcing everything toward the language they were told to expect. Set it to Hindi and English words come out as odd phonetic Hindi. Set it to English and the Hindi turns to noise. Neither setting is right, because the sentence is genuinely both.

The workflow

Step 1: finish your edit first

Do your cuts, trims, and speed changes before captioning. If you caption first and trim afterwards, every timestamp after the trim is wrong. This one habit prevents most subtitle sync problems.

Step 2: export the edited video

Export from CapCut at your normal settings. This exported file is what you will caption, so its timing matches what you will eventually publish.

Step 3: generate the captions

Upload that file to a tool that handles code-switching in a single pass. DesiCaptions transcribes Hindi, English, and any mix together, and writes the result in Roman script so it reads the way your audience types. A five minute video takes around 60 to 90 seconds.

Step 4: fix names and brands

Check the transcript for proper nouns, brand names, and slang. These are what any AI gets wrong most often. Correcting them now takes seconds and saves editing text on a timeline later.

Step 5: export an SRT

Download the SRT rather than the burned-in video, since you are going to style the captions inside CapCut.

Step 6: import into CapCut

Step 7: style once, apply to all

Style a single caption clip the way you want it, then use CapCut Apply to All so the rest match. Doing this after import means the styling survives, because the text is already final.

If your CapCut version will not import SRT

Mobile CapCut has shipped several versions with no local subtitle import. Rather than fighting it, invert the order: have the caption tool burn the captions into the video, then bring that finished video into CapCut for any remaining edits like music, effects, or transitions.

You lose the ability to restyle captions inside CapCut, since they are pixels at that point. You gain captions that can never drift out of sync, which for short-form is usually the better trade.

Whichever route you take, keep the SRT file. It costs nothing to store and it is what lets you recut the same footage for a different platform later without transcribing again.

When the import fails

A few specific failures come up repeatedly, and each has a quick check.

If none of those apply, the fastest route past it is to skip the import: export a video with the captions already burned in and use CapCut only for music and effects.

Settings that work for vertical video

Once the text is in, these are reasonable starting numbers for a 1080 by 1920 Reel or Short.

SettingStarting pointWhy
Font size58 to 72 pxReadable on a phone held at arm length
WeightBold or heavierSurvives a bright or busy background
Outline3 to 5 px, darkKeeps text legible over any footage
Vertical position55 to 65% of frame heightBelow the face, above the interface
Words per caption3 to 5A full sentence gets skipped, not read
Lines2 maximumThree lines starts covering the video

Style one caption clip with these, then Apply to All. Doing it in that order means you set it once rather than forty times.

The vertical position matters more than people expect, because the bottom of the frame is covered by Instagram own interface. The exact margins are in the Reels safe area guide.

Getting the look right

A few things that matter more than the font choice:

Tools for this

Free to try, no credit card needed.

Caption your next video in minutes

Free plan, no credit card. Hindi and Hinglish captions in clean Roman script.

Start for free

Frequently asked questions

Can CapCut auto-captions handle Hinglish at all?

Poorly. They run one language model at a time, so a sentence that switches between Hindi and English mid-way confuses the engine regardless of which language you select. Captioning outside CapCut and importing an SRT is the reliable route.

Does CapCut mobile support importing SRT files?

It varies by version and region, and several releases have shipped without it. If yours does not have Local Subtitle under the Text menu, export a burned-in video from your caption tool instead and edit around it in CapCut.

Will the captions be in Devanagari or Roman script?

That depends on the tool. DesiCaptions always outputs Roman script, so captions read as "kya baat hai" and work with any font, including the display fonts that have no Devanagari coverage.

Do I need to re-caption after changing my edit?

If you cut or move anything before an existing caption, yes, its timing is now wrong. This is why captioning belongs at the end of the edit rather than the start.