A CapCut export frozen at 1% or 99% gives you a place to start, not a diagnosis. The same damaged clip, unavailable asset or resource limit can surface at different percentages depending on platform and export settings. Protect the project first, then separate a save/download problem from a timeline/render problem with short controlled tests.
Quick answer: duplicate the project, note any error code, confirm free local storage and a writable destination, then export a short simple range at 1080p. If that works, isolate the failing timeline range or paid/cloud asset. If even a blank-project test fails, troubleshoot the app, browser, account or device rather than deleting project media.
This page is part of the CapCut Fixes hub. Never uninstall, clear app data or delete source files until an unsynced draft and its original media are backed up.
Before Retrying a Stuck CapCut Export
- Save evidence: screenshot the percentage, full message and error code.
- Duplicate the draft: use the copy for destructive tests.
- Keep media available: reconnect external drives and relink offline source files.
- Check the destination: use a normal local folder with free space; avoid a cloud-synced folder for the test.
- Run a control: export a few seconds from a blank project with one known-good local clip.
If the control export also fails, changing random timeline effects is unlikely to help. Update/restart the official app or browser, verify account and connection-dependent assets, and check the platform-specific section below. If the control succeeds, the original project or its media is the useful scope.
Is CapCut Export Slow or Stuck?
A percentage that sits still for a few minutes is not enough evidence. Heavy effects, optical-flow frames, denoise, captions, high-resolution sources and software encoding can make one range take much longer than the rest. Web adds a second stage: the cloud render can finish before the browser completes the download.
Use a controlled comparison instead of a universal timer:
- Record the percentage and time; do not cancel immediately.
- Duplicate the project and export five to ten seconds from a simple range at 1080p.
- Create a new project with one known-good local clip and export the same short duration.
- If both short tests work, return to the original timeline and isolate its failing range.
- If the new-project control fails, move to app, browser, device, account or destination checks.
Do not compare a 4K effect-heavy project with somebody else's plain 1080p clip. A changing percentage or growing output file suggests work is continuing, but neither guarantees a valid final file. The proof is a completed file that plays correctly.
There is also no safe universal free-space multiplier. CapCut can need room for temporary data as well as the final file. Check the device's real free space, choose a local destination, and leave a comfortable margin rather than matching only the estimated output size.
CapCut Export Stuck at 99%: Saving, Downloading or Finalizing
CapCut's current 99% guide says a late stall commonly involves local storage, a blocked save/download, permissions, complex projects or corrupted/unsupported media. It says the render may have finished, but that is not proof that every frame and stream is valid.
- Web: keep the tab open, allow downloads from CapCut, confirm the browser's download destination and free local space, then test a current Chrome or Edge build. A completed cloud render still needs a successful browser download.
- Desktop: choose a short filename and a writable local folder. Confirm the source drive is connected and the destination is not being moved or synced during export.
- Mobile: check device storage and the photo/media permission CapCut requests. Keep the app foregrounded for the test and turn off battery saver if it is terminating the export.
Do not wait for a universal number of minutes. Duration depends on source codecs, effects, resolution, frame rate, hardware and service load. Compare progress with a shorter/lower-resolution test rather than declaring a render dead from the clock alone.
CapCut Export Stuck at 1% or the Same Timeline Point
An early freeze can involve the opening range, but the percentage is not a reliable map to a clip. Start with a duplicate and split the project into halves. Export the first half, then the second. Continue halving the failing range until one clip, compound clip, transition, effect, caption, audio item or linked file remains.
CapCut's error-code guide supports this range-isolation method for codes 4114 and 10004. It gives more specific actions for other codes: rebuild compound clips for 22113, relink media for 10006, and change save location for -30007. Follow the displayed code before a generic checklist.
Replace or re-import only the isolated item and test the short range again. Keep the original file. Converting every clip to H.264 or deleting the first few timeline elements before proving the scope creates unnecessary quality loss and rework.
Export Resets From 99% to 5% or Starts Over
A progress bar that reaches the end and drops back is behaving like a failed finalization or retry loop. It does not prove that the timeline rendered cleanly. Stop repeating the same full export and preserve the evidence.
- Check whether a partial file exists and whether its size changes.
- Switch the test to a short filename and a normal writable local folder.
- Confirm free space and Web download permission where relevant.
- Run the blank-project control and then the first-half/second-half isolation test.
- Retry the same short range after changing only one variable.
A recent community report describes an export reaching 98–99% and resetting to 5%. That confirms the symptom, but anecdotal retries do not establish the cause. The destination, control export and range tests still provide better evidence.
CapCut Export Button Not Working, Loading or Greyed Out
If no export settings or progress window opens, check what the interface is waiting for:
- a paid-material or Pro verification prompt hidden behind the editor;
- an asset still downloading from the cloud;
- offline source media or an unfinished AI task;
- a browser extension/pop-up restriction on Web;
- a temporarily unresponsive app under memory pressure.
Save the draft, wait for visible asset downloads, close unnecessary apps/tabs and restart CapCut. Test the same account with a blank project. If only the original draft fails, return to timeline isolation. If Pro status is wrong at export, use the account checks in CapCut Pro not working rather than repeatedly buying or reinstalling.
CapCut Export Failed: Error Codes, Media and Hardware
| Evidence | Next safe test |
|---|---|
| Error 4114 or 10004 | Export sections; replace the isolated material |
| Error 22113 | Re-create compound clips in the duplicate |
| Error 10006 | Relink imported media |
| Error -30007 | Change to a writable local save folder |
| Crash or GPU message | Update OS/GPU driver; lower settings; test software encoding only if the current build offers it |
| No code | Compare blank project, short range and alternate destination |
Do not disable antivirus protection as a first-line fix. If security software explicitly quarantines CapCut or blocks a chosen folder, review its event log and create the narrowest trusted-app/folder exception you understand, or contact support. Do not delete the whole CapCut data directory: Desktop drafts and temporary data can be stored locally, and “cache” advice found online is frequently broader than it sounds.
Hardware acceleration controls and labels vary by version. Switching the encoder can be a useful A/B test when the export panel exposes it, but it is not a guaranteed fix and software encoding can be much slower. Record the original setting so it can be restored.
Project, App or Service Problem?
The control project separates most cases. If a known-good clip exports in a new project, the original draft, an asset or its settings are the scope. If every new project fails on one device, update and restart the official app or browser, test another writable folder and reduce export settings. If Web and connected cloud features fail across multiple simple projects, preserve the drafts and wait before reinstalling; the problem may be account-side or service-side.
Community threads can reveal a cluster—such as a recent report of exports repeatedly stopping at 30%—but they cannot prove a global outage. Use CapCut's current export-not-working guide and submit the exact version, platform, error, project scope and control-test result to support.
Platform-Specific Export Checklist
- Web: current supported browser, stable connection, tab kept open, downloads allowed, enough local space, no aggressive content blocker for the test.
- Windows/macOS: writable local destination, connected source drives, available disk/RAM, current CapCut and GPU/OS updates, known-good short export.
- iPhone/Android: free device storage, required photo/media access, charger if needed, app foregrounded, battery saver off for the test, lower resolution/frame rate comparison.
CapCut's template-export guide also separates browser/network, local desktop resources and mobile interruptions. Treat its numeric connection/storage examples as general guidance, not universal minimums for every project.
CapCut Export FAQ
Why is CapCut export stuck at 99 percent?
A late stall commonly involves saving or downloading the final file, low local storage, a blocked destination, permissions, complex media or a damaged asset. Check the destination and run a short control export; 99% alone does not prove the render is complete.
Why is CapCut export stuck at 1 percent?
The opening range is one possibility, but the percentage does not reliably identify a clip. Duplicate the project and export halves or short ranges until you isolate the failing material, then replace or relink only that item.
Why does CapCut export reset from 99 percent to a lower number?
Treat the reset as a failed finalization or retry loop, not fresh proof that the timeline is healthy. Stop repeated full attempts, verify free space and the save or download destination, then run a short control export and isolate the project if needed.
How long should I wait for a CapCut export?
There is no reliable universal time. Source codecs, effects, duration, resolution, frame rate, hardware and Web service load all matter. Compare a five-to-ten-second control export and a lower-resolution test instead of using another creator's render time as a deadline.
Why does the CapCut export button do nothing?
Look for a hidden Pro prompt, unfinished cloud or AI asset, offline media, Web pop-up restriction or an unresponsive interface. Save and restart, then compare a blank-project export with the affected draft.
Should I clear CapCut cache or app data?
Do not clear system app data, uninstall or delete desktop folders before backing up unsynced drafts and media. Use a clearly labeled in-app cache control only after checking its scope. A blank-project and short-range test is safer evidence.
Should I disable hardware acceleration?
Only as a reversible A/B test when your current Desktop build exposes an encoder control or reports a GPU issue. Record the original setting. Software encoding can be slower, and timeline media or storage can still be the real cause.
Can exporting in sections fix a failed CapCut project?
Sections help locate the bad range and reduce peak project load. Keep the original project and use matching settings for each segment; our lower-risk export settings covers resolution, frame rate, codec and audio choices. Join clean segments in a new draft after identifying the cause.
Why is CapCut export stuck at 15%, 20%, or 100%?
Those percentages are progress markers, not universal CapCut error codes. If the export repeatedly stops at the same mid-render point, such as 15% or 20%, export the timeline in sections to isolate a clip, effect, caption, or transition near that point. If it reaches 100% but never produces a file, check free storage, save permissions, and the destination folder. CapCut's stuck-export guidance points to device resources, connectivity, and project complexity, while its 99% guidance treats the final stage as saving.