CapCut Captions Not Working? Fix Generation and 99% Stalls

Checked 30 August 2026.

If CapCut captions are not working, don't begin with a reinstall. Confirm the project is saved, play the exact track that contains speech, select the spoken language and run Auto Captions on one short, clean test clip. If the test works, the original audio or timeline is the likely problem. If it fails too, move outward to the app, account, connection or current service.

One exception comes first: if CapCut Web is already processing and shows 99%, keep that tab open. CapCut's current 99% guidance says a refresh or navigation can cancel remote processing. A percentage is a symptom, not a diagnosis.

First, find where the caption job failed

Match the symptom you can actually see:

• Auto Captions is missing: check the current Captions route, the official update and the account shown in the editor.
• Generate does nothing: play the selected speech track and try a short clean clip.
• “No speech recognized” or an empty result: isolate the voice and confirm the spoken language.
• Progress stops at 45%, 99% or another number: protect the active job, then check whether the failure follows this file or the whole platform.
• Captions appear and then disappear: save, reopen and compare the short test project.
• Captions exist but the words or timing are wrong: generation succeeded. Return to the CapCut Auto Captions workflow and repair the track.

Use this guide when no usable caption track exists. A wrong word, late line or SRT problem needs a different fix, not another recognition pass.

Run one short clean test before changing the app

The quickest useful test is not the full project again. Duplicate the project if your build offers that safely, or at least confirm it has saved. Add one short clip with clear speech and no music. Use the same account, platform and spoken language as the failing project.

1. Play the test clip from the timeline. You should hear the words from the track you intend to transcribe.
2. Open Captions → Auto Captions. Current CapCut help uses that route on Web, Desktop and Mobile, although labels can move between builds.
3. Select the spoken language explicitly instead of relying on a remembered previous setting.
4. Generate captions and leave the app or browser in the foreground while it works.
5. Check whether a real caption track appears and survives a save/reopen.

The result changes the rest of the diagnosis:

• The test works: CapCut can generate captions for this account and platform. Go back to the original project and inspect its audio, overlapping speech, language, length and timeline state.
• The test also fails: the problem is broader than one edit. Check the current app version, connection, account gate and another supported platform before touching local project data.

CapCut's official Auto Captions troubleshooting names poor audio, background noise, a wrong or unsupported language, an unstable connection, muted or missing audio and an outdated build as common causes. The short test separates those branches faster than trying every generic fix on a valuable project.

If Auto Captions is missing

Current English CapCut help shows Captions → Auto Captions on Web and Desktop and Captions in the Mobile bottom menu. The normal workflow is documented for all three platforms in CapCut's subtitle-recognition guide.

If the control is missing:

• Put media on the timeline and select the project before searching the home screen.
• Check Captions first; older builds and older tutorials may still point to Text.
• Update only through CapCut's official app store or installer route.
• Confirm the same account and region before comparing two devices.
• Check the live badge or counter. A missing free use is not the same problem as a missing tool.
• Try the signed-in Web editor if the Desktop or Mobile tile is absent, but protect source media before moving an important job into a browser workflow.

Do not install an old build or an unofficial APK just to recover a menu shown in an old video. If the whole editor is unstable rather than one caption control, use the broader CapCut not working guide.

If Generate does nothing

Pressing Generate cannot help if the selected source has no audible speech. Play the timeline with headphones before changing settings.

Check these in order:

1. The correct source is audible. A muted camera track, detached voiceover at zero volume or missing source file can leave Auto Captions with nothing to analyze. Use the CapCut no-sound guide if playback itself is silent.
2. The right speech track is selected. If music and voice are on separate tracks, select the voice where the current dialog offers a source choice, or mute the music for the recognition pass.
3. The spoken language matches. A wrong language can produce empty or unusable recognition. Mixed-language speech may need separate passes and human review.
4. The live gate allows the action. Free uses, plan prompts and rollouts can vary. CapCut's free-usage explanation says limits can change during testing, so check the current dialog instead of copying someone else's allowance.
5. The connection is stable. Current official help describes cloud processing as one reason generation can fail. Test another reliable network before assuming the project is corrupt.

If the button still does nothing in the clean test, save the project, close CapCut normally and reopen it. On Web, try a current Chrome or Edge session. Clearing site data comes later because it can sign you out and remove local browser state.

If CapCut says no speech was recognized

“No speech” does not always mean the clip is silent to a human. Speech recognition has to separate words from everything around them.

• Solo the voice or mute music and sound effects for the recognition pass.
• Raise a very quiet speech track only enough to make the words clear; avoid clipping it.
• Test a section without overlapping speakers.
• Choose the language manually, especially after duplicating a project or switching accounts.
• If one portion fails, split out a short clean section and test it rather than regenerating the entire edit.

Do not claim a universal accuracy score or blame an accent. Names, numbers, fast speech, code-switching and background sound all change the result. Once captions exist, correct the transcript before styling it.

If captions are stuck at 99% or 45%

CapCut's current official page treats 99% as a finalization, rendering or synchronization delay that can happen after speech analysis has progressed. The safe next step depends on the platform.

Web

Do not refresh or navigate away while the 99% job is still active. Keep the tab open and the connection stable. If the job clearly stops changing, save what the Web project has preserved and test a short clean clip in a current Chrome or Edge session. Only clear browser data after confirming the project and login state are recoverable.

Desktop

Keep the project open while CapCut is still working. Check whether the app and system still show activity. If a short clean clip completes but the original does not, simplify the recognition source: mute extra tracks, isolate speech and test the failing range. Back up the project and source media before reinstalling.

Mobile

Keep CapCut in the foreground and confirm a stable connection. Close other heavy apps if the device is under pressure, but do not delete CapCut data while local drafts are unprotected. If the clean test works, return to the original audio rather than resetting the whole app.

A stall at 45%, 99% or another number does not justify a separate fix page. Record the platform, current build, spoken language, clip, visible message and whether the clean test works. Those details are more useful than the percentage alone.

What the current CapCut Captions screen should confirm

Before generating, confirm three visible facts rather than trusting an old screenshot:

• the dialog is actually Auto captions, not Auto Lyrics or a template;
• the spoken language matches the audible track;
• any Pro, free-use, bilingual or other live badge is understood before the run.

The screenshot is a navigation reference, not proof that every account has the same allowance or optional controls.

If captions appear, then vanish or stay empty

First distinguish an empty generated track from captions that exist but are hidden.

• Save the project, close it normally and reopen it.
• Look for an existing caption track and make sure it is not hidden, disabled or covered by a duplicate pass.
• Move the playhead over a caption block. A block outside the current time will not appear in the preview.
• Compare with the short test project. If the test survives reopening, the original project state needs attention.
• Export a very short test only after the timeline track is visible. An export cannot restore captions that are absent from the edit.

If text exists but line breaks, words or timing are wrong, generation no longer counts as failed. Continue with the main Auto Captions guide instead of repeatedly generating new overlapping tracks.

Protect the project before resets

Restarting an app is reversible. Clearing browser data, deleting app data and reinstalling are not equally safe when local drafts or unsynced media are involved.

Before a risky reset:

• confirm the project is saved or synced in a way you can verify;
• keep the original source media outside CapCut;
• record the account and sign-in method;
• note the app version, platform, language and visible error;
• export or duplicate any working portion that would be difficult to rebuild.

The CapCut project safety guide covers backup and transfer decisions. Do not clear App Data or remove local folders as a casual caption fix.

When to stop troubleshooting

Stop repeating the same generation attempt when:

• the same clean test fails on more than one supported platform;
• the control shows an account or usage gate you cannot resolve locally;
• the service fails on multiple files and networks;
• the project is not safely backed up for the next reset;
• the failure began after an update and a current official route behaves differently.

At that point, preserve the evidence and contact CapCut support from its official troubleshooting page. Include the platform, build, account region, spoken language, short-test result and visible message. “It stops at 99%” is less useful than a reproducible test.