> ## Content Index > Fetch the complete content index at: https://capcutguide.com/llms.txt > Use this file to discover other available public pages before exploring further. # CapCut Export Stuck? Fix 99%, 1% and Failed Exports - URL: https://capcutguide.com/capcut-export-stuck/ - Published: 2026-07-09T05:54:58.000Z - Updated: 2026-10-28T19:09:27.000Z - Description: Find out whether CapCut is failing on the timeline, saving the file or refusing to start. Use short tests and the exact error code before changing the project. - Author: Daniel Reyes - Tags: Fixes, Tutorials, Tips & Tricks **If CapCut export is stuck at 99%, the video has usually rendered and the final save or download is what's failing.** [CapCut's 99% help](https://www.capcut.com/help/export-stuck?ref=capcutguide.com) puts it down to low storage, a folder CapCut can't write to or damaged media. Free up space, save to another local folder (on Web, allow the browser download) and retry before you touch the timeline or reinstall. If it stops at 1% or at the same point every time, export one five to ten second clip in a new project first, then test sections of a duplicate. The percentage points to a likely cause; it can't tell you which clip, setting or device component is to blame. [Download](https://fetchify.surf/c/xHB0yiyBiqIs?ref=capcutguide.com) For other symptoms, head to [CapCut Fixes](https://capcutguide.com/capcut-fixes/). If CapCut won't open at all, run the [app startup checks](https://capcutguide.com/capcut-not-working/) before you try anything below. ## Where the export stops and what to check first Find the point where your export stops, run the first check, then use the linked section for the full steps. Make every timeline change in a duplicate, as the next section explains. A failed export can be retried; a damaged only draft can't. | Where it stops | What it usually means | First check | | -------------------------------------------------- | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Stuck at 99% | The video has usually rendered, but CapCut can't finish saving or downloading the file | Free space, a different local folder and the browser's download list. [99% checks](#capcut-export-stuck-at-99-saving-downloading-or-finalizing) | | Stuck at 1% | Not a timeline position: CapCut also points to resource limits and hardware-encoding conflicts | A short control project, then the hardware-encoding setting on Desktop. [1% checks](#capcut-export-stuck-at-1-or-the-same-timeline-point) | | Stops at the same point every time | Something in that part of the timeline, such as a clip, caption, transition or effect | Export each half of a duplicate, then narrow down the half that fails. [Range tests](#capcut-export-stuck-at-1-or-the-same-timeline-point) | | Reaches 99%, then starts over | The attempt restarted, and the counter doesn't show why | Check whether the file exists and plays, then change one thing, starting with the destination. [Restart checks](#export-resets-from-99-to-5-or-starts-over) | | Export does nothing, keeps loading or asks for Pro | The export panel or a premium asset is blocking the job, not the render | Let processing assets finish and restart the editor; for a Pro prompt, find the flagged asset. [Button and Pro checks](#capcut-export-button-not-working-loading-or-greyed-out) | | An error code appears | CapCut's code table gives a specific next step | Match the code: 4114, 10004, 22113, 10006, -30007, -1 or 4155\. [Error codes](#capcut-export-failed-error-codes-media-and-hardware) | | Slow, but the percentage still moves | Usually a heavy job rather than a stall | Compare with the short test and leave room for temporary files. [Slow or stuck](#is-capcut-export-slow-or-stuck) | | Even a short new project fails | The app, browser, device or account, not this draft | Restart, update, then run the checks for your platform. [Platform checks](#platform-specific-export-checklist) | ## Protect the draft, then run one simple test Leave the original draft and source files alone. Use the project's duplicate or copy command if your build has one, then make sure the copy opens with its media. CapCut itself recommends [duplicating a project before major edits](https://www.capcut.com/help/modify-history-task?ref=capcutguide.com). A duplicate inside CapCut protects you from editing the wrong timeline. It's **not an independent backup** against app-data deletion, though. Before any reset or reinstall, [verify a separate copy of the editable project and original media](https://capcutguide.com/backup-transfer-capcut-projects/). An exported MP4 isn't that editable copy. If you can't verify a backup, leave app data alone. 1. **Record the failure.** Note the percentage, full error message, app version, platform and export settings. Keep screenshots private if they contain account details, file paths or project names. 2. **Check storage and destination.** On a computer, choose a local folder you can write to, outside a syncing folder for this test. Use a new, short filename. Keep source drives connected. Do not free space by deleting media used in the draft. 3. **Create a control project.** Import one local clip that opens and plays, with no effects, templates or paid assets. Use about five to ten seconds and try 1080p, or a lower resolution if the source is smaller. This is a diagnostic sample, not a required project length or final-quality setting. 4. **Open the completed file outside CapCut.** Check picture, audio and duration. If it works, move to the affected project's range tests. If it fails too, start with the platform checks below rather than deleting items from the original edit. A successful simple export narrows down where to look next. It doesn't prove the device can finish a much larger job, or that every setting and asset in the original will work. ## Is the export slow or actually stuck? Give an active export time to work. High-resolution footage and complex effects can take longer than a plain clip, and progress won't always move at an even pace. A changing percentage or a growing output file suggests something is happening. Neither proves the final video will be valid. There's no dependable “cancel after five minutes” rule. Compare the small test above with the affected project instead. Don't treat a fixed storage multiplier as a guarantee either: [CapCut notes that exporting also uses temporary files](https://www.capcut.com/help/export-video-on-capcut?ref=capcutguide.com). Leave space beyond the estimated output, and on a computer, check the system drive as well as the destination. ## Stuck at 99%: check the save and download At this point, check where the file is going before you change the timeline. [CapCut's 99% guidance](https://www.capcut.com/help/export-stuck?ref=capcutguide.com) lists storage, permissions and interrupted downloads, and it lists problematic media too. CapCut says the render is usually done by now, but a damaged clip can still stop it late, so don't treat the file as healthy until it plays. - **Web:** keep the editor tab open. Check the browser's download list for a failure or permission request, then confirm its destination and free local space. A cloud render and a successful download are separate steps. Permit an expected download from CapCut; do not bypass a security warning about an unsafe file. If it still stalls, CapCut's 99% help suggests reloading the page and exporting from a different browser. - **Desktop:** retry the short test in a different writable local folder. Keep the source drive connected and avoid changing file locations while CapCut is using them. CapCut's [template-export help](https://www.capcut.com/help/template-export-gets-stuck?ref=capcutguide.com) adds that a 99% stall often means antivirus or disk permissions are blocking the final write, so check your security software's history or quarantine log for a blocked save before you change the project. On Windows, use the [Protection History checks below](#capcut-export-failed-error-codes-media-and-hardware) and keep protection on. - **iPhone or Android:** check device storage and the photo/media access CapCut requests. Keep the app visible during the test. If the phone is hot, let it cool before another attempt. Once a file finally shows up, play it all the way through, ending and audio included. A partial file, a thumbnail or a 100% counter isn't enough. If the video finishes but has no sound, use the separate [audio-after-export checks](https://capcutguide.com/capcut-no-sound/#capcut-has-sound-but-the-exported-video-is-silent). ## Stuck at 1% or repeatedly in the same place An opening clip or effect is worth testing, but **1% is not a timeline timestamp**. CapCut's [early-export guidance](https://www.capcut.com/help/export-stuck-at-the-begin?ref=capcutguide.com) also points to resource limits and hardware-encoding conflicts. So don't delete the opening shots just because the number is small. ### Mark a range without cutting up the master On Desktop, click into the timeline, move the playhead to your intended start and press **I**. Move to the end and press the letter **O**. Check the marked interval, then use Export. CapCut documents these [In and Out controls](https://www.capcut.com/help/export-clip-of-video?ref=capcutguide.com), and our [selected-range guide](https://capcutguide.com/export-selected-clip-capcut/) covers boundaries and builds that use different controls. [![CapCut Desktop timeline with In and Out markers around a short highlighted range and the playhead on the Out point](https://capcutguide.com/content/images/2026/10/capcut-desktop-in-out-export-range.webp)](https://capcutguide.com/content/images/2026/10/capcut-desktop-in-out-export-range.webp) Press I at the start and O at the end, then check the highlighted span and, where Export shows it, the range or duration before rendering. [Open full size](https://capcutguide.com/content/images/2026/10/capcut-desktop-in-out-export-range.webp). The keyboard steps above don't apply universally on Mobile or Web. If your editor has no range tool, trim only a verified working duplicate, and keep every track the test section needs. If you can't make a safe copy, don't cut anything from the only draft. ### Test both halves, then follow the result - **One half fails:** test smaller ranges within that half. Check overlapping captions, [transitions](https://capcutguide.com/capcut-transitions/), audio and effects as well as the video clip. Replace or relink an item only when the evidence points to it, and retain its original file. - **Both halves fail:** there may be multiple troublesome items, a shared effect or a wider export problem. Compare the simple control project before continuing to subdivide. - **Both halves work, but the whole project fails:** test a short section spanning the join. Compare the full export's settings, storage and resource use. A boundary interaction or the larger workload remains possible; you have not identified one bad clip. [![Three outcomes when testing both halves of a CapCut export: one fails, both fail or both pass](https://capcutguide.com/content/images/2026/09/capcut-export-range-results-20260912.webp)](https://capcutguide.com/content/images/2026/09/capcut-export-range-results-20260912.webp) One failed half, two failed halves and two successful halves lead to different next checks. This diagram explains the test; it does not guarantee that one clip is responsible. [Open full size](https://capcutguide.com/content/images/2026/09/capcut-export-range-results-20260912.webp). Selecting a range limits what gets exported. It doesn't promise to unload the rest of the project or cut peak RAM. A success at lower resolution is useful evidence too, but it doesn't pin down a single cause. If you need a usable file today, CapCut's [stuck-export guide](https://www.capcut.com/help/template-export-gets-stuck?ref=capcutguide.com) lists lower export quality as a fix: on mobile, tap Resolution before exporting and choose 1080p instead of 4K. I'd try that on the whole duplicate first, because it still gives you one continuous file instead of separate range exports. **Before the final full export, reset the test range.** Clear it with your build's range controls, or set I at the start of the full intended timeline and O at its end. Check both boundaries and the expected total duration, then look at the beginning and ending of the exported file. Don't count on clicking a different clip to clear an earlier range. ## Export reaches 99%, then starts over A counter that drops from 99% to 5% doesn't tell you why the attempt restarted. An [April 2026 user report describes that exact symptom](https://www.reddit.com/r/CapCut/comments/1sbq7qk/export%5Fkeeps%5Fresetting%5Fto%5F5%5Fpercent%5Fat%5Fthe%5Fvery/?ref=capcutguide.com), but that doesn't establish a finalization bug or a universal fix. Write down the sequence and any message. Check whether the expected file exists and plays. If it doesn't, point the control test at a different local destination, then follow the range results above. Change one variable per retry, so a successful attempt tells you something. Rerunning the same full render with no change adds little evidence. ## Export opens nothing, keeps loading or asks for Pro If no export panel opens, you may not be able to run the range checks yet. Save the draft, look for a dialog behind the editor, and if any asset is still visibly processing, let it finish. Close desktop apps or browser tabs you don't need, then restart the editor. CapCut's [button-response guidance](https://www.capcut.com/help/export-button-not-working?ref=capcutguide.com) also covers interface freezes and browser-extension conflicts. A Pro prompt is a different problem from a stalled render. Look at the exact [premium asset or export setting flagged by CapCut](https://www.capcut.com/help/join-capcut-pro-for-exporting?ref=capcutguide.com). Don't assume every 4K export needs the same plan on every account. If you've already paid, check the [purchase account and subscription status](https://capcutguide.com/capcut-pro-not-working/) before you buy again or strip down the edit. If the button won't respond even in the simple project, move on to the platform checks below. For an app that freezes outside export too, use the startup and app-response checks linked at the top. ## Use the displayed error code [CapCut's error-code table](https://www.capcut.com/help/export-issues?ref=capcutguide.com) lists different actions for different messages. Treat them as troubleshooting directions, not proof of a single underlying fault. Any timeline changes go in the duplicate. - **4114:** test sections and replace the material implicated by the tests. - **10004:** test sections; remove and re-add the implicated clip in the copy. - **22113:** CapCut recommends removing and rebuilding all compound clips. Preserve the master and check their contents and timing before attempting this in the duplicate. - **10006:** relink imported media. Confirm the original files still exist and are accessible before assuming the project itself is corrupt. - **\-30007:** try another writable local destination. Keep security protection on; use the security checks below if an actual block is recorded. - **\-1 or 4155:** CapCut recommends increasing virtual memory. On Windows, check the page-file guidance below. Do not apply Windows instructions to a Mac or phone. ### Windows: page-file and security checks are separate Microsoft explains that [page-file sizing depends on the system's workload](https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/how-to-determine-the-appropriate-page-file-size-for-64-bit-versions-of-windows?ref=capcutguide.com). Windows manages it by default, and letting it grow takes disk space. Before you try arbitrary numbers, check whether it's been disabled or manually restricted. On a managed computer, ask IT to review the setting. Don't reach for a fixed RAM multiplier or a “memory cleaner.” If a save is blocked, check [Windows Security's Protection History](https://support.microsoft.com/en-us/windows/security/windows-security/protection-history-in-the-windows-security-app?ref=capcutguide.com). Consider Microsoft's [allowed-app approach](https://learn.microsoft.com/en-us/defender-endpoint/controlled-folder-access-overview?ref=capcutguide.com) only when a recorded Controlled Folder Access event identifies the genuine, trusted CapCut installation. An executable's name alone doesn't prove it's safe. A malware quarantine is a different event: don't restore or allow a flagged file just to finish an export. ### Desktop: test hardware encoding reversibly If your build has it, open **Settings → Performance** and note the current hardware-encoding setting. Change only that control, follow any restart prompt, and run the same short test again. The official early-export guide recommends this check, though the option's availability and wording can vary by build. [![CapCut Desktop Performance controls for hardware encoding, hardware decoding and GPU interface rendering](https://capcutguide.com/content/images/2026/10/performance.webp)](https://capcutguide.com/content/images/2026/10/performance.webp) Encoding, decoding and interface rendering are separate controls. Record the original state and change one available setting at a time; labels and options can vary by build. [Open full size](https://capcutguide.com/content/images/2026/10/performance.webp). Don't change encoding, decoding and interface rendering at once, or you'll lose the comparison. Software encoding may take longer. If the test doesn't help, put the original setting back. On Mac, [Activity Monitor → Memory](https://support.apple.com/en-euro/guide/activity-monitor/actmntr1004/mac?ref=capcutguide.com) shows Memory Pressure and Swap Used. Check those instead of hunting for a Windows page-file control. ## If even the simple project fails - **Web:** save and verify the draft before refreshing. Retry in a current supported browser; CapCut suggests Chrome or Edge. Compare on another trusted connection. Test a suspected extension's effect only on CapCut, then restore it. Keep your working sign-in session and browser site data intact. - **Windows or Mac:** restart the app and computer, then check the official app for an available update. Do not interrupt an installer already running. CapCut's stuck-export guide also lists GPU driver issues among the usual causes, so on a Windows PC update the graphics driver too. I'd do that before any reinstall, because a driver update leaves your drafts alone. Keep the test destination local and leave source files where CapCut can access them. - **Android:** check storage, permissions and available updates. If needed, use the device's app settings to clear *cache*, not storage/data. [Google distinguishes temporary cache from permanently deleted app data](https://support.google.com/android/answer/15728899?hl=en&ref=capcutguide.com). Menu names vary by phone. - **iPhone or iPad:** open Settings → General → iPhone Storage or iPad Storage. Review what occupies space without deleting project media. [Apple's Delete App option removes related data](https://support.apple.com/en-us/108429?ref=capcutguide.com); it is not a harmless cache-clear button. Try restarting and an available official update first. [CapCut's platform-specific template advice](https://www.capcut.com/help/template-export-gets-stuck?ref=capcutguide.com) also recommends keeping a mobile export in the foreground. If battery saving interrupts the job, compare a short attempt with it turned off, then restore your preference afterward. Don't delete the CapCut data folder, and don't assume a rendered gallery video backs up the draft. ## When to stop retrying and contact support If several simple projects fail, especially when account or online assets fail too, that's where I'd stop retrying: keep the drafts safe and contact CapCut. Even that pattern doesn't prove a global outage. Send the platform, app version, exact error, available storage, export settings and the results of your control and range tests. Use the support link on [CapCut's official export-help page](https://www.capcut.com/help/export-issues?ref=capcutguide.com) or the support option in your app. If they ask for an example, send the smallest non-sensitive one that reproduces the issue. Don't post client footage, account identifiers, private paths or your full project publicly. If exporting clean segments is the only way you can deliver, keep their resolution, frame rate and audio settings consistent. Our [export-settings guide](https://capcutguide.com/capcut-export-settings/) explains those choices. Check the joins and the whole assembled file. Re-imported exports are flattened videos, not editable stand-ins for the original tracks, and exporting again can affect quality. ## CapCut export FAQ Why is CapCut export stuck at 99 percent? Check storage, save permissions and the browser download before changing the timeline. Problematic media can also cause a late failure. The percentage alone does not prove that rendering succeeded; open and check the completed file. Why is CapCut export stuck at 1 percent? An opening clip is one possibility, not a diagnosis. Test a simple new project and then ranges in a duplicate of the affected draft. Resource limits and hardware-encoding conflicts can also matter. Why does export reset from 99 percent to a lower number? The counter restarting does not establish the cause. Record the sequence and any error, check for a usable output file, then compare the destination, simple-project test and range results. Do not label it a confirmed finalization bug without further evidence. How long should I wait for a CapCut export? There is no reliable universal deadline. Duration, source media, effects, output settings and the device or online service affect the time. Compare a short test and watch for activity rather than using another person’s export time as a cutoff. Why does the CapCut export button do nothing? Save the draft, check dialogs and visibly unfinished assets, then restart the editor. Compare a simple project. A Pro prompt needs an account or flagged-content check; it is not the same as an unresponsive button. Should I clear CapCut cache or app data? Do not clear app storage, uninstall or delete app folders while an important draft has no verified independent backup. Android Clear Cache removes temporary data; Clear Storage deletes app data. On iPhone, Delete App removes related data and is not a harmless cache-clear action. Should I disable hardware acceleration? Only as a reversible comparison if your Desktop build exposes the relevant control. Record its original state, change hardware encoding alone and retry the same short section. Software encoding may take longer; restore the setting if it does not help. Can exporting in sections fix a failed project? It may provide a workaround or narrow the investigation, but does not guarantee one faulty clip or lower peak RAM. If both halves pass, test across the join and compare full-project settings and resource use. Check every segment and the assembled file. What if export stops at another percentage or reaches 100%? Treat the number as progress, not a code that identifies a clip. Use the same controlled tests. At 100%, confirm that the expected file exists and plays correctly; a completed counter alone is not a verified delivery.