Edge
Safari
Firefox
DuckDuckGoUndo is Ctrl+Z and redo is Ctrl+Y. When undo stops short of where you expect, the usual reason is that Undo History Depth has been capped — it defaults to unlimited, but a numeric cap silently discards the oldest steps once it is reached.
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.
Open Edit → Preferences (Ctrl+,) and check Undo History Depth under General. The default is unlimited; a cap trades history for lower memory use on long sessions.
Performing any new edit after an undo discards the redo branch. This is expected behaviour — there is one linear history, not a tree.
Undo history is session state and does not survive a reload. The project itself is preserved by sync; the history is not.
While editing a text element or a numeric field, Ctrl+Z applies to that field. Press Escape to deselect first, then undo.
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