You finish a clean little edit, everything looks right, you hit back… and Alight Motion just refuses to save the project.
Or worse. It looks like it saved, but when you reopen the app, the project is missing, stuck on a loading spinner, or it opens like a blank timeline with nothing in it.
If you’re here, you probably already did the classic stuff. Close the app. Restart your phone. Try again. Still broken.
So let’s do this properly.
This is the exact 10 minute checklist I use when Alight Motion projects won’t save. Start at Step 1 and stop as soon as it works. No need to do everything.
Note: I’m assuming you’re talking about project saving inside Alight Motion (not exporting a video). I’ll cover exporting issues too, but later.
Quick signs you’re dealing with a real saving issue
You’re probably in the right place if any of these are happening:
- You tap back and it doesn’t ask to save, or it loops.
- The project thumbnail shows but won’t open.
- The project opens but changes didn’t stick.
- It says something like “Couldn’t save project” or just silently fails.
- Alight Motion crashes right after you add effects, fonts, or big files.
Ok. Let’s fix it.
If you want to know about Alight Motion Completly Visit Home Page
The 10 minute fix, in order
Step 1 (1 minute): Check storage space, but check it for real
Alight Motion can fail to save even if you have “a few GB free” because:
- your phone needs extra space for temporary files
- Alight Motion caches previews and renders
- the project may have huge linked media
Do this:
Android
- Settings → Storage
- Make sure you have at least 2 to 4 GB free (more if your project is heavy)
- Empty trash in your file manager and Google Photos if needed
iPhone
- Settings → General → iPhone Storage
- Aim for 3 GB+ free minimum
If you were near full, free space, reopen Alight Motion, open the project, make a tiny change (like move a layer 1 frame), and try saving again.
Step 2 (1 minute): Force close Alight Motion the right way
Not just swipe it away and hope.
Android
- Open Recent Apps and swipe Alight Motion away.
- Then go to Settings → Apps → Alight Motion → Force stop.
iPhone
- Open the app switcher by swiping up, then swipe Alight Motion away.
Now reopen and try saving.
If it still won’t save, keep going.
Step 3 (2 minutes): Disable Battery Saver and background restrictions
This one is sneaky. Saving is a write operation and some phones throttle or kill apps in the background, especially if your project is heavy.
Android
- Turn off Battery Saver or Power Saving mode.
- Go to Settings → Apps → Alight Motion → Battery and set it to Unrestricted (or “Don’t optimize” depending on your phone).
iPhone
- Turn off Low Power Mode via Settings → Battery.
Try saving again.
Step 4 (2 minutes): Clear cache (not data) on Android
If you’re on Android, cache corruption is a common reason projects act weird.
- Go to Settings → Apps → Alight Motion → Storage.
- Tap Clear cache.
- Reopen the app, open your project, and try saving.
Do not clear data yet. That’s more nuclear.
If you’re on iPhone, skip this step and move on.
Step 5 (2 minutes): Duplicate the project (this often bypasses the saving bug)
If the project file is partially corrupted, Alight Motion sometimes can’t write new changes to it. Duplicating forces a clean new project record.
- Go to your projects list.
- Tap the project menu (often three dots).
- Tap Duplicate.
- Open the duplicate.
- Make a small change and back out to trigger a save.
If the duplicate saves fine, you’re basically done. Just keep working from the duplicate.
Step 6 (2 minutes): Remove the “problem layer” that’s breaking saves
If it stops saving right after you added something, it’s usually one of these:
- a high resolution PNG (especially huge 4K+ transparent images)
- a corrupt MP3
- a weird font file
- heavy effects stacked too deep (blur + glow + distortion + motion blur everywhere)
- imported XML or preset that isn’t compatible
Here’s how to isolate it fast:
- Open the project
- Turn off visibility for half the layers (eye icon)
- Try saving
- If it saves, the issue is in the hidden half. If it doesn’t, the issue is in the visible half.
- Keep halving until you find the layer causing it
Once you find it:
- delete the layer, save, then re import a cleaner version of the file
- or replace it with a smaller resolution copy
This is boring, yeah. But it’s effective.
If that didn’t work, do these next (still usually under 10 minutes total)
Fix 7: Update Alight Motion (or roll back if the bug started after an update)
Sometimes the app version is the issue, not your project.
- Go to Play Store / App Store and update Alight Motion
- Restart phone
- Try again
If the saving issue started right after updating, you can also try:
- waiting for the next patch
- or on Android only, installing a previous stable version from a reputable source (be careful with random APK sites)
Fix 8: Sign in and sync, or turn sync off and on
If you use Alight Motion’s account features and cloud sync, a sync loop can interfere with saving.
Try:
- Ensure you’re logged in (or log out and back in)
- Check if your internet connection is stable
- Toggle Wi Fi off and on
- Reopen Alight Motion and try saving
Also, if the app is failing while online, try saving offline (Airplane mode) just to see if it’s a sync problem.
Not a permanent fix, but a good clue.
Fix 9: Export your work before you do anything drastic
If your project is unstable, you want a backup right now, even if you can’t fully fix saving yet.
Try:
- Export as MP4 (even low quality) just to capture the edit
- Export individual elements if needed (like transparent PNG sequence if that’s your workflow)
Sometimes export works even when project saving is flaky.
Fix 10: Last resort, clear data (Android) or reinstall (iPhone and Android)
This is where people accidentally lose stuff, so slow down for a second.
Before anything:
- If you can, duplicate projects
- Export what you can
- If you have cloud sync, let it finish
Android
- Settings → Apps → Alight Motion → Storage → Clear data
- Or uninstall/reinstall
iPhone
- Uninstall Alight Motion → reinstall
Important: Depending on how you use Alight Motion, uninstalling can remove local projects. If your projects are not synced, they may be gone. So only do this after you’ve tried the safer steps.
Common reasons Alight Motion projects stop saving (so you can avoid it)
This part is not mandatory, but it’ll save you headaches later.
1. You’re editing with almost no free storage
Even if the app “runs,” saving needs room. Especially with cached previews.
2. Your project is too heavy for your device
Some edits are basically asking a mid range phone to do laptop work.
Signs:
- timeline lags
- crashes when you scrub
- saving takes forever
- audio desync
Quick ways to lighten:
- pre render complex sections (export and re import)
- reduce resolution of assets (don’t use 8000×8000 PNGs)
- avoid stacking multiple heavy blurs
- keep motion blur limited
3. Fonts and imported files can break things
If you imported a font from somewhere sketchy, it can glitch the app.
Try removing the font usage and switching to a default font. Then save.
4. Corrupted media
A single broken MP3 can poison the project. Same with screen recordings that have variable frame rate or weird audio encoding.
Fix:
- re export the audio as a clean MP3 or AAC
- re encode video using a converter (HandBrake is great on desktop)
- avoid VFR screen recordings when possible
“My project disappeared.” What now?
Ok, different problem, but related.
First, check if it’s actually filtered or not loading
- Scroll down. Sounds dumb, but project lists sometimes don’t refresh at the top.
- Search if Alight Motion has a search option in your version.
- Close and reopen.
Check if it’s stuck on a loading screen
If it shows a thumbnail but won’t open, try the following steps:
- Duplicate the project if possible, then open the duplicate
- Try opening the project with airplane mode on
- Clear the app cache (Android)
If you reinstalled and lost projects
If you weren’t synced, recovery is hit or miss. On Android, you can sometimes recover if the app data folder still exists, you have a file backup, or your phone didn’t wipe everything. But realistically, if you uninstall and your projects were only stored locally, they may be gone. That’s why exporting and duplicating early is so important.
“It saves, but it doesn’t save my latest changes.”
That usually means the save fails silently at some point and the app reopens the last stable version.
Try this workflow:
- Make your changes
- Wait 10 seconds
- Back out to the project list and watch if the thumbnail updates
- Force close the app
- Reopen and check
If it still reverts, identify the layer that triggers the issue using the halving method, then duplicate the project and continue working in the duplicate.
A simple way to prevent this next time (realistic, not perfect)
Here’s a low effort routine for working on bigger Alight Motion edits:
- Keep 5 GB free storage before starting
- Duplicate the project at major milestones, for example: “Edit v1”, “Edit v2 effects”, and “Edit v3 final”
- Export a low quality draft occasionally as a safety capture
- If you add a new font, preset, or large asset, save immediately after to confirm nothing breaks
It’s not glamorous. It works.
What to do if nothing works (and you need the project today)
If you tried everything and it still won’t save, do this:
- Open the project and screen record your timeline playback as a reference (if export fails).
- Export in lower settings first.
- Rebuild the project in a new file using the same assets and any pre-rendered clips from the broken project (if export works even once).
Also, send a bug report to Alight Motion support. Include the following details:
- Your device model
- Android or iOS version
- Alight Motion version
- A screen recording of the save failure
- Whether the issue happens on new projects or only that specific one
You’re not wasting time doing that. If it’s a version specific bug, they actually need those details.
Images you can add (optional but useful inside WordPress)
If you’re publishing this as a tutorial post, these images make the steps easier to follow. Replace with your own screenshots or use placeholders.
1) Storage settings screen
2) Android App info page for Alight Motion
3) Clear cache screen (Android)
4) Project menu showing Duplicate option
Wrap up
If Alight Motion isn’t saving your project, it’s almost always one of three things: storage, battery/background restrictions, or a specific layer/media file corrupting the save.
Do the quick checklist in order:
- Free up storage
- Force stop and reopen
- Turn off battery saver and restrictions
- Clear cache (Android)
- Duplicate the project
- Isolate the problem layer
That usually fixes it in under 10 minutes, honestly.
If you tell me your phone model, Android/iOS version, and what happens when you try to save (error message or just nothing), I can narrow it down even faster.
FAQs (Frequently Asked Questions)
Why won’t Alight Motion save my project after editing?
Alight Motion may fail to save your project due to insufficient storage space, app cache corruption, background restrictions like Battery Saver modes, or problematic layers such as high-resolution images or corrupt media files. It might also be caused by app version bugs or sync issues.
How much free storage do I need for Alight Motion to save projects properly?
Ensure you have at least 2 to 4 GB of free storage on Android devices and a minimum of 3 GB free on iPhones. This extra space accommodates temporary files, cached previews, renders, and large linked media within your project.
What is the recommended way to force close Alight Motion before retrying to save?
On Android, swipe Alight Motion away from Recent Apps and then go to Settings → Apps → Alight Motion → Force Stop. On iPhone, open the app switcher by swiping up and swipe Alight Motion away. Then reopen the app and try saving again.
How can I identify and fix a ‘problem layer’ that’s causing saving issues in Alight Motion?
Use a visibility-halving method: open your project, turn off visibility for half the layers, and attempt saving. If it saves, the issue lies in the hidden half; if not, it’s in the visible half. Repeat halving until you isolate the problematic layer—often a huge PNG, corrupt MP3, weird font file, or heavy stacked effects—and then delete or replace it with a cleaner version.
What should I do if clearing cache and disabling battery saver don’t fix my saving issue in Alight Motion?
Try duplicating your project from the projects list menu and work on the duplicate; this often bypasses saving bugs caused by partial file corruption. Additionally, update Alight Motion to the latest version or roll back if issues started after an update. Also consider toggling cloud sync off and on if you use account features.
Is there a quick checklist to follow when Alight Motion won’t save my project?
Yes! Start by checking your device’s free storage (2-4 GB minimum), then force close the app properly, disable Battery Saver or Low Power Mode, clear cache (Android only), duplicate your project to bypass corrupted files, isolate any problem layers causing issues, update or roll back Alight Motion versions if needed, and manage cloud sync settings accordingly.



