Illustrative stock photograph; not a Meluvya result or a test of the technique. Photo by Leticia Curvelo / Pexels.
The quick answer
Keep the original capture, an editable working version when supported, and a separate delivery export. Before committing to an unfamiliar editor, test whether you can reopen and revise an edit. Undo history, a revert command, and an independent backup are different protections; do not assume one provides all three.
Give each version a clear job
An original is the starting capture. A working file stores whatever adjustments the editor supports. An export is the image prepared for someone to view or use elsewhere. Keeping these roles separate prevents a social-media copy from quietly becoming your only source.
Adobe's nondestructive-editing guidance describes approaches such as editable adjustments that preserve source pixels. The exact capabilities vary across applications, so verify the tool you use instead of relying on a generic promise of reversibility.
A simple file arrangement
Version
Example name
Purpose
Original
cafe-portrait-original
Untouched source to return to.
Working edit
cafe-portrait-edit
Supported editable settings or layers.
Delivery
cafe-portrait-share
Final crop and size for a particular use.
Test reversibility on an unimportant copy
Make one obvious adjustment. Apply a visible crop or brightness change so it is easy to tell which state you are viewing.
Save and close. Reopen the image or project. Check whether the adjustment can still be changed rather than merely applied again.
Try the documented revert process. Confirm what it restores and whether it removes all edits. Do not experiment on the only version of a photo you care about.
Export separately. Open the export outside the editor and confirm it has the intended appearance. Keep the working version for future revisions.
Do not confuse synchronization with a backup
Apple documents that edits in an iCloud Photos library can appear across devices. That is useful synchronization, but another device showing the same library is not necessarily an independent untouched copy.
If you need a separate original, preserve it deliberately using your storage or backup workflow. Also check what happens when deleting an image or reverting an edit. A backup is useful only if it contains the version you need and you know how to retrieve it.
Before a large edit session, confirm the location of one original and one working file. That small check is easier than reconstructing a folder full of ambiguous exports later.
Common questions
Is duplicate the same as backup?
Not necessarily. A duplicate in the same synchronized or vulnerable location can be affected by the same deletion or storage problem.
Will undo still work after reopening?
It depends on the application and file type. Test it rather than assuming an editing session's history is permanent.
Can I remove a filter from an exported image?
Not reliably if it was flattened into the pixels. An original or editable working file is the better starting point.