Quick answer: Edits keeps crashing most often because of a tired app session, a full phone, or a single damaged draft — not because the app is broken. Fully close Edits, restart your phone, and check free storage before you touch anything deeper. Work the fixes below in order, and stop as soon as Edits opens and stays open.
Edits crashing feels personal because it usually happens when you are about to work: you tap the icon, the splash screen appears, and the app vanishes. Or it opens, you tap a draft, and it closes again. The good news is that most crashes are boring. They come from a session that has been running too long, a phone that is out of breathing room, or a project file that the app chokes on. All three are fixable without losing your work, as long as you work in order and resist the urge to delete the app first.
The symptom, precisely
Crashes come in three shapes, and the shape points at the cause. If Edits closes the moment you tap it, before you see anything, the problem is usually the app session or the install itself. If Edits opens but closes when you tap a particular draft, the problem is usually that draft. If Edits crashes mid-edit, usually during a heavy effect or an export, the problem is usually memory or storage. Notice which shape yours takes before you start fixing, because the first three fixes differ by shape.
Likely causes, ranked
1. A tired app session. Edits has been running in the background for days, its memory is fragmented, and a fresh launch trips over old state. This is the most common cause of all, and the cheapest to fix.
2. Low storage or low memory. A phone with little free space cannot hold the temporary files Edits needs while editing, and a phone with many apps open cannot hold Edits in memory alongside them. Crashes during exports and heavy effects point here.
3. One damaged draft or clip. A single project that closes the app every time you open it is almost never a coincidence. Something in that project — a clip, an effect, or a corrupted save — is what the app trips over.
4. A bad update or a staged rollout problem. A new version can introduce a crash on some devices, and a half-applied update can leave the app in a broken state. This is less common than the first three, but it clusters: if crashes started the day you updated, suspect this.
5. An emulator or device limitation. In an emulator, Edits runs through a compatibility layer, and crashes cluster around heavy effects and exports. On older phones, the same effects can simply exceed what the hardware can hold. Neither is a bug you can fix in settings.
Fixes, quickest first
Fix 1: Fully close Edits and reopen it. Swipe Edits out of your recent-apps list so it stops completely, then tap the icon again. This is not the same as switching away and back; the app must actually stop. If it opens and stays open, you are done.
Fix 2: Restart your phone. A restart clears the memory and session state that a mere app close leaves behind. It is the single most effective crash fix, and it costs two minutes. Open Edits again after the restart and try the same action that crashed it.
Fix 3: Free up storage and close other apps. Check how much free space your phone has, and clear downloads, old videos, and app caches you do not need until you have comfortable breathing room. Close other apps before opening Edits, especially camera and video apps. Then try again.
Fix 4: Open a different draft. If Edits opens but crashes on one project, the project is the suspect. Open a different draft or start a new one. If other projects work, leave the damaged one alone for now — the drafts guide explains what can still be recovered — and keep editing on the healthy projects.
Fix 5: Update Edits, or wait out a bad update. Open your store listing and check for an update; a crash that arrived with a version often leaves with the next one. If crashes started the day you updated and no newer version exists, check our updates page and give it a day before trying anything deeper — a hotfix often follows quickly.
Fix 6: Clear the app cache. In your phone settings, clear Edits’ cached data (not its stored data — clearing stored data can remove drafts). Cache clearing removes the temporary files that a tired session leaves behind, and it is safe to repeat. Reopen Edits and test the same action.
Fix 7: Remove the suspect clip or effect. If one project always crashes, open it if you can and remove the most recent clip, effect, or transition you added, then save a copy under a new name. If the project will not open at all, leave it and work from your last export or a duplicate — the drafts guide covers recovery options in detail.
Fix 8: Reinstall Edits, last. Only now, after the seven fixes above, delete and reinstall Edits from the official store listing. Understand what this costs: drafts stored only on the device may not survive, so export anything you can first. Reinstalling fixes a corrupted install, and nothing else on this list does — which is exactly why it sits last.
Crashes in an emulator or desktop workflow
Emulator crashes deserve their own note, because they follow a different pattern. In an emulator, Edits shares the computer’s memory with the emulator itself, and heavy effects, long timelines, and exports push that shared memory hardest. If crashes cluster around effects and exports while simple cuts work fine, the emulator’s memory allocation is the likeliest cause: give the emulator more RAM in its settings, close other computer programs, and keep timelines shorter while you test. Our PC routes guide explains the emulator trade-offs in full. If crashes persist even after more memory, edit on the phone for heavy projects and use the computer only for review — that split is the honest desktop workflow for crash-prone setups.
When it is a rollout or server issue
A crash wave that starts suddenly, affects a feature rather than a file, and survives every fix above is usually a bad build or a server-side problem, not your phone. The tell is clustering: friends with the same version crash in the same place, and no local fix changes anything. In that case the genuine fix is checking our updates page for a known issue and waiting for the next build. We do not invent error codes or Meta statements here, and we do not dress up waiting as a technical fix — but when the cause is server-side, waiting is the fix, and repeating local fixes only wastes your evening.
Mistakes to avoid
The biggest mistake is reinstalling first. It feels decisive, but it destroys drafts that a restart would have saved, and it rarely fixes the actual cause. The second mistake is clearing stored data instead of cached data — the two sound alike in phone settings and do very different things. The third is chasing a single crash with ten fixes at once: change one thing, test, and only then move on, or you will never know which fix worked.
Frequently asked questions
Why does Edits keep crashing on launch?
Usually a tired session or a corrupted install state. Fully close the app, restart the phone, and only then consider deeper fixes.
Does Edits crashing mean my phone is too old?
Not necessarily. Most crashes are session, storage, or draft problems. Age matters only when crashes cluster around heavy effects on an older device.
Will reinstalling Edits delete my drafts?
Drafts stored only on the device may not survive a reinstall. Export what you can first, and treat reinstalling as the last fix.
Why does Edits crash only in the emulator?
Emulators share memory with the host computer, so heavy effects and exports crash more often. Give the emulator more RAM and shorten timelines while testing.
Can a single project crash Edits?
Yes. If Edits opens fine but closes on one draft, that draft is the suspect. Open a different project to confirm, then work from a copy.
What if nothing here fixes the crash?
Check our updates page for a known bad build or server issue, and wait for the next version rather than repeating fixes.
More help: browse every problem in our help hub, or check what changed in the latest Edits update.
Download Edits on the App Store
Unofficial guide: this page is not published by Instagram or Meta. The store buttons above link to the official Edits listings.
Reading the crash pattern before you fix anything
Crashes leave a pattern, and reading it before fixing saves you from the most common waste of time in troubleshooting: fixing the wrong thing thoroughly. Ask three questions about your crash. First, does it happen on launch, on one draft, or during one action? Launch crashes point at the session or the install; single-draft crashes point at that project; action crashes point at memory, storage, or the effect itself. Second, did it start after an update, a phone change, or nothing at all? Update-linked crashes point at the build; nothing-at-all crashes point at storage or session drift. Third, does it happen in the emulator, on the phone, or both? Emulator-only crashes point at the emulator’s memory; both-platform crashes point at the project or the build.
Write the answers down before you start. Not because anyone will ask for them, but because fixing without a pattern means trying fixes at random, and random fixing is how a ten-minute restart turns into an afternoon of reinstalls. The pattern also tells you when to stop: if every fix fails and the pattern says “started with the update, affects everyone on this version,” you have your answer, and it is on the updates page, not in your phone settings.
Preventing the next crash
Once Edits is stable again, a few habits keep it that way. Restart your phone at least once a week; a phone that never restarts accumulates exactly the session state that causes launch crashes. Keep comfortable free storage — not just enough for one export, but enough that the phone never has to choose between Edits’ temporary files and its own breathing room. Close Edits fully when you finish a session instead of leaving it parked in the background for days, especially before a heavy edit. And duplicate a project before you add a risky effect or a long chain of transitions, so a crash on one version never costs you the whole edit. None of these habits is exciting, and together they prevent more crashes than any single fix on this page.