A CapCut progress bar stuck at 99% does not prove the audio was recognized successfully. Check whether the app responds, whether captions have appeared and whether the job is still active before deciding how to retry.
Quick answer and symptom table
Keep the project open while checking the observable state. CapCut’s troubleshooting guide describes delays and separate platform checks; its explanations do not diagnose your specific job.
| Observed state | Check before retrying |
|---|---|
| Brief pause at 99%, app still responsive | Allow processing time and inspect whether output appears. There is no universal completion time. |
| Indicator unchanged, app responds | Record how long it has been unchanged, connection state and error text. |
| App unresponsive | Avoid assuming autosave. Retain available project/source copies before a restart. |
| Dialog closes | Inspect caption blocks and play them with sound; disappearance is not proof of a correct result. |
Record platform, version and symptom before changing the project
Do not immediately clear application cache or force-close the editor when a progress stall occurs. Perform these diagnostic steps first:
- Check timeline track state: Zoom out on your timeline. In some instances, captions have already been generated and placed on a secondary text track, even though the status dialog remains visible.
- Note your exact platform: Record whether you are using CapCut Web (browser), CapCut Desktop (macOS / Windows), or CapCut Mobile (iOS / Android), along with your app version number.
- Preserve original project files: Duplicate your project file or save a copy to local storage before clearing browser data or reinstalling the application.
Web checks for CapCut Web
Avoid refreshing or navigating away from an active recognition job. Check your connection and note whether an error appears. If you later try another supported browser, save the project first.
An extension conflict is a possibility to investigate with a controlled retry, not a conclusion from “99%.” Change one condition at a time and keep a record of what happened.
Desktop checks for CapCut Desktop
Observe whether the app still responds and whether other heavy applications are competing for resources. Task Manager or Activity Monitor can show resource activity; zero CPU usage does not prove a network timeout.
Save or duplicate the project if the interface allows it. If a restart is necessary, understand that recent unsaved edits may be lost. Check for an official update after preserving work. Do not infer a firewall problem from the percentage indicator.
Mobile checks for CapCut Mobile
Keep CapCut open during recognition and check the connection. Record the app/OS versions and whether the same source fails on another attempt.
Preserve the project and original media before restarting, clearing app data or reinstalling. CapCut’s mobile guidance includes app and cache checks, but availability and consequences vary by version; use its current help for those controls.
A controlled retry: protect original and test a sample
If subtitle generation remains stuck after performing platform checks:
- Duplicate your project: Create a duplicate copy of your project in the main workspace to preserve your cuts, media clips, and manual edits.
- Test a short 10-second sample: Export or duplicate a 10-second section of your video containing clear spoken dialogue. Attempt auto-caption generation on the short clip and compare its behavior. This is a diagnostic comparison, not proof of a server-wide issue.
- Re-run auto captions: If the sample succeeds, record the difference before trying your copied project again. Review any output for missing text and timing errors.
Enjoying this read?
Get weekly insights on video editing, AI workflows, and creator growth straight to your inbox.
If it persists: support evidence and caption playback review
If the 99% stall persists across multiple attempts and short test samples, gather the following information for official CapCut support:
- Exact operating system version, browser/app build number, and account subscription type.
- Video clip length, audio file format, and language selected during generation.
- Whether the failure occurs on all projects or only a specific media file.
If captions render on your timeline after a delayed response, review the output for accuracy and timing alignment before exporting.
Frequently asked questions
Does 99% mean my audio could not be recognized?
No conclusion about recognition success follows from the percentage alone. Inspect the actual caption result and compare it with the recording if it becomes available.
Will force-quitting CapCut delete my video project?
Force-quitting while a project is unsaved may result in loss of recent timeline adjustments. Keep available project and source copies. A frozen interface may not let you save the latest changes; do not assume they are recoverable.
Where should I go if captions fail completely or contain wrong words?
- For complete generation failure where no progress bar appears, see CapCut Auto Captions Not Working: What to Check.
- For fixing misheard words or proper names, see How to Fix Inaccurate Captions in CapCut.
- For importing pre-made subtitle files, see How to Import SRT Subtitles into CapCut.
Optional source-video caption workflow in Cubix
For a separate caption edit, start with your original video in Cubix. Upload the source footage, generate captions and review the wording, timing and placement before exporting the video. See the Cubix caption workflow for the relevant controls.
The editor entry opens Home. It does not transfer a third-party project or automatically upload/import the reader’s files.
Don’t miss the next one.
Join our newsletter for exclusive tips, product updates, and the latest from the Cubix team.