If your CapCut export is stuck, fails with an error or finishes without saving a video, start with checks that do not alter the original edit. The safest order is to identify the exact symptom, check available space and export demand, follow the relevant platform checks, and then test whether one part of the timeline is causing the failure.

Keep the original draft intact throughout this process. Do not clear app data, uninstall CapCut or delete local project files when the effect on locally stored drafts has not been confirmed for your device.

Identify how the CapCut export is failing

Before changing settings or timeline items, record what happens during the failed attempt. Different symptoms call for different tests, although the progress percentage by itself does not prove the cause.

Symptom What to record First diagnostic focus
Progress freezes at a fixed percentage The percentage and whether it changes after another attempt Available space, export demand and the current project
An export error appears The complete message and exact error code The applicable official error guidance
Rendering appears to finish, but no file is saved The intended destination and whether CapCut reports a permission or path problem Free space and an accessible save location
Only one project fails Whether a small test project exports normally Media or demanding elements in the affected timeline
Every project fails The platform, available space and whether the problem persists after a retry Platform-wide storage, browser or temporary software conditions

Do not assume that stopping at 1%, 50% or 99% identifies a particular clip or effect. Instead, compare another project if one is already available. If other projects export but the current one does not, that narrows the diagnostic scope to the current timeline without proving that any particular item is corrupted.

Capture any displayed error code before dismissing the message. CapCut maintains separate instructions for some codes, and the exact code can also help if the problem ultimately requires support.

Try the safest supported export checks first

CapCut identifies insufficient storage and demanding export conditions among the possible reasons an export will not complete. Its CapCut export troubleshooting guidance supports starting with the following reversible checks.

  1. Check available space at the destination. Free storage on an Android device, iPhone or iPad, or free disk space on a Windows PC or Mac. CapCut does not provide one universal amount that guarantees a successful export, so avoid relying on an unsupported storage threshold.
  2. Retry without altering the timeline. A fresh attempt can show whether the failure was temporary. Keep the original project unchanged while testing.
  3. Test a lower resolution or frame rate. Use this only as a diagnostic comparison. If the less demanding export succeeds, resource or processing demands may be involved, but the result does not establish one exact cause or require you to accept those settings permanently.
  4. Note whether the output file is created. If progress completes but the file is absent, focus on the destination, available space and permissions rather than repeatedly changing the edit.

These checks are designed to preserve the project. Avoid jumping to app-data clearing, reinstallation or local-file deletion, because those actions can put locally stored drafts at risk when their platform-specific consequences are unknown.

Use the checks that match your platform

Mobile, desktop and web exports do not rely on identical conditions. Follow only the branch that matches where you are exporting.

Android, iPhone and iPad

  1. Confirm that the device has free storage, then retry the export.
  2. Test a less demanding resolution or frame rate to see whether export demand is contributing to the problem.
  3. If the failure continues, restarting CapCut or the device is a reasonable temporary-state test, but it is not a guaranteed fix.
  4. Updating CapCut may help when outdated software is involved. Use the update mechanism available on your device rather than relying on an unverified in-app path.

On Android, clearing CapCut’s cache may help as a cautious test. The location of that control varies by device. Do not select clear data or clear storage, and do not assume that iPhone or iPad provides the same Android-style cache control.

Windows and macOS

  1. Check that the local disk has free space.
  2. If CapCut cannot use the current destination, select a different accessible export folder.
  3. As a test, close resource-heavy background applications before retrying a demanding project.
  4. If necessary, restart CapCut and check for an available update. Neither action guarantees that a project-specific failure will be resolved.

Desktop exports are processed using local resources and require both usable disk space and an accessible save location. A path or permission problem is especially relevant when rendering appears to finish but CapCut cannot create the output file.

CapCut Web

  1. Check that the internet connection remains available during the export.
  2. Clear the browser cache, then retry the project.
  3. Update the browser if an update is available.
  4. Test the export in another current browser to determine whether the problem is browser-specific.

CapCut Web depends on both browser and internet conditions, unlike a local desktop export. Do not apply undocumented bandwidth requirements or assume that one browser will always work. If the export succeeds in another current browser, the original browser environment is the more useful diagnostic focus.

Test whether one timeline item is blocking export

If a small test project or another existing project exports normally, investigate the affected timeline without immediately deleting anything. CapCut’s export error guidance recommends exporting in smaller parts to help isolate a problematic section.

  1. Preserve the original edit. Keep the existing draft unchanged. If your current CapCut version provides a way to make a test copy, use it only after confirming that the original remains available.
  2. Export a smaller section. Test one portion of the timeline rather than the complete project.
  3. Compare the results. If one section exports and another repeatedly fails, narrow the failing section into smaller segments.
  4. Inspect the isolated segment. Look for source media, compound clips or other demanding elements within that segment. Their presence makes them candidates for testing, not confirmed causes.
  5. Change only the test version. Temporarily replace or remove one candidate at a time, then export the same segment again. Do not perform destructive trial and error on the only copy of the project.

If CapCut explicitly identifies missing or unavailable source media, re-link that media before retrying. Do not assume a clip is unavailable merely because the progress bar stops near it or freezes at a particular percentage.

This smaller-section method provides useful information even when it does not reveal one defective item. If every section exports separately but the complete timeline does not, the combined project demand may be relevant; the lower-setting test can then provide another comparison.

Handle exports stuck at 99%, save failures and unresolved errors

An export stuck at 99% does not prove that rendering is complete or identify one specific cause. According to CapCut’s guidance for exports stuck at 99%, possible final-stage causes include insufficient storage, save permissions and problematic media.

  1. Check available storage or disk space again, particularly on the destination used for the output file.
  2. On Windows or macOS, retry with a different accessible export location if the current path cannot be used.
  3. On CapCut Web, repeat the connection, browser-cache and alternate-browser checks already covered.
  4. If only this project sticks at 99%, export smaller timeline sections to identify whether one segment reproduces the failure.
  5. If an exact error code appears, record it and use CapCut’s current official instructions rather than applying an unrelated code-specific fix.

If the export still fails after these checks, prepare concise diagnostic details before seeking CapCut support: your platform and device, project length, attempted export resolution and frame rate, the frozen percentage, whether other projects export, the intended save location and the complete error message or code. Some export errors require support follow-up, and these details make the problem easier to distinguish from a general storage, browser or project-specific failure.

Why is my CapCut export stuck at 99%?

CapCut identifies insufficient storage, save permissions and problematic media as possible final-stage causes. Check available space and the save location, then test smaller timeline sections if only one project fails. The 99% reading alone does not prove which cause applies.

Why does only one CapCut project fail to export?

If other projects export normally, the current timeline becomes the most useful diagnostic scope. Preserve the original draft, export the affected project in smaller sections and inspect the segment that repeatedly fails. This can narrow the problem without assuming that a particular clip or effect is responsible.

What should I check when CapCut Web will not export?

Check the internet connection, clear the browser cache, update the browser if an update is available and test another current browser. CapCut Web depends on browser and internet conditions, so a successful test in another browser can help distinguish a browser-specific problem.