A CapCut export that freezes at 1% and one that freezes at 99% are two different failures, and CapCut's own help center treats them that way. Most articles on this topic lump them together and hand you the same generic checklist. CapCut publishes a separate page for each, with different causes and different first moves.
If yours sits at 1%, the page you want is the one about exports stopping "right at the beginning" — and its headline suggestion is to go look at the start of your timeline.
What a 1% freeze actually means
CapCut's help article on this states it directly:
"If your video export stops right at the beginning, you may encounter the CapCut export stuck at 1 issue. 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."
Compare that with what CapCut says about the 99% case on its separate page:
"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."
The split is clean. At 99%, the render is described as finished and the problem is writing or downloading the result. At 1%, rendering has barely started — so the suspect is whatever CapCut has to read first.
Note the hedging in both quotes: CapCut says "usually means" and "in most cases," not always. Treat the 1% page as the most likely explanation, not a diagnosis.
The fastest fix: pull the first few clips off the timeline
For CapCut Online, CapCut's solution list for a 1% freeze includes this step verbatim:
"Remove early timeline elements: Temporarily delete the first few clips or effects and test the export."
Two details in that sentence do the real work:
- "Temporarily" — this is a test, not a rewrite. Delete, export, undo. You are trying to find out whether the export gets past 1% at all.
- "clips or effects" — a broken effect at the head of the timeline counts, not just footage. If the first clip alone does not clear it, remove the transitions, filters, and text sitting on top of it too.
Work in halves rather than one clip at a time. Cut the opening third of the project, try the export, and let the result tell you which side of the timeline to look at next. CapCut recommends the same bisection idea elsewhere: for error code 4114 its official advice is to "Export your video into smaller parts to find which clip or material is causing the issue," and for error code 10004, to "Export the video in sections to locate the problematic material."
Once you have found the offending clip, CapCut's own suggestion for media it cannot handle is to re-encode it outside the editor — its import troubleshooting page says to "Use a trusted third-party transcoding or conversion tool," then "Convert the video or image into a format supported by CapCut" and "Import the converted file into your project and continue editing."
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That runs in your browser tab — the file is re-encoded on your own machine and never uploaded, which matters when the clip in question is unreleased client work. Feed it the clip that stalls the export, drop the output back into the timeline in place of the original, and try again. If you need the output in a specific container instead, MOV to MP4 covers the most common case, since CapCut's page on videos not showing up tells PC users to "Reimport the video file or convert it to a common format, such as MP4."
Other causes, in order of likelihood
Not enough free space. Insufficient storage is the first cause listed on the 1% page. CapCut's template export troubleshooting gives one concrete figure, for CapCut Desktop: "Ensure Enough Storage: You need at least 2–3 GB free space on your export drive." That figure is stated for desktop only — CapCut does not publish an equivalent number for web or mobile.
Hardware encoding. For CapCut PC, the 1% page says: "Disable hardware encoding: Go to Settings → Performance and turn off hardware acceleration." Worth trying early because it costs nothing but export time.
The project file itself. Also from the PC section of the same page: "Duplicate the project: Open the copy and try exporting from the duplicated file." Cheap, non-destructive, and it occasionally clears a freeze that nothing else touches.
Settings that are too demanding for the machine. "Demanding export settings" is named in the 1% page's own list of causes. On the web version specifically, CapCut warns that "Large file size or high resolution: Exporting 4K videos or long projects may exceed browser processing limits," and suggests you "Export in segments: Export shorter clips and combine them later if the project is very long." If the high-resolution options are missing entirely rather than stalling, that is a separate question — see why CapCut shows no 4K export option.
Connection, if you are in the browser. CapCut describes web exports as depending on the cloud: "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." For template exports on CapCut Web, CapCut states that "A stable connection (≥10 Mbps) is required throughout the entire export" — that figure is given for that scenario, not for desktop.
Backgrounding the app, on mobile. CapCut lists these as mobile export failure causes: "Screen lock or switching apps pauses rendering" and "Low storage or battery optimization kills the process." Its instruction is blunt: "Keep the app in the foreground and disable auto-lock during export." If you started an export and went to check a message, that alone can explain a progress bar that never moves.
Cache and destination folder, on desktop. CapCut states that CapCut Desktop has no in-app Clear Cache button, and gives the manual locations for resetting temp files: on Windows, delete the contents of %LocalAppData%\CapCut\; on macOS, remove items in ~/Library/Caches/com.lemon.lvoverseas/. It also advises exporting to a local folder: "Avoid saving directly to cloud-synced folders (e.g., OneDrive, iCloud)."
How to tell it worked
The signal is simple: the counter moves past 1% and keeps climbing. If it now stalls at 99% instead, you have not failed — you have moved to a different problem, the one CapCut describes as rendering finished but saving incomplete, and the fixes there are about storage, permissions, and download rather than your opening clips.
Also give it time before declaring a freeze. CapCut's own guidance is that "A 5-minute 4K video can take 10+ minutes to export, depending on your hardware," and a progress bar that is slow to leave 1% is not the same as one that is stuck.
FAQ
Why does CapCut get stuck at 1% and not at 99%? Because they are different stages. CapCut says a 1% freeze usually means the problem happens very early in rendering, while a 99% freeze usually means rendering has finished and the app cannot complete the final saving process.
Which clips should I delete first to test it? The ones at the start. CapCut's instruction is to temporarily delete the first few clips or effects and test the export, so include effects, transitions, and text layers sitting over the opening footage, not just the footage.
Does a 1% freeze mean one of my files is corrupted? Not necessarily. Corrupted clips at the start of the timeline are one of four causes CapCut lists, alongside insufficient storage, demanding export settings, and temporary app glitches.
How much free space does CapCut need to export? For CapCut Desktop, CapCut says you need at least 2–3 GB free on your export drive. It does not publish a figure for the web or mobile versions — check the official documentation for those.
Will lowering the resolution fix it? It can help on the web version, where CapCut warns that 4K or long projects may exceed browser processing limits and suggests exporting in segments. On desktop, try disabling hardware acceleration first.
Want to fix the source file rather than fight the export? Start with the video compressor, browse all Clapr tools, or read the rest of our export and upload fixes. Everything runs locally in your browser.
