If CapCut keeps crashing, note the last successful action before it closes. A launch crash, an import crash, a repeatable timeline crash and an export crash need different tests. Start with the matching branch below instead of clearing data or reinstalling the app.
Avoid uninstalling, tapping Clear storage, or deleting a desktop data folder before the draft is safe. Local-only work can sit inside the data those actions remove. Back up the project and verify the copy first. Reinstalling belongs at the end of the diagnosis.
Quick answer: protect the draft, reproduce the crash once, and write down the last successful action. If every project fails, test the app, device, storage and graphics path. If one project fails at one timestamp, isolate the clip or effect. If CapCut closes only during export, test the render settings and destination before touching the installation.
For everything else that goes wrong in the app, start from the CapCut fixes hub.
Fact-checked August 26, 2026 against current CapCut Help, Apple Support, Android Developers and Microsoft Support. Interface labels can move between builds, so record what your version shows before changing a setting.
Protect the Project Before You Touch App Data
On Android, Clear cache and Clear storage are not two names for the same control. CapCut says to use Profile → Settings → Clear Cache and never clear App Data in system settings because it permanently deletes local projects. Treat Delete App on iOS, an uninstall, and deletion of desktop User Data as destructive until the draft has been verified elsewhere.
Do this before you change anything:
- Upload the project to CapCut Spaces, then confirm it opens from another device. Don't assume that signing in has backed up every local project. On desktop, Spaces sits in the left-hand toolbar; CapCut's guidance on reaching your cloud space also warns that cloud content is tied to one specific account, which matters if you sometimes sign in with TikTok and sometimes with Google.
- Keep your own copy of every source file. Save the original video, images, audio and custom fonts. A copied project folder may preserve the timeline without the files it references; restoring that folder can still leave every clip offline.
- Export a reference copy if the project still opens. Even an unfinished 1080p render preserves timing, crop and caption placement for a rebuild; it doesn't replace the editable project.
On desktop, the guide to finding and copying CapCut project folders explains the current checks. Use Settings → Save to or the Details panel of an open project to identify the path shown by your build. A path copied from another computer or an old article is not proof that your draft lives there.
On Android, don't treat a manual folder copy as a backup. Android 11 restricts access to the Android/data directory and all its subdirectories, so a file manager or a USB connection may reach nothing, or produce a partial copy that has not been verified as restorable. Use Spaces and keep your own source files.
Crash, Freeze or Lag? Record the Exact Failure
A crash closes CapCut and returns you to the home screen or desktop. A freeze leaves the window visible but unresponsive. Lag is different again: the interface still reacts, only slowly. Record which one happens before applying a fix, because a stalled export, overloaded preview and process crash don't share one diagnosis.
The distinction changes what you do next. A desktop or Web export sitting at 99 percent may still be writing the final file. CapCut lists antivirus software and destination-folder permissions as possible blockers for a stuck export. Wait, check the destination for a finished file, then test a local writable folder before treating the stall as an application crash.
Start With the Last Successful Action
Note the last thing on screen before it went. That one detail narrows the cause faster than any checklist.
| When it fails | Likely causes | Start here |
|---|---|---|
| Instantly at launch | Outdated build, temporary data, compatibility or graphics conflict | Record the version, update, restart |
| Opening the import window | System file picker, permissions, or a very large media folder | Drag and drop instead |
| After media is added | Format or encoding the build doesn't support, or a damaged file | Add clips one at a time |
| Scrubbing the timeline | Memory pressure, effect load, or project complexity | Proxy, lower preview quality |
| At export | Storage headroom, project element, encoder or destination folder | Test a short range, then save locally |
| Only on templates | Template assets failing to load, or a version mismatch | Update, try another template |
| At the same timeline position every time | One clip, effect, transition or audio element | Inspect the elements around that timestamp |
| After sustained heavy work | Heat, memory pressure, or project complexity | Cool the device, test a lighter project |
| Right after an app update | A regression, or a bad interaction with old temporary data | Clear cache, test a blank project |
If It Closes Before the Project List Appears
Start with your CapCut version number. Tap Me, the settings icon at top right, then scroll to the bottom; on desktop it is Settings then Version. CapCut documents both paths. Once the project is safe, install the current official build and repeat the same test.
If it still dies before the project list appears, restart the device and use only the safe cache route documented for that platform. If CapCut closes when the local project library appears, opening the synced copy from Spaces on another device can separate a local-library problem from an account or cloud problem. Don't delete the local library merely to test that theory.
If Import Triggers the Crash
Two different failures hide under this heading, and they need different fixes.
If CapCut dies the instant the import window opens, try dragging one small known-good file from Explorer or Finder onto the timeline. Recent r/CapCut reports describe import-triggered crashes, while a separate Windows 11 report describes the same file-dialog failure across several editors. These are diagnostic clues, not proof of one cause. If drag and drop works, test another app's Open dialog and check CapCut's photo or media permission before reinstalling.
If CapCut closes after a file is added, test media compatibility. CapCut states plainly that a familiar extension doesn't guarantee support: a file labelled MP4 or JPG can hold an underlying format the app can't read, and renaming an extension changes nothing. Play each clip outside CapCut first, then add clips one at a time to find the offender.
Keep the original file untouched. Convert a copy with a trusted tool into a format CapCut currently lists for your platform, then import only that copy. If it works, the original file or its encoding becomes the lead suspect. The result still doesn't identify a single codec defect by itself.
If One Timeline Crashes at the Same Point
If a blank two-clip project stays stable, compare it with the failing project before changing the whole app. Close heavy background programs and lower preview quality. CapCut describes Proxy as a playback-performance feature; test it if your build offers the control. A proxy can make preview decoding lighter, but it can't repair a damaged source file or effect.
To find a specific bad element, halve the timeline. Disable or delete the back half, test playback, then keep halving whichever half still crashes. Each pass halves the search area, so a large timeline can usually be narrowed to a small group of clips or effects quickly. If the crash lands at the same timestamp every run, start with the clip, transition, caption or audio element sitting at that point.
If Editing Works but Export Closes the App
Export failures have their own causes and their own guide. In its template-export guidance, CapCut asks for at least 2–3 GB free on the desktop export drive and more than 1 GB on mobile. Those figures are troubleshooting minimums for that workflow, not universal capacity estimates. Longer, higher-resolution or effect-heavy projects may need substantially more working space.
CapCut's export error-code guide gives the same isolation method for codes 4114 and 10004: export the timeline in sections, find the material that fails, then replace or re-add it before trying the full render again.
Export a five- or ten-second range around the suspected timestamp first. If that fails, replace or disable the nearby clip, compound clip, effect or audio item. If it succeeds, test 1080p/30fps to a local folder, close background programs and switch off battery saver on mobile. Our CapCut export settings guide covers the quality trade-offs; CapCut export stuck maps stalled percentages and current error codes.
If CapCut edits normally and only fails at export, test export settings, storage, the destination folder and individual timeline elements before you reinstall anything.
Safe Tests on iPhone and iPad
- Force close and reopen. This clears runtime state without touching files.
- Update the app, then restart the phone.
- Clear the in-app cache: Me, settings icon, Clear cache. This doesn't delete projects.
- Free real storage. CapCut cites more than 1 GB free in its template-export guidance; treat that as a bare minimum, not a general storage target.
- Turn off Low Power Mode. CapCut advises keeping the app in the foreground and disabling auto-lock during export, and notes that a screen lock or switching apps pauses rendering.
- If you need a clean app binary, use Settings → General → iPhone Storage → CapCut → Offload App. Apple confirms that offloading keeps documents and data, while Delete App removes the app and related data. CapCut still tells users to sync projects first, so verify the draft in Spaces before relying on offload.
Safe Tests on Android
- Force close, update, restart the phone.
- Clear the in-app cache from Me and the settings icon first.
- If that is not enough, use Settings, Apps, CapCut, Clear cache, which is the path CapCut itself documents. Leave Clear storage alone unless your project is already in Spaces.
- For an export crash, turn off Battery Saver, keep CapCut in the foreground and repeat the same short test. Restore the battery setting afterward.
- Check photo and media permissions if imports fail.
- Free working space by moving finished exports off the device, then verify the available-storage number before repeating the test.
Windows: Test the Driver, GPU and Cache Paths
Install Windows and optional driver updates first. Microsoft recommends Windows Update for routine driver updates and the hardware maker's official site when Windows has no newer compatible driver. CapCut also names outdated graphics drivers as a cause of rendering freezes. Avoid third-party driver-download sites.
Then work through Menu, Settings, Performance:
- Hardware acceleration. CapCut currently tells Desktop users to turn hardware-accelerated encoding and decoding off for some failures. Treat this as a controlled test, not a permanent setting: change both, save, restart CapCut and repeat the same project action. If the crash remains, restore the original state before the next test.
- Proxy. Turn Proxy on if the current build exposes it, then repeat the same playback test. CapCut currently places the control under Menu → Settings → Performance in its help material, but the location and available proxy quality can differ by build.
- GPU preference. If the PC has more than one GPU, Windows exposes the app preference under Settings → System → Display → Graphics. Test High performance, save, restart CapCut and keep the setting only if the same crash stops.
Close screen recorders, game overlays, streaming tools and GPU monitoring utilities for one controlled test. If the crash stops, re-enable them one at a time until it returns. For a wider look at running the app on desktop, see the guide to CapCut for PC.
Desktop cache has conflicting official instructions. One current CapCut page tells users to reset render cache from Settings → Draft → Clear Cache with the trash icon beside cache size.
Another current CapCut page says Desktop has no in-app Clear Cache button and tells Windows users to delete the contents of %LocalAppData%\CapCut\. Yet current desktop builds can expose a cache-size trash control in the Draft tab. That broad Windows root can also contain User Data and projects, so this article doesn't recommend deleting the whole folder. The two CapCut pages conflict, and build differences don't prove that every installation stores data identically.
Use the in-app control if your build exposes it. Otherwise stop before a manual deletion unless the exact folder has been identified as temporary data and the project has been verified in Spaces. Never delete Projects, com.lveditor.draft, the whole User Data directory or the whole CapCut data root as a generic crash fix.
macOS: Update First, Then Separate Cache From Projects
On macOS, CapCut points users to System Settings → Software Update for graphics-related updates. Start there and update CapCut, then check storage and the export folder. If the failure repeats at the same timeline position, inspect the clip, effect, transition or audio element at that point before changing the whole installation.
For cache, CapCut currently points macOS users to ~/Library/Caches/com.lemon.lvoverseas/. Quit CapCut first and verify the project in Spaces before deleting anything by hand. Leave project locations alone. The separate guide to CapCut for Mac covers the app and permission setup.
When the Crashes Started After an Update
If crashes began immediately after an update, record the version before assuming the update is the cause. Restart the device, then test a blank project with two clips and no effects. Use only the safe cache control documented for the current platform and build. If the blank project survives and the real one doesn't, a project-specific media, effect or saved-state problem becomes more likely.
Don't install an unofficial old build to chase a regression. A project last saved by a newer version may not behave correctly in an older one, and an unverified installer adds security risk. Keep the draft synced, record the affected version and use CapCut's official support route while testing a blank project in the current build.
When the Failure Is Online, Not a Local Crash
Login, templates, stock media, Spaces and AI tools can fail upstream while local editing still works. Test more than one online feature on another network or device before changing local files. As of August 26, 2026, CapCut Help doesn't link to a public status dashboard. Treat third-party outage reports as signals and use the Help Center or an official CapCut channel for confirmation.
Install from an official store or capcut.com wherever CapCut is officially available in your region; CapCut's guide to install and compatibility failures lists the legitimate download paths. Unofficial or outdated packages can introduce security, compatibility and update problems, so rule them out early.
For symptoms that are not crashes, such as a black preview, a failed login or blank templates, see CapCut not working. If you're unsure which features your version should have at all, the full features guide covers what differs between mobile, desktop and web.
Send CapCut a Reproducible Crash Report
A reproducible report gives support something to compare. Collect this before you write:
- Device model and operating system version
- CapCut version number, from the settings screen
- The exact moment of failure: launch, import, playback or export
- The timeline timestamp, if it fails at the same point every run
- Project length, resolution and rough file size
- Source codec and frame rate
- Free storage on the drive or device
- Your UID and DID, which CapCut explains how to find
- Any crash report or error code, and whether it reproduces on a blank project
The blank-project result makes the report more useful. If two known-good clips also crash, report the app build, device, graphics path and operating system. If only one project fails, duplicate it and isolate its media, effects, fonts and saved state. Use the CapCut project recovery guide only if the crash has already left the draft missing or unreadable.
CapCut Crashing FAQ
Does clearing the cache delete my CapCut drafts?
The in-app Clear cache control should leave drafts intact because it targets temporary data, but verify important projects in Spaces first. Don't use Android's Clear storage or manually delete project folders on desktop unless the drafts are already backed up.
Will uninstalling CapCut delete my projects?
A full uninstall can remove local-only drafts, so treat it as destructive unless the project is already in Spaces. On iOS, Offload App is a separate and gentler operation that keeps documents and data. On desktop, uninstalling may leave the User Data folder behind, but don't rely on it. Upload to Spaces, confirm the project opens on another device, and keep your own source files before you remove anything.
Can a crash corrupt the project I was working on?
A crash by itself doesn't prove that the project is corrupt. A media file, effect or saved-state problem can produce the same repeatable failure. Keep the original untouched, duplicate the project if it opens, and isolate the failing timestamp in the copy. If no copy opens, contact support before rebuilding from the source media.
Does CapCut Pro crash less than the free version?
No CapCut documentation says the Pro subscription makes the editor more stable. Some paid AI or effect workflows add processing, but the subscription itself doesn't fix a codec, driver, storage or project-specific failure.
Is CapCut down, or is it just me?
Test more than one online feature on another network or device. If login, templates and Spaces fail together, look for current reports and ask CapCut support before changing local data. As checked on August 26, 2026, CapCut Help doesn't link to a public status dashboard. If local editing alone crashes while online services respond, a device, driver, media or project cause is more likely.
Why does CapCut crash on one project but not others?
If other projects stay stable, treat the failing project's media, effects, fonts, caption tracks and saved state as suspects. Halve the timeline repeatedly to identify the smallest failing section instead of rebuilding the whole edit.
Why does CapCut keep crashing on a Chromebook?
On ChromeOS, start with CapCut Online in an updated Chrome browser rather than trying to install the Windows or macOS desktop build. CapCut's official Chromebook guidance also lists the Google Play app on compatible Chromebooks. If the web editor crashes, protect the project, close other heavy tabs and extensions, test a short blank project, and check local storage and the network. Update or reinstall the Android app only after unsynced drafts are backed up.