Protect the Project Before You Troubleshoot
Don't begin with a reinstall, “clear app data” or random deletion inside CapCut's folders. Those are not harmless refresh buttons. CapCut's own connection troubleshooting warns that clearing app data can permanently delete local projects and that uninstalling during an update can cost unsynced work.
Before a risky step, keep the source media where it is, duplicate the project if CapCut still opens, and confirm whether the project is local or uploaded to Spaces/cloud storage. An exported MP4 is useful insurance, but it is not an editable project backup.
The Fastest Diagnosis Is One Small Test
Create an empty project, add one short local clip and try the action that fails in the real project. That single test divides most CapCut problems into two useful groups:
- The clean project works: the original project, a media file, effect, font, caption track or timeline section is the likely trigger.
- The clean project also fails: look at the app version, device resources, account, network, permissions or a service-side problem.
If an export always stops at the same percentage, material around roughly the corresponding part of the timeline becomes a useful suspect, although the progress number is not a precise timestamp. Duplicate the project before removing or replacing anything. If it fails at different points, storage, heat, memory pressure, export path or background interruption becomes more plausible. CapCut's export guidance separates web, desktop and mobile causes for exactly this reason.
Work Out Which Layer Is Broken
CapCut won't open or keeps closing
Start outside the project: restart the app and device, confirm free storage, install the current official build and close competing heavy apps. If only one project crashes, stop treating it as an installation problem and isolate the project instead.
The app opens, but online tools are missing
Templates, sign-in, cloud sync and AI tools depend on a working connection and current session. Test another site, switch once between Wi-Fi and mobile data, check CapCut's network permission and sign in again only after you know the password or login method. A working editor with broken online panels is not the same problem as a completely offline device.
Only one project, clip or timeline section fails
Duplicate the project, then remove the newest effect, font, transition or media file one change at a time. A clip that plays in a gallery can still have an encoding problem CapCut dislikes. Re-encode a copy; don't overwrite the only source file.
Export starts but stalls, crashes or can't save
Check free space on both the working drive and export destination, choose a normal local folder, lower one setting for a diagnostic export and close other heavy programs. CapCut documents separate cases for an unresponsive Export button, general export failures and an export path without permission. Preserve the exact error message because each route starts somewhere different.
The file exports, but playback is wrong
Open it in a second player or device before exporting again. A black picture with working audio points somewhere different from a file with no audio at all. Check the original file, the timeline and the final export separately so you know where the failure first appears.
A paid feature, template or material disappears
Verify the exact login method and membership status before changing the installation. CapCut says Pro can appear unavailable when the plan is inactive, the wrong account is open, the app is outdated or the feature is region-restricted. Its official Pro diagnostic also distinguishes store subscription status from the CapCut account currently signed in.
Why a Missing Template Is Not Always a Bug
Template catalogs are not identical across mobile, desktop and web. They also vary by region, account state, app version and rollout. CapCut's template help lists region limits, outdated software, sign-in state, connection and navigation as separate causes. Check the same template on its intended platform before resetting anything.
This distinction matters because no amount of cache clearing can create a template that is not licensed, released or supported for that platform. The templates guide in the card grid handles the platform-by-platform checks without turning this hub into another full tutorial.
Watermark Problems Are Usually Visible in the Project
If a mark appears after export, identify what it belongs to before blaming the renderer. Check the final timeline seconds for an ending card, then inspect the template and every diamond/Pro-labelled asset. A template mark, paid effect and CapCut ending clip are different cases with different fixes.
Don't crop a watermark out until you understand the source; cropping can damage framing and leave the paid element in the project. The watermark guide shows how to remove or replace the actual trigger.
Use the Full Diagnostic When Symptoms Overlap
Open the full CapCut not-working diagnostic when several areas fail at once, the problem survives a clean test project, or you still can't say where it begins. Follow its order: service and account checks, network and permissions, storage and cache, version, then reinstall only after local work is protected.
If you reach support, send useful evidence: device and operating system, CapCut version, login method without exposing credentials, exact error text and whether a clean project works. Add the percentage or timeline timestamp where failure repeats and what changed before it started. “CapCut is broken” forces support to begin the diagnosis again.