If CapCut keeps crashing, the useful question is not why apps crash in general. It is when yours dies. An app that closes before your projects load has a different cause than one that survives an hour of editing and quits at 94 percent of an export. Most guides ignore that and hand you the same seven steps in the same order.
Those lists also share a habit that costs people work: they put "uninstall and reinstall" at step three or four. On mobile, local-only CapCut drafts may depend on the app's stored data, so clearing storage or deleting the app can remove them.
Quick answer: back the project up to CapCut Spaces and confirm it opens on a second device, note the exact moment CapCut fails, then work through the fixes for that moment only. The in-app Clear cache control should leave projects intact, but verify critical drafts in Spaces before any cleanup. Common areas to test include damaged temporary data, incompatible or corrupted media, memory or heat pressure in heavy projects, and desktop graphics or driver conflicts.
For everything else that goes wrong in the app, start from the CapCut fixes hub.
Before You Fix CapCut Crashing, Protect the Project
Two pieces of common advice destroy work. On Android, "clear the app data" is a different instruction from "clear the cache." Clear cache removes temporary app data and should leave projects intact. Clear storage or Clear data resets the app and can permanently remove local-only drafts. Uninstalling carries the same risk on both platforms. CapCut's own guidance is blunt about it: clear the cache from Profile then Settings, and never clear App Data in system settings, because that permanently deletes local projects.
Do this before you change anything:
- Upload the project to CapCut Spaces, then confirm it opens from another device. Do not 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. Original video, images, audio and any custom fonts. A project folder can hold timeline data without holding the media it points at, so a folder copy on its own can restore an edit that opens to missing clips.
- Export a flat copy if the project still opens. Even a rough 1080p render of an unfinished edit gives you something to rebuild from.
On desktop you can also copy the project folder, but check Settings then Save to, or the Details panel of an open project, before you trust any path you read online. Locations move between builds. Commonly reported locations are %LocalAppData%\CapCut\User Data\Projects\com.lveditor.draft\ on Windows and ~/Movies/CapCut/User Data/Projects/com.lveditor.draft/ on macOS.
On Android, do not 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.
CapCut Crash or Freeze? Tell Them Apart First
These get treated as one problem and they are not. A crash closes the app: you land back on your home screen or desktop with no window, which is what people usually mean when they say the CapCut app keeps closing. A freeze leaves the window on screen and unresponsive, and you have to end it through Task Manager or Force Quit.
The distinction changes what you do next. A desktop or web export sitting at 99 percent may have finished rendering and become blocked while writing or saving the final file. CapCut lists this as a common cause of a stuck export. Give it a few minutes, then check whether antivirus software or disk permissions on the destination folder are blocking the write.
Why CapCut Keeps Crashing: Diagnose by the Moment It Fails
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 | Corrupted cache, outdated build, graphics driver conflict on desktop | Update, then clear cache |
| 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 does not 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, encoder settings, destination folder | Lower resolution, 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 |
CapCut Crashes Immediately at Launch
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. Update before you touch anything else. Older builds may contain known stability bugs or become incompatible with current backend services.
If it still dies before the project list appears, clear the cache using the platform steps below, then restart the device. If CapCut closes only when the local project library appears, test whether one local project or thumbnail is triggering the crash. Signing in on another device and opening the project from Spaces helps distinguish a local app or project-library problem from an account or cloud issue.
CapCut Crashes When Importing Media
Two different failures hide under this heading, and they need different fixes.
If CapCut dies the instant the import window opens, the app is handing off to the operating system's file picker. Try dragging files from Explorer or Finder straight onto the timeline instead. Treat that as a temporary workaround rather than proof that the media or CapCut itself is the root cause, since a failure in the system file picker can affect more than one application. Check that CapCut has photo and media permissions, and point the picker at a small folder rather than a drive holding thousands of files.
If CapCut closes after a file is added, test media compatibility. CapCut states plainly that a familiar extension does not guarantee support: a file labelled MP4 or JPG can hold an underlying format the app cannot read, and renaming an extension changes nothing. Play each clip outside CapCut first, then add clips one at a time to find the offender. Re-encoding the suspect file to constant frame rate H.264 and importing the copy is a fast diagnostic test: if the copy imports cleanly, the original file, container or encoding is implicated. A recent r/CapCut discussion about crashes when the Windows import dialog opens reports drag and drop as a temporary workaround, although it does not identify the underlying system cause.
CapCut Crashes While Editing or Scrubbing
Treat memory pressure and project complexity as the first suspects, especially if a blank project stays stable. Turn on proxy so the timeline runs on lightweight copies while the originals return at export, drop the preview quality dropdown from Original to performance mode, and close background apps competing for RAM, GPU resources or storage bandwidth.
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.
CapCut Crashes During Export
Export failures have their own causes and their own guide. The short version: CapCut asks for at least 2 to 3 GB free on the export drive on desktop and more than 1 GB on mobile, quoted there in the context of template exports. Treat those as a floor rather than a guarantee, because the real requirement climbs with length, resolution and effect count.
Beyond storage, drop 4K to 1080p and 60fps to 30fps, send the file to a local export folder rather than a OneDrive or iCloud folder, and switch off battery saver on mobile. Our guide to CapCut export settings covers which combinations are worth keeping. For stalled progress bars, error codes and audio that survives the edit but not the render, see CapCut export stuck.
If CapCut edits normally and only fails at export, test export settings, storage, the destination folder and individual timeline elements before you reinstall anything.
CapCut Crashing 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 does not 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, use Settings, General, iPhone Storage, CapCut, Offload App. Apple confirms offloading keeps an app's documents and data while deleting removes both. CapCut's own guidance pairs offloading with the note that projects remain if they are synced to the cloud, so upload first.
CapCut Crashing 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.
- Battery optimisation can restrict a long render or a heavy editing session. Temporarily exempt CapCut from optimisation and repeat the same test.
- Check photo and media permissions if imports fail.
- Free several gigabytes. Moving finished exports off the device helps more than deleting apps.
CapCut Crashing on Windows 10 and Windows 11
Update the GPU driver from NVIDIA, AMD or Intel directly rather than through Windows Update. In one Microsoft Q&A case, an independent advisor read the submitted crash data as a DirectX or graphics driver problem rather than a fault in CapCut itself. That is one case, not a rule, but drivers are cheap to rule out and CapCut's own troubleshooting names outdated drivers as a cause of rendering freezes.
Then work through Menu, Settings, Performance:
- Hardware acceleration. Advice online splits cleanly in two. Some guides say switch hardware decoding and encoding on to stop stuttering, others say switch it off to stop freezing. Both recommendations appear because hardware acceleration can expose driver, codec or GPU compatibility problems, while disabling it may increase CPU load. Toggle it, restart CapCut fully, and test each state for a few minutes.
- Proxy. Enable Proxy at 540p or 720p if those options are available in your build. In some builds this sits in Project Settings rather than global settings.
- Dedicated GPU. In Windows, open Settings, System, Display, Graphics, find CapCut and set High performance.
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, and a contradiction worth knowing about. CapCut's current help pages describe two different desktop cache workflows. One page tells you to reset the render cache from Settings, Draft, Clear Cache, using the trash icon beside the cache size. Another states that CapCut Desktop has no in-app Clear Cache button and instructs deleting the contents of %LocalAppData%\CapCut\. That suggests the control varies by build, and the second instruction is the risky one, because User Data and your projects sit inside that same folder. Use an in-app Clear Cache control if your version has one. Otherwise close CapCut and remove only a folder explicitly identified as cache. Never delete Projects, com.lveditor.draft, or the entire User Data directory. Autosaves are not disposable cache.
CapCut Crashing on macOS
On macOS, GPU drivers are delivered through system updates rather than separate NVIDIA, AMD or Intel installers, and CapCut points Mac users at System Settings then Software Update. Start there and with the CapCut build, then look at storage and disk permissions. Heat can reduce performance during long renders, so let the Mac cool before repeating a test. If CapCut fails at the same timeline position every time, inspect the clip, effect, transition or audio element around that point before treating heat as the primary cause.
For cache, CapCut points macOS users at ~/Library/Caches/com.lemon.lvoverseas/. That directory is separate from projects under ~/Movies/CapCut/, so clearing it is the safer of the two operations. Quit CapCut first, and verify the project is in Spaces before deleting anything by hand. More on the desktop app in the guide to CapCut for Mac.
CapCut Started Crashing After an Update
A new build can introduce a regression or interact badly with temporary data left by the previous version. Clear the cache first, then test a blank project with two clips and no effects. If the blank project survives and your real one does not, a project-specific media, effect or saved-state problem becomes more likely.
Rolling back can create project-compatibility and security problems, especially if the project was last saved by a newer build, so weigh that against however long the patch takes. Back the project up to Spaces either way.
CapCut Crashing From Server, Account or Regional Causes
Login, templates, stock media and AI tools depend on CapCut's servers, so those can fail while local editing works. If several online features fail across multiple devices or networks, check for a current CapCut service incident before changing local settings. If those features work, a device-specific or project-specific cause becomes more likely, though that does not rule out a partial outage.
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 are unsure which features your version should have at all, the full features guide covers what differs between mobile, desktop and web.
What to Send CapCut Support About Crashing
Support requests without detail get generic replies. 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
That last item is especially useful. If a two-clip blank project also crashes, the problem is probably app-level, device-level, driver-level or operating-system-level rather than tied to one timeline. If only one project crashes, a media file, effect, font or project corruption becomes more likely.
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. Do not 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 do not 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?
Possibly, although a damaged media file or effect can produce the same symptoms without the project itself being harmed. If a project opens to a black timeline or refuses to open at all, rebuild it in a new file from your source media rather than continuing to open the suspect one.
Does CapCut Pro crash less than the free version?
There is no evidence that a Pro subscription by itself improves crash stability. Pro unlocks heavier features, and using those on weak hardware makes crashes more likely rather than less.
Is CapCut down, or is it just me?
Test more than one thing. If you can log in, browse templates and generate auto-captions, those tested services are responding and a local cause is more likely. If several online features fail on more than one device and network, check for a current service incident before changing settings.
Why does CapCut crash on one project but not others?
A single media file, effect, font, caption track or damaged project state is a common cause when every other project stays stable. Halve the timeline repeatedly to isolate it rather than rebuilding the whole edit.