Quick fix first. If an export fails, do this before anything else: force-close Edits, restart your phone, and free up storage so at least 2 GB is available. Then try the export again with nothing else running. Most failed exports clear at that point, because export is the moment Edits needs the most free storage and memory at once. If it still fails, the steps below work from the cheapest cause to the deepest one — and your project is almost certainly safe, because a failed export does not damage the timeline it came from.
An export that stops halfway is uniquely frustrating: the edit is done, the preview looks right, and the finished video simply will not come out. This guide covers the three shapes the failure takes — an export that stops partway, one that restarts endlessly, and one that ends with a failure message — and ranks the causes so you fix the likely one first instead of reinstalling the app and hoping.
Edits Guide is an independent, unofficial guide. We are not affiliated with, endorsed by, or connected to Meta Platforms, Inc. or Instagram. We do not invent error codes or official statements; where the honest answer is that the cause is on Instagram’s side, this guide says so and points you to the updates page.
The symptom, precisely
Watch where the export stops, because the stopping point is diagnostic. An export that fails at the same percentage every time is almost always choking on one specific clip or effect at that point in the timeline. An export that fails at random points points to storage or memory running out. An export that fails instantly, before any progress, points to a settings problem or a damaged project file. Note which pattern you see — it tells you which fix to try first.
Likely causes, ranked
- Not enough free storage. Export writes a large temporary file and then the finished video. A phone with little free space runs out mid-render, and the export dies. This is the most common cause by a wide margin.
- Memory pressure on a long or effect-heavy timeline. Many clips, stacked effects, and long durations push the phone’s memory to its limit during rendering, especially on older devices.
- A damaged or unusual clip. One corrupt file, or a clip in a format Edits handles poorly, can halt rendering at the same point every time.
- Export settings the phone cannot handle. The highest resolution and frame rate combination can exceed what an older phone can render, even when editing itself felt smooth.
- Corrupt cache or a bad app update. Damaged temporary files or a half-installed update can break rendering while the rest of the app works normally.
- A server-side problem. Uncommon for exports, which mostly happen on your phone, but a broken feature or account issue can block exports for many people at once — the pattern to watch for is identical failures reported widely at the same time.
Fixes in order, quickest first
Test an export after each step. Stop when one works — your project does not need the rest of the list.
1. Force-close Edits and restart your phone. This frees the memory and storage headroom an export needs, and it clears a stuck render session. Close other apps first, too: a game or browser holding memory in the background can be the difference between a finished export and a failed one.
2. Free up storage properly. Check free space in Settings and aim for at least 2 GB free — more for long videos. Move finished videos off the phone, clear downloads, and empty gallery trash. The storage guide covers this without risking your drafts. Remember that export needs room for both the temporary render and the final file, so “just barely enough” is not enough.
3. Lower the export settings for one test. In Edits, drop the export resolution or frame rate one notch — for example, from 4K to 1080p — and try again. If the lower setting exports, your phone was hitting its rendering limit, not a broken project. The export settings guide explains each setting, and a successful lower-resolution export is far better than no export at all.
4. Isolate the problem clip. If the export always stops at the same point, duplicate the project and delete the clip nearest that point in the timeline, then export the copy. If it succeeds, that clip is the culprit: replace it with a re-recorded or converted version. Work in halves on long timelines — export the first half, then the second — to find the bad section fast.
5. Simplify the timeline. Temporarily remove stacked effects, heavy transitions, and overlays from a copy of the project, then export. If it works, re-add effects a few at a time. Effects multiply rendering work, and one incompatible effect can halt an otherwise healthy export.
6. Update Edits and clear the cache. Install the latest version from the official store, then clear the cache (Android: Settings, Apps, Edits, Storage, Clear Cache; iPhone: offload and reinstall). This addresses damaged temporary files and half-installed updates without touching your projects.
7. Split the video and rejoin it. For very long projects on older phones, export in two or three sections and stitch the finished files together in a new project. It is a workaround, not a fix, but it reliably gets long videos out when a single render keeps failing.
8. Reinstall as a last resort. Export any finished work first, accept that on-device drafts may be lost, then uninstall, restart, and reinstall from the official store only. If a fresh install still cannot export a simple test project, the cause is your device or a server-side issue, and further reinstalls will not help.
When the export fails at the same point every time
A consistent stopping point is good news in disguise: it means the cause is local and findable. Convert the suspect clip to a standard format before importing it again, or replace it entirely. Also check for a clip that was recorded while the phone was nearly full or overheating — files written under those conditions are sometimes incomplete in ways that only show up at render time. If the stopping point sits on a transition or effect rather than a clip, remove that effect and re-export before blaming the footage.
How to tell when it is a rollout or a server problem
Exports mostly happen on your phone, so a server problem is a less likely cause here — but it is not impossible. The signature is the same as elsewhere: identical export failures reported by many creators at the same time, including on simple test projects that used to export fine. When you see that pattern, stop reinstalling and check the updates page, then wait for a corrected release. Reinstalling during such a window only risks your drafts, and it cannot fix a problem that lives on Instagram’s side.
Frequently asked questions
Will a failed export delete or damage my project?
No. A failed export leaves the timeline untouched — the project, its clips, and its edits all stay exactly as they were. That is why this guide has you work on duplicates when isolating a bad clip: the original is safe either way. What a failed export can cost you is time, and in rare cases a temporary render file left behind, which clearing the cache removes. If the project itself will not open, that is a different problem, covered in the crashing guide and the drafts guide.
My export fails at 99 percent every time. What does that mean?
A failure at the very end usually means storage ran out just as the final file was being written, or the last clip or effect in the timeline is the problem. Free up storage first — the final file plus its temporary render can need more room than the finished video’s size suggests. If storage is plentiful, test by exporting a copy with the final clip removed: if that succeeds, the last clip or its effect is the culprit, and replacing it fixes the export.
Why does a short video export fine but a long one fail?
Long videos multiply everything that can go wrong: more storage for the render, more memory during processing, and more chances that one clip in the timeline is damaged. This is also why a phone that edits smoothly can still fail at export — editing previews at reduced quality, while export renders every frame at full settings. Splitting the project into sections, as step seven describes, is the most reliable workaround for long videos on older phones, and lowering export settings helps when the limit is rendering power rather than storage.
Does my internet connection affect exports?
Almost never. Export renders on your phone, so a weak connection does not stop it. The exception is any step that needs Instagram’s servers — such as sharing directly to Instagram from inside Edits, or features that fetch audio or effects online. If the video exports to your camera roll fine but will not upload, the problem is the upload, not the export, and the upload-stuck guide covers that separately.
Should I reinstall Edits after one failed export?
No — not before trying the earlier steps. Reinstalling is slow, it risks your drafts, and it rarely fixes an export failure, because the common causes are storage, memory, settings, or a single clip. Reinstall only after storage is free, settings are lowered, the suspect clip is isolated, and the cache is cleared — and even then, export any finished work first. If a simple test project also fails after a fresh install, the cause is your device or a server-side problem, not your data.
Get Edits on Google Play Get Edits on the App Store
Next: Blurry Export → · All help guides →
If you worked through these steps and exports still fail, note the exact stopping point and whether a short test project exports — those two facts narrow the cause faster than anything else, and you can send them through the contact form so the guide can be improved.
Keeping exports reliable
Two habits prevent most repeat failures. First, keep storage headroom before you start editing, not just before you export: a project that grows past your free space will fail at the last step no matter how good the edit is. Second, export a rough draft early in a long project — a successful early export proves the timeline renders, and it gives you a fallback if a later clip breaks the render. Creators who do both almost never lose an evening to a failed export.