Hide or delete uploads
Hiding pulls a contribution out of the shared album and saves it for you. It gathers in its own area and can be restored at anytime.
Removing removes the file. That can't be undone, and it's the right answer only when somebody really asked for it.
What hiding does
A hidden contribution goes away for your guests and remains yours. It shifts into its own area where everything you have hidden gathers, ready to be restored. Nothing about the file changes, and it keeps occupying the storage it always did.
That makes it the low-risk tool. Hiding something you were unsure about takes one click to undo.
- Open the album. The contribution and both actions sit on the same screen.
- Hide by default. For anything blurred, duplicated or just dull, hiding is enough and costs nothing.
- Delete only on request. When a guest requests to withdraw something, hiding isn't what they meant.
What deleting does
Removing removes the contribution permanently. There's no restore, no recycle area, and no copy kept for you. The dashboard requests you to confirm, and that confirmation is the final chance anybody gets.
Removing frees up the storage it used, which counts when an album is close to its ceiling.
| Hide | Delete | |
|---|---|---|
| Guests see it | No | No |
| You still have it | Yes | No |
| Can be undone | Yes | No |
| Frees storage | No | Yes |
| Right for a withdrawal request | No | Yes |
If you're unsure which you want, hide it. That decision keeps both choices open; removing closes one.
The morning-after walk-through
Walk through the album on the day after, when the late arrivals are in. Hide what's blurred, what's the third near-the same shot of the same table, and what's a photo of somebody s shoe. That's a 10-minute pass and it's what turns a pile into an album.
Resist removing mid-party. Nothing in that list needs to vanish for good, and tomorrow you may disagree with yourself.
When a guest asks to withdraw something
Guests can't remove their own contributions — without an account there's no private space for it, so the request comes to you. When it does, remove instead of hide. Hiding leaves the file with you, which isn't what somebody asking to withdraw a photo is asking for.
Act swiftly, too. A guest who must request twice halts contributing.
Hiding does not free space
A hidden contribution still eats into your album s storage, and on the free tier still falls under the 60-contribution cap. If you're hiding things since the album is full, you're using the wrong tool — that needs removing, or a larger plan.
Storage spans 5 GB on the free tier to 250 GB, and video does the filling.
Download before you delete
Pull the album down first, then clean up. Once you have the files, a deletion costs you nothing irreplaceable; before that, it loses you the only copy. That counts double near the end of the retention window, when the entire album goes anyway.
On the paid plans that's 1 download of everything. The free tier offers no bulk export.
Common questions
Can I get a hidden contribution back?
Yes. Hidden items gather in their own area and can be restored at anytime.
Can I get a deleted one back?
No. Removing is final, which is why the dashboard requests you to confirm.
Does hiding free up storage?
No. Only deleting does. A hidden file still counts.
A guest wants their photo removed — hide or delete?
Remove. Hiding keeps the file with you, which isn't what they asked for.
Do guests know something was hidden?
They see it's no longer in the album. They aren't told who removed it or why.
Approve, reject and approve in bulk
The queue, for events that review first.
Guests: finding, deleting, downloading
Why a withdrawal request reaches you at all.
When to create it, how long it collects
Get the files down before the album expires.
A guest album for a birthday
The 10-minute pass that turns a pile into an album.
You deleted something by mistake
Write to us right away with the album name and about when. We can't make promises, but the sooner we hear, the better.