My export bar sat at 99 percent for 11 minutes last Tuesday on a 23-clip TikTok compilation I'd promised a client by 9 a.m. I'd seen this exact freeze before, so I didn't restart anything right away. That instinct saved the render. If your CapCut export is stuck at 99%, frozen at 1%, or the export button won't respond when you tap it, you're not looking at one bug. You're looking at three different problems that happen to feel identical from the outside.
Quick answer: CapCut export stuck at 99% almost always means the video already finished rendering and the app is failing to write the final file, usually because of low storage or a blocked save location. Stuck at 1% points to something broken near the start of your timeline, often a damaged clip. A dead export button means the app interface itself has frozen, which has nothing to do with rendering at all. Treating all three the same way wastes time.
This guide is part of the CapCut Fixes hub. Start there if you need symptom-first fixes for crashes, export failures, no sound, watermark issues, Pro features, or install problems.
Why CapCut Export Gets Stuck or Fails
Every export failure in CapCut traces back to one of four things: storage space, a damaged file somewhere in your project, a hardware or connection conflict, or the app simply losing focus mid-task. Which one you're dealing with depends on where the progress bar stops.
I keep a mental rule now after four separate export failures on the same laptop in one month: if the bar dies early, blame the timeline. If it dies late, blame the device. If the bar never moves and the button just sits there, the app has locked up before rendering even started. That single distinction cuts your troubleshooting time by more than half.
CapCut Export Stuck at 99 Percent on Mobile, Desktop, and Web
This is the one almost everyone hits eventually. Your video finishes rendering. The bar climbs to 99% and then stops moving, sometimes for a few minutes, sometimes indefinitely. What's happening: CapCut has finished processing the footage and is trying to save or write the final file, and that last step is getting blocked.
On CapCut Online, the render happens in the cloud, so a 99% freeze often means the file finished on CapCut's servers but could not fully download or save locally. Check browser download permissions, local storage, connection stability, and whether your project contains unusual or corrupted media. If your CapCut Cloud space is full, clean it up too, but treat that as one possible account-side limit rather than the default cause.
On CapCut PC, the usual suspects are disk space, a corrupted clip or audio file somewhere in the project, or a permissions problem with the folder you're saving to. Switching the export destination to a plain local folder, away from anything synced through OneDrive or iCloud, fixes this more often than people expect.
On CapCut Mobile, it's almost always device storage or a storage-access permission CapCut doesn't have. Free up space, confirm CapCut can write to your device storage in system settings, and restart the app before trying again. CapCut's own help center entry on this issue walks through the same storage and permission checks for each platform.
Most tutorials tell you to just wait it out. Sometimes that's right, cloud rendering on a long or 4K project can take several minutes on its own. But if you're past ten minutes with no movement and no other app is using your bandwidth, waiting stops being patience and starts being denial.
CapCut Export Stuck at 1 Percent Is a Different Bug Entirely
Freezing at 1% means the problem showed up almost immediately, which usually points to something at the very beginning of your timeline rather than a resource issue at the end. A damaged clip, a broken transition, or an effect applied to your first few seconds can all stop the export before it really starts.
Here's the isolation method that works: delete the first three or four elements on your main track and try exporting again. If it moves past 1%, you've found your culprit. Add the pieces back one at a time, exporting after each addition, until it freezes again. That's your broken clip.
If isolating elements doesn't turn anything up, duplicate the whole project and export from the copy instead. Project files pick up minor corruption more often than people assume, and a duplicate sidesteps it without touching your original edit. Lowering your resolution, frame rate, or bitrate before exporting also helps if the freeze is a resource problem rather than a corrupted asset. On desktop, go to Settings, then Performance, and turn off hardware-accelerated encoding. That one setting resolves a surprising share of 1% freezes on older graphics cards. CapCut documents this exact scenario in its export stuck at 1% guide, which is worth a look if the isolation method above doesn't turn anything up.
CapCut Export Button Not Working or Greyed Out
This is the odd one out because rendering never even begins. You tap or click export and nothing happens: no progress bar, no error, no response. That's an interface freeze, not an export failure, and it usually comes from the app running low on memory or getting stuck on a background task.
Close other apps and programs eating memory, then restart CapCut completely rather than just backgrounding it. If the project is heavy, meaning lots of layered effects, keyframes, or 4K clips, simplify it before trying again. Clearing the app cache and updating to the latest version clears out a good chunk of these freezes too, since CapCut tends to ship export-stability fixes in its regular updates.
If the button hangs only when your project uses Pro-marked assets, reconnect to the internet, relaunch CapCut, and let your account status sync before exporting again. Treat this as an account or asset check, not the main cause of a dead export button. Most export-button failures are still interface freezes, memory pressure, cache, browser extensions, or project overload. CapCut's official troubleshooting page for this issue covers the same interface-freeze causes in more depth.
CapCut Export Failed Error Message: Codec, GPU, and Cache Issues
An outright "export failed" message, rather than a stalled bar, usually points somewhere more specific: an unsupported file format, a GPU conflict, or cache corruption. MKV, AVI, HEVC, and variable frame rate footage tend to be the formats most likely to trip this up, particularly on desktop.
Start by disabling hardware acceleration in Settings, then Performance. CapCut sometimes defaults to GPU rendering for a codec your graphics card doesn't fully support, and forcing CPU rendering instead often clears the error immediately. If that doesn't help, convert the problem clip to standard MP4 with H.264 before re-importing it.
Cache corruption is the quieter cause. On Windows, clear out %LocalAppData%\CapCut\. On Mac, clear ~/Library/Caches/com.lemon.lvoverseas/. If your desktop build exposes cache management in Settings, use that first. If not, close CapCut and clear the local cache folder manually, then restart the app. For CapCut Online specifically, an export failure is almost always a dropped connection mid-render. Check your internet, then refresh and start over rather than trying to resume. CapCut's general export troubleshooting guide breaks down these platform-specific causes in more detail.
CapCut Export Fixes Quick Reference Table
| Symptom | Most Likely Cause | First Fix to Try |
|---|---|---|
| Stuck at 99% | Low storage or blocked save location | Free up space, change export folder |
| Stuck at 1% | Corrupted clip near timeline start | Isolate and test the first few clips |
| Button not responding | App interface frozen or overloaded | Close background apps, restart CapCut |
| "Export failed" message | Unsupported codec or GPU conflict | Disable hardware acceleration |
How to Stop CapCut Export Problems Before They Start
Give yourself more free storage than you think you need. A few gigabytes of headroom beyond your expected file size tends to prevent most 99% freezes before they happen. Export to a plain local folder, not one synced through OneDrive, Google Drive, or iCloud, since those services can lock the file mid-write.
Keep the app updated on whichever platform you use. Recent CapCut Android and CapCut iOS builds have included regular stability fixes, and running an old version is one of the easier problems to rule out entirely. If you're working on something long or effects-heavy, export in smaller segments and stitch them together afterward instead of rendering the whole timeline in one pass. Dialing in your export settings before you're on a deadline saves you from discovering a bad codec choice at the worst possible moment.
And if you're minutes from a deadline with a project that keeps failing, don't keep retrying the same export. Drop the resolution to 1080p, export a low-quality version first to confirm the project itself is sound, then decide whether you have time to re-export at full quality. A usable video beats a perfect one that never finishes rendering.
CapCut Export FAQ
Why does CapCut export get stuck at 99 percent?
In most cases, your video has already finished rendering and CapCut is failing to write or save the final file. Low storage space, a blocked save folder, or a permissions issue are the usual causes, and they vary slightly by platform.
Why does CapCut export freeze at 1 percent?
A freeze this early usually means something near the beginning of your timeline is broken, most often a corrupted clip, effect, or transition. Isolating and testing the first few timeline elements is the fastest way to find it.
Why is the CapCut export button greyed out or unresponsive?
This points to the app interface freezing before rendering even starts, typically from memory overload or a heavy, complex project. Restarting CapCut and closing background apps resolves it more often than not.
How long should a CapCut export normally take?
It depends heavily on project length, resolution, and your device, so there's no fixed number to expect. A short 1080p clip should finish in well under a minute on most modern devices, while long or 4K projects, especially rendered through CapCut Online, can take several minutes.
Does exporting in smaller sections fix CapCut export failures?
Often, yes. Splitting a long or heavy project into shorter segments and stitching them together afterward reduces the load on your device during each individual render, which sidesteps a lot of resource-related failures.
Should I turn off hardware acceleration in CapCut?
If you're seeing export failures, stuck renders, or codec-related errors, disabling hardware-accelerated encoding under Settings, then Performance, is worth testing. It shifts the rendering load to your CPU instead of your GPU, which resolves a fair number of export failures on older or less-supported graphics hardware.