Edge
Safari
Firefox
DuckDuckGoSaving and exporting fail together far more often than either fails alone, because both depend on the same three things: a valid session, somewhere to put the result, and enough GPU memory to finish the work. Isolating which one is at fault takes one test each.
If one or more of these match what you are seeing, you are on the right page.
Ordered from most to least likely. Work down the list — each cause is paired with what to do about it.
Sign out and back in. This is the fastest test: if Ctrl+S succeeds afterwards, the session was the cause and export will work too.
Check the storage percentage in the account indicator. Remove unused assets from the Asset Library first — embedded images dominate project size.
Export renders at full resolution regardless of preview quality. Reduce simultaneous blur, alpha mask and non-Normal blend mode usage, or export a short range first to confirm the composition is the limit.
Saves queue locally and resume automatically; exports do not. Restore connectivity, wait for the indicator to read Saved, then export.
If none of the causes above match, contact support with the steps to reproduce the problem, your browser and version, and any message from the browser console. You can reach us at support@flashfx.app.
Contact Support