Two features that solve unrelated problems
Archive and Locked Folder sit next to each other in Google Photos and are frequently confused, but only one of them is an access-control feature.
Archive is organisation: it removes an item from the main grid so the view is less cluttered. Locked Folder is authentication: it puts an item behind your device or account credential. Choosing between them starts with deciding whether your problem is clutter or unauthorised viewing.
What Archive actually does
Archiving moves an item out of the primary Photos view. Google's documentation is explicit that archived items can still appear in albums, in search results, and in device folders.
That makes Archive genuinely useful for tidying a timeline and completely unsuitable as a privacy control. Anyone who searches, opens an album, or browses the device's file system may encounter an archived item without ever needing to defeat anything.
What Locked Folder adds, and what it borrows
Locked Folder is a real boundary: items inside it are kept out of the main grid, search, memories, and ordinary sharing flows, and opening it requires authentication.
The authority it uses, however, is borrowed. Access is tied to your device screen lock or Google Account authentication rather than an independent per-folder secret. Someone with an accepted device or account credential may be able to open the folder; merely holding an already unlocked device is a different situation and depends on the current authentication policy.
The backup question to settle first
Locked Folder's backup behaviour has changed over time and depends on your settings. Before moving anything irreplaceable, confirm whether Locked Folder backup is enabled on your account.
This is a concrete recovery risk. Moving an item into a folder that is not backed up, then losing or resetting the device, can leave no recoverable copy.
Move one test item and follow it
- Decide first whether you are solving clutter or unauthorised viewing.
- Confirm whether Locked Folder backup is enabled before moving anything you cannot replace.
- Move a single non-sensitive test item and verify where it disappears from — and where it still appears.
- Check edited versions, previously shared copies, Trash, and device folders as separate locations.
- Only then move the content you actually care about.
Mistakes that follow from the confusion
- Treating Archive as a lock because the item vanished from the timeline.
- Assuming every duplicate and edited version follows the original.
- Factory-resetting a phone before confirming Locked Folder backup was on.
- Expecting a shared link to stop working because the source item was moved.
When neither is the right tool
Both features remain inside Google Photos, under your device or account authority. If you need a boundary that does not share the phone's unlock credential, or separate spaces that do not reveal each other, that is a different category of tool.
That is the trade a separate encrypted vault makes: an independent credential and encrypted storage, in exchange for managing your own recovery and backup rather than inheriting Google's.
A fictional example
Amara starts with a non-sensitive test: “Decide whether the problem is clutter or unauthorized viewing.” Next, Amara follows the second check: “Check whether Locked Folder backup is enabled before moving irreplaceable media.” This fictional scenario demonstrates the decision process; it is not a report of product testing.
Common mistakes
- Treating Archive as a lock
- Assuming every duplicate moves with the original
- Factory-resetting before confirming Locked Folder backup
What this workflow does not change
- Treating Archive as a lock
- Assuming every duplicate moves with the original
- Factory-resetting before confirming Locked Folder backup
Questions people ask
Can archived photos still appear in search?
Yes. Google says archived items can remain in albums, search results, and device folders.
Does Locked Folder use a separate secret?
Its current unlock authority is tied to device or Google Account authentication, not an independent NullVault pattern.