An invitation, not another login
Let wedding guests contribute without a Google account
Wedding photo sharing without Google account requirements starts with a simple distinction: you register to host the collection; your guests do not register to contribute. Send them the event link or its QR code, and they can choose pictures in their browser without joining another service.

Separate your host account from their contribution
A relative asking whether they need Gmail may be asking several different questions. They might have forgotten a password, use another email provider, or simply not want a wedding photograph linked to a new profile. Answer the practical question first: Candid Photos does not require guests to have a Google account or any other account. The registration belongs to the person creating and managing the event, not to everyone holding a phone at dinner.
- The host
- You register, create the event and manage its settings through your own account. Keep the host login separate from the address you send to guests. Your dashboard is the working area for the collection, not the destination that belongs on the invitation or table card.
- The contributor
- A guest opens the event page and supplies a name with their contribution. Giving a name is not creating a profile, choosing a password or connecting a Google library. Tell people what the name is for: helping you recognise who sent the photograph, rather than proving their identity.
- The invitation
- The share link and matching QR code lead to the guest experience. Neither is a Google invitation requiring acceptance. A person can use their existing email or messaging service to receive that link; the service carrying your message does not become the service managing your photographs.
Choose a collection destination, not a new email identity
Do not make the decision by arguing that one technology company is good or bad. Decide what you want a wedding guest to do. Someone who already shares family pictures through Google may prefer that familiar arrangement for everyday use. An event-specific collection serves a narrower purpose: receive chosen photographs from people whose phones, accounts and confidence differ. You can keep using your own photo library afterwards without asking all your guests to adopt it.
Start from an existing shared library
- Check its current contribution requirements with someone who is not already signed in. A successful test on your own phone can hide an account dependency that a guest will encounter.
- Explain whether the invitation lets people view, add files, or both. Receiving a link does not necessarily mean that every action behind it follows the same access rules.
- Choose this route when the actual people contributing are comfortable with it, rather than assuming that everyone already uses the same service.
Start from the wedding upload page
- Create the event as its registered host, then circulate the guest address. Guests contribute in the browser without a Google login or a separate Candid Photos account.
- Ask for a small selection of relevant pictures rather than access to anybody's whole library. The guest chooses the files they want to send from their device.
- Make a separate decision about guest browsing. An easy upload route does not require you to show the collection to everyone who has the link.
Run a signed-out rehearsal before printing
The most useful test is not whether you can see a beautiful event header. It is whether somebody with none of your saved sessions can complete the job. Ask a willing helper to use their own phone and an ordinary, non-sensitive test picture. Watch where they hesitate without taking the phone away immediately. That hesitation tells you whether the instruction needs changing before you print a hundred copies of it.
Open the actual guest destination
Copy the share address from your event, not the address bar of a dashboard screen. Open it outside your host session and check that the event name is recognisable. If you are shown a host login, inspect the address before telling the helper to register.
Choose and submit one photograph
Let the helper operate the file picker and enter their name. They should select a file they are happy to share, submit it and wait for the page to confirm the result. Opening the page alone does not test the transfer.
Check the receipt at both ends
Look for the contribution in your host view. If you have enabled approval, check the waiting submissions rather than expecting immediate gallery display. A successful upload and a visible photograph are different outcomes, and your test should distinguish them.
Keep a record of the instruction that worked
Write down the shortest explanation that the helper understood. Reuse that wording on the cards and in the follow-up message. A rehearsal earns its time when it changes the guest instructions, not just when it proves you can operate your own event.
Write the no-account promise where people need it
People should learn that no registration is needed before they decide whether to scan. Put the reassurance beside the request, not in a long explanation reached afterwards. Keep the hosts' names visible so the destination feels connected to the wedding. Avoid calling the collection a drive, a shared login or an email account: those terms send guests looking for credentials they do not need.
A table-card version
Use wording such as: Send us a few wedding favourites. Scan this code, choose your photos and add your name. No Google account or other guest account is needed. Please keep the page open until your upload finishes. This tells a seated guest what to do and how to know they have finished.
A message for after the wedding
Try: We would love the little moments you caught yesterday. Open our wedding link whenever you have a good connection and choose a few favourites. You do not need to register. Add your real closing date and the link when sending; do not leave a vague invitation that appears to stay open indefinitely.
An answer to a cautious relative
Say: You do not have to connect your Google photos or give us a password. You choose the pictures to send on the guest page. Offer to sit beside them while they try, but leave the selection in their hands. Reassurance is more useful when it explains the choice they retain.
Help the phone find the right files
Removing registration does not remove every practical difficulty. A picture may be visible in a phone's library while the full file still needs to load from the guest's own cloud service. The file picker can also look different from the photo application they normally browse. These are device and file-selection questions, not a reason to create a wedding account. Keep the original on the guest's device until the contribution has arrived.
- Ask the guest to locate one wedding photograph before selecting a large batch. A single successful transfer makes the next attempt easier to understand and separates file selection from connection trouble.
- If the chosen item is not available locally, let the guest retrieve it through their usual library first. Any account needed for their personal storage is separate from the wedding collection's contribution requirements.
- Use the normal browser if a messaging application's embedded window behaves unexpectedly. Reopen the same trusted guest link rather than searching for a different upload destination.
- Read the actual error before retrying. A file type, connection, closed collection or capacity issue will not be solved by telling the guest to make a Google account.
- Respect the boundary of the picker. Do not scroll through somebody's private photographs on their behalf unless they explicitly ask you to help, and let them confirm the final selection.
A browser contribution still requires an internet connection. A saved QR image or an open page is not an offline upload queue.
Understand what the link does not prove
An account-free contribution route is convenient precisely because it does not authenticate every guest through a personal profile. Do not turn that convenience into a security claim. A supplied name is not verified identity, and an unlisted event address is not an authenticated private guest list. Someone who receives a forwarded link may be able to reach the page. Share deliberately and explain your expectations without promising technical restrictions that are not there.
- Distribution
- Send the event address directly to the people you intend to invite. Avoid posting it in a publicly visible wedding announcement if your intention is a small family collection. A request not to forward the link is useful etiquette, but it is not an access-control mechanism.
- Visibility
- The host can switch guest gallery browsing off to make the page upload-only. That is a separate decision from how a person contributes and from whether submissions need approval. Describe the actual setting in your invitation so people know whether they can expect to see other pictures.
- Permission
- Ask contributors to choose pictures that the people shown would be comfortable sharing with the intended audience. Be especially careful with children, vulnerable relatives and quiet personal moments. No-account upload is not consent to wider publication, and it does not replace a conversation about sensitive photographs.
Match the trial to a realistic collection
Use the free trial to test the account-free path, not as a promise that it can receive an entire wedding. Preview allows 20 photos, no video, 10 contributors and 500 MB for seven days, with no downloads. Those ceilings are useful for a rehearsal involving a few helpers. Before circulating the link widely, decide how many contributions you expect and what you need to save after the collection closes.
- A modest photo request
- Gather costs USD 19 once per event and includes 200 photos, 30 videos, 5 GB, one month online, standard downloads and a written guestbook. Choose it from the expected file count and storage requirement, not simply because the wedding has a small guest list.
- A larger set to keep
- Celebrate is USD 39 once per event, with 750 photos, 100 videos, 20 GB and three months online. It includes original-quality downloads, a video guestbook and slideshow. None of these paid features changes the basic fact that guests do not register to contribute.
- A longer collection with help
- Keepsake costs USD 69 once per event and includes 2,000 photos, 300 videos, 50 GB, six months online and two extra managers. More room still has limits: both the photo or video count and the total storage allowance matter when relatives send large files.
Recover a missed contribution without another signup
A guest who puts the phone away during dinner has not necessarily refused your invitation. They may be conserving battery, watching a speech or waiting for a better connection. Give them a later route that is as clear as the printed one. Send the same event link directly, with a short explanation and a date. Do not create a second collection merely because someone missed the first reminder.
At the reception
Keep the request small
Ask for one or two favourite moments when there is a natural pause. If the connection is poor, suggest taking pictures normally and sending them later. Guests should not feel that troubleshooting an upload is more important than being present for the wedding.
After the journey home
Give the link another context
Include it in a direct thank-you message with the hosts' names. A clickable address is better than asking somebody to scan a QR code displayed on the same phone. Mention the no-registration requirement again for anyone who ignored the first request.
Before the real deadline
Finish the transfer and the archive
Check that expected files arrived, then download your collection on a plan that supports downloads. Keep a separate copy before expiry. The absence of guest accounts does not make the event permanent, and reopening an old message does not extend its online period.
Questions from guests who do not use Google
Can I contribute with an email address from another provider?
Yes. Guests do not need a Google account or any other account to upload. Receiving the invitation through a particular email service does not require you to connect that service to the collection.
Why did the host have to register if I do not?
The host needs an account to create and manage the event. Your guest link leads to the contribution page instead, so you are not being asked to take over the host's administrative job.
Does no login mean that everybody can browse the pictures?
No. Guest gallery visibility is a separate host setting, and the page can be upload-only. Do not assume that an unlisted address verifies who is visiting it or prevents recipients from forwarding it.
Can I upload after I leave the venue?
Yes, while submissions remain open and the collection has capacity. Use the original guest link with an internet connection and wait for confirmation; scanning a code earlier does not itself send the files.
Test the guest path before you invite the room
Create your host account, open the guest link outside your own session and send one test photograph. Once that path is clear, choose capacity for the wedding and print instructions that say exactly what guests need: their chosen pictures, their name and a working connection, not another account.
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.