When a CapCut export sits at 99%, the video has usually already been rendered. What is failing is the step after rendering — writing the file to disk, or downloading it out of the cloud. That distinction changes which fixes are worth trying, and it comes straight from CapCut's own help center rather than from guesswork.
What "stuck at 99%" actually means
CapCut's help page for this exact symptom opens with a description of the mechanism:
"If your video export stops at the final stage, you may encounter the CapCut export stuck at 99 issue. In most cases, the video has already finished rendering, but the app cannot complete the final saving process. This usually happens due to low storage space, corrupted media files in the project, or permission restrictions that prevent the exported video from being written to your device."
Three things are named there, and all three are about delivery, not rendering: storage, corrupted source media, and write permissions.
You can see how deliberate that framing is by comparing it with CapCut's separate page for the export that freezes at the other end of the bar. For a stall at 1%, the official wording is different:
"When exporting freezes at 1%, it usually means the problem happens very early in the rendering process. This can occur due to insufficient storage, corrupted clips at the start of the timeline, demanding export settings, or temporary app glitches."
Same product, two pages, two different attributions — early-timeline material and export settings at 1%, final saving at 99%. Most write-ups treat both as one "CapCut won't export" problem and send everyone to clear the cache. CapCut itself does not.
Why the browser version is its own case
This is the part that explains an otherwise baffling piece of advice. On CapCut Online, the first reason the official page lists is:
"Low local storage or download interruption: The video finishes rendering in the cloud but cannot be fully downloaded."
So on the web version, 99% is not your machine grinding through frames. The render happened on CapCut's servers; the bar is stuck on the download. That is why "Try another browser" appears in CapCut's own list of solutions for this page — swapping browsers does nothing for a render, but it is a perfectly sensible move against a stalled download.
CapCut's general "Why Can't I Export My Video" page reinforces the same picture for the browser:
"When editing videos using the browser version of CapCut, exporting relies on cloud processing and a stable internet connection. If the connection drops or the browser blocks certain scripts, the CapCut export problem may occur."
There is one bandwidth figure in the official documentation, and it comes with a narrow scope — it is stated for CapCut Web template exports: "A stable connection (≥10 Mbps) is required throughout the entire export." Note the last four words. A connection that drops for a moment near the end is exactly the failure mode that leaves you at 99%.
The fastest fix
Work in this order. Each step maps to something CapCut states rather than to folklore.
- Free up space, then change where the file is being written. CapCut's solution for desktop is literally "Change export location: Save the video to a different folder." On the storage side, its template-export guidance for CapCut Desktop is "Ensure Enough Storage: You need at least 2–3 GB free space on your export drive."
- Do not export straight into a synced folder. Same page, CapCut Desktop section: "Export to A Local Folder: Avoid saving directly to cloud-synced folders (e.g., OneDrive, iCloud)." A sync client fighting you for the file during the final write is precisely a "cannot complete the final saving process" scenario.
- On CapCut Online, try another browser and keep the connection up. The render is already done; you are retrying a download.
- On mobile, stop touching the phone. CapCut lists "Screen lock or switching apps pauses rendering" and "Low storage or battery optimization kills the process" among the reasons mobile exports fail, and its first instruction is "Keep the app in the foreground and disable auto-lock during export."
Once the file finally lands, you may find you exported at a higher resolution than the destination needs — and re-running a fragile export just to get a smaller file is the last thing you want. Shrink the file you already have instead:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs inside your browser tab. Nothing is uploaded, which matters here: if a flaky connection is what broke the export in the first place, adding another round trip to someone's server is not an improvement. Other conversions run the same way — see all Clapr tools, or go straight to compress video.
Other causes, in order of likelihood
Corrupted media inside the project. It is the second cause named on the 99% page. CapCut's error-code page gives a matching procedure — for code 4114: "Export your video into smaller parts to find which clip or material is causing the issue," then "Replace the problematic material, then try exporting again." For code 10004 it says "Export the video in sections to locate the problematic material." Be aware that the official page gives fixes for each code, not definitions of what each code means, so treat these as procedures rather than diagnoses.
Something blocking the write. For code -30007, CapCut's listed steps are "Turn off antivirus software temporarily," "Change the save location for the exported file," and "Try exporting again." That trio lines up with the "permission restrictions" cause on the 99% page.
Stale temp files on desktop. Worth knowing before you go hunting for a button that does not exist: CapCut states that "CapCut Desktop does not have an in-app "Clear Cache" button." To reset temp files manually, its instructions are to delete the contents of %LocalAppData%\CapCut\ on Windows, and to remove items in ～/Library/Caches/com.lemon.lvoverseas/ on macOS.
The project is simply too big for the browser. CapCut lists "Large file size or high resolution: Exporting 4K videos or long projects may exceed browser processing limits" among the hidden causes on web, and its suggested workaround is "Export in segments: Export shorter clips and combine them later if the project is very long."
It is not actually stuck. CapCut's own caution: "A 5-minute 4K video can take 10+ minutes to export, depending on your hardware." A progress bar that has not moved for two minutes on a long 4K timeline is not yet evidence of a failure.
How to tell it worked
Go to the export folder and confirm the file exists with a plausible size — the 99% symptom is about the file being written, so the file on disk is the real verdict, not the progress bar. Then play it outside the editor. CapCut's own advice on mobile is to "Play the exported video on a computer or external player—not just in the CapCut app—to confirm true quality." If it opens and plays through to the end elsewhere, the save completed.
FAQ
Why does CapCut get stuck at 99% and not finish? Because rendering and saving are separate steps. CapCut states that in most cases the video has already finished rendering and the app cannot complete the final saving process, pointing at low storage, corrupted media in the project, or permission restrictions.
Is my video already saved somewhere if it stalls at 99%? CapCut does not say where partial output goes, so check your chosen export folder before re-exporting. If nothing usable is there, the write did not complete.
Why do people say to switch browsers for CapCut Online? Because on the web version the render happens in the cloud and the last step is a download. CapCut's own wording is that the video "finishes rendering in the cloud but cannot be fully downloaded," and "Try another browser" is one of its listed solutions.
Does clearing the cache fix a CapCut export stuck at 99%? There is no in-app cache button on CapCut Desktop — CapCut says so explicitly and gives manual folder paths instead. Free space and export location are the causes it names first for this symptom, so start there.
Is stuck at 1% the same problem as stuck at 99%? No. CapCut publishes separate pages with different causes: early-timeline clips and demanding export settings for 1%, final-save failures for 99%. For anything else — file size caps, formats, upload rejections — browse the fix guides or the walkthrough for Premiere Pro's "Error compiling movie", which is a different editor with a similar write-stage failure.
All CapCut behaviour cited here comes from CapCut's official help center (capcut.com/help/), checked 18 September 2026. CapCut's marketing pages sometimes state things the help center does not — check the official documentation for anything not quoted above.
