Receive first, decide on sharing later
Collect wedding pictures without opening a guest gallery
Looking for wedding photo sharing upload only? Switch guest gallery browsing off and use the event page to receive contributions. Guests can send their chosen files without an account, while you decide separately whether there should ever be a shared gallery. Upload-only describes the viewing arrangement, not a promise of authenticated private access.

Choose receiving as the purpose of the page
You do not have to make every contributor an audience member. Some couples want to see the photographs themselves before deciding what to share. Others want guest pictures as a personal record and have no intention of opening a shared gallery. An upload-only arrangement fits both intentions. Start by stating that purpose clearly, because guests may otherwise assume that sending a photograph buys them immediate access to everybody else's pictures.
A private viewing moment for the couple
You may want to look through the contributions together after travelling home. Receiving pictures now and deciding on wider viewing later lets the invitation remain simple. Do not promise an opening date until you are comfortable with the material and the audience you intend to invite.
A deliberate collection rather than a feed
At the reception, the task can be just to contribute a few favourites and return to the celebration. Guests do not need to browse an expanding set of photographs for their upload to be useful. Say that the page is for sending pictures, not for watching everyone else's activity.
A permanent decision not to browse together
It is also reasonable to keep guest gallery browsing off for the whole collection period. You can thank people without offering them the full set. Make that expectation honest from the first request rather than treating a future reveal as an incentive you may never deliver.
Distinguish visibility, approval and guestbook choices
These controls answer different questions. Guest gallery visibility determines whether the guest page offers browsing of the collection. Approval determines whether new submissions wait for a host decision. Guestbook availability and its own setting concern messages. One choice should not be used as shorthand for the others. In particular, hiding the photo gallery should not become a blanket claim that every other part of the guest experience has also been hidden.
- Gallery visibility
- Switching guest gallery browsing off makes the photo collection upload-only for guests. It does not mean you have stopped receiving files. Keep the distinction visible in your welcome text so a person who cannot find the gallery does not conclude that the whole event is closed.
- Approval
- The host can turn on the approval switch to hold submissions for review. That does not itself switch guest browsing off. A visible gallery can show accepted material while newer contributions wait, and a hidden gallery can stay hidden even after you accept a contribution.
- Guestbook
- Review the guestbook separately if your invitation includes written wishes or recorded messages. Do not assume the gallery setting makes every message private to the couple. Check the actual guest pages and the available settings before describing who can read or watch anything submitted there.
- Downloads
- The ability to download files is another decision, subject to package availability and settings. Preventing downloads is not the same as preventing viewing. If the goal is no guest browsing, choose that explicitly rather than relying on the absence of a download button.
Set up the receiving path before distributing it
The owner registers and creates the event; guests use the event link or QR code without registering. Configure the collection before printing the request, then check it from outside the host account. Your dashboard will naturally show material you manage, so looking only at that screen cannot tell you whether a guest sees an upload-only experience. Use a helper's phone or a separate browser session for the final check.
Prepare a recognisable event
Use the couple's names and a clear event title. Add a welcome message explaining that this page receives pictures for the couple and does not currently offer guest browsing. A recognisable destination helps people distinguish the correct link from an unrelated message or a dashboard address.
Switch off guest gallery browsing
Find the public gallery setting in the event controls and turn it off. Keep photo uploads available if receiving photos is the purpose of the page. Review video and guestbook choices separately rather than treating upload-only as a bundle of every possible setting.
Submit a harmless test
Open the guest link, choose a non-sensitive test photograph, enter a contributor name and wait for the result. Confirm receipt in the host workspace. Do not use immediate gallery appearance as the success test, because you have intentionally removed that browsing experience.
Approve the wording for print
Once the test behaves as intended, print a single card and scan it. Make sure its promise matches the current page: send pictures to the couple, not scan to see the full gallery. Keep the same meaning in your digital follow-up invitation.
Tell guests what success looks like without a gallery
People often look for their picture in a gallery as proof that it arrived. When browsing is off, explain that the upload confirmation is the useful signal. Otherwise a guest may resend a successful batch or assume the feature is broken. You do not need a long privacy statement on the table; you need a precise sentence about what the page does and what happens after pressing send.
- On a table card
- Try: Share a few wedding favourites with us. Scan, choose your pictures and add your name. This page is for sending photos to the couple, not browsing a guest gallery. Please wait for confirmation before closing it. No guest account is needed. Add the event's actual link and names when you prepare the card.
- In a follow-up message
- Try: We are collecting the moments we missed. Please send a few favourites through our wedding link by the date below. The gallery is not open for guest browsing, so you will not see the full collection afterwards. We will let you know separately if we decide to share pictures later.
- When somebody asks where their image went
- Explain: The page confirmed your upload, and we are receiving the pictures in our collection. Guest browsing is switched off, so your image is not supposed to appear in a shared gallery. If the page showed an error rather than a confirmation, tell us what it said and we will check.
Set honest boundaries around the unlisted address
Upload-only limits guest browsing of the photo collection. It does not turn the event address into a verified invitation list, and it does not prove who is uploading. Guests provide a name, not an authenticated identity. The address is unlisted and kept out of search indexes, but unlisted does not mean authenticated private. Anyone entrusted with a link can pass it along, so your distribution choices still matter.
Do not promise secrecy from a viewing switch
Avoid saying that only named invitees can ever reach the page, that forwarding is impossible or that every file is guaranteed confidential. Those are stronger claims than upload-only supports. If a picture would cause serious harm if shared beyond its intended audience, the safer decision may be not to collect it through a broadly circulated event address at all.
- Send the event link through the direct channels you intend to use, rather than putting it in a public announcement and then describing the destination as invite-only.
- Ask guests to send photographs they have permission to share, and give them a straightforward way to contact you about a sensitive image.
- Make no automatic promise about guestbook visibility. Inspect that part of the experience separately if you enable it, especially when inviting personal written or recorded messages.
- Remember that the owner and any authorised helpers have a different working view from guests. Explain access accurately instead of saying nobody can see a file until a future reveal.
- Keep administrative invitations and credentials out of the guest request. An upload link is not the same thing as permission to manage the collection.
Use the right control for the actual concern
Several wedding arrangements can look quiet from a guest's perspective, but they are not interchangeable. Choose upload-only when you do not want a guest photo gallery. Choose review before display when you do want a gallery, but not immediate publication of every submission. Choose an upload deadline when you want contributions to stop. Naming the concern first stops a settings change from solving one problem while accidentally creating another.
Receive without guest browsing
- The invitation asks guests to send selected files to the couple. Success means the submission is received, not that the sender can browse the whole event afterwards.
- Accepting a contribution does not require opening the guest gallery. You can organise your own review and keeping work while leaving browsing switched off.
- This fits a couple who want to decide later whether any wider sharing is appropriate. It also fits a couple who never intend to offer a shared gallery.
Review before showing a guest gallery
- The gallery is available, but the host turns on approval so new submissions wait for acceptance. Guests can see accepted material without every arrival appearing immediately.
- The host needs a review routine and wording explaining that visibility may be delayed. A waiting image is not necessarily a failed upload.
- This fits a collection intended for guest browsing after a human check. It does not authenticate the audience or make forwarding the event address impossible.
Test the promise across each guest-facing surface
A single successful upload does not prove the whole invitation is clear. Guests may arrive from a printed code, a saved link, a follow-up message or an older browser tab. Check the routes you actually intend to distribute. If you previously showed a gallery, changing its visibility cannot undo what people already saw or saved. Treat the change as a new arrangement and explain it rather than implying the earlier exposure never happened.
Check the fresh visitor experience
Open the current guest link outside the host session. Confirm that the upload request is readable and that the intended photo browsing route is unavailable. If what you see differs from the saved setting, resolve that discrepancy before inviting more contributors.
Inspect message and guestbook routes separately
If the event includes a guestbook, open its guest-facing route and see what a visitor can read or submit. If it does not match your intended boundary, adjust the relevant setting or wording. Do not infer its behaviour from the absence of a photo gallery.
Check any room display independently
A slideshow is a separate display destination. If you do not want event media shown on a room screen, do not distribute or run that display merely because the guest photo gallery is hidden. Review every place you deliberately show the collection.
Ask the helper to explain the outcome
After testing, ask what they believe will happen to their contribution and whether they expect to browse later. If their answer differs from your intention, rewrite the invitation. The best test checks understanding as well as whether a button works.
Keep collection time and the later handover realistic
Hiding the gallery does not change the package's counts, storage or expiry. Preview has 20 photos, no video, 10 contributors, 500 MB and seven days online, with no downloads. It suits a small photo rehearsal, not a plan to receive wedding files and save a final archive. Choose the event's capacity and download option before the link reaches everybody, even if nobody will browse the collection.
Before collecting
Choose a downloadable outcome
Gather costs USD 19 once per event and includes 200 photos, 30 videos, 5 GB, one month online and standard downloads. Celebrate costs USD 39 with 750 photos, 100 videos, 20 GB, three months online and original-quality downloads. Check the full current details against your expected contributions.
When the couple is ready
Make a fresh sharing decision
Review the material and the promises made to contributors before switching guest browsing on. Do not treat an upload to the couple as blanket permission for wider publication. If you decide to share a gallery, explain the new audience and arrangement clearly.
Before expiry
Save the collection regardless of visibility
Download and verify your own copy while the collection is available. Extra online time costs USD 9 for six more months or USD 15 for twelve, starting at the existing expiry. The visibility switch does not extend that period or provide a separate backup.
Questions about receiving without showing
Can guests still send photos when gallery browsing is off?
Yes, that is the purpose of an upload-only photo collection, provided uploads remain open and capacity is available. The contributor should wait for the upload result rather than expecting to find the file in a guest gallery.
Does approving a picture make the hidden gallery open?
No. Approval and gallery visibility are independent decisions. You can accept a submission while leaving guest browsing switched off.
Does upload-only mean guests cannot forward the address?
No. It describes the photo viewing arrangement, not an authenticated invitation system. Share the link deliberately and do not claim that an unlisted address can never reach another person.
Must I open the gallery when the wedding is over?
No. You can keep browsing off and use your own downloaded copy, subject to the package's download availability. Tell contributors that intention upfront rather than promising a shared reveal you do not plan to provide.
Make the page a clear request to send, not to browse
Create the collection, switch guest gallery browsing off and test a contribution outside your host account. Then use wording that matches the experience and a keeping plan that fits the expiry. You can receive the wedding's missing moments without promising a shared gallery in return.
How it works
Put one link on the tables and let everyone contribute.
Create a collection, print the table stands, and the photographs your guests took are waiting for you the morning after. Guests never install anything and never make an account.