A link from your existing website
Give your wedding website one clear photo link
Your wedding website already answers where to go and when to arrive. A wedding website photo upload link answers a different question: where should a guest send the pictures afterwards? Add an ordinary hyperlink to the event's guest page, with a short explanation of what happens next. The website remains your information page; the collection opens separately in the browser. No embedded upload form or website-builder connection is required.
Collecting everyone's pictures into one place, whatever the occasion.

Keep the website and the upload destination distinct
An ordinary hyperlink is enough to connect the two jobs. On your wedding website, the guest reads a short invitation and selects a clearly labelled link. That link opens the Candid Photos guest page, where they can choose files and follow the upload form. You are not moving the collection into your website, copying a gallery into its layout or asking the website builder to manage photographs. This distinction makes both the setup and the guest explanation easier: one page provides context, and another receives the contribution.
Avoid describing the arrangement as an embedded gallery or an integration unless you are discussing a separate capability you have independently verified elsewhere. This guide is about the simple link alone. It does not need a plugin, an API key or code pasted into your page. If your website editor supports linking text, you can use its normal link control. Guests do not need a Candid Photos account, app or password to use the upload destination. Any access rule on your own wedding website remains a separate matter and should not be confused with an account requirement for guest uploading.
Copy the guest address rather than a host bookmark
Create the event and check its identity
Use the couple's names and the intended wedding date so visitors can recognise the destination. Make the important visibility decisions before distributing the address. If you are still experimenting, do not publish a test collection as if it were the final wedding destination; changing addresses after guests have saved them creates avoidable uncertainty.
Take the share link intended for guests
Copy the event's guest address, not the address bar from your management screen. A dashboard bookmark may work for you because you are signed in, which is not a useful test of guest access. Keep one authoritative copy of the address while editing your site and printing signs so you do not accidentally mix two events.
Attach that address to ordinary text
Select a descriptive phrase in your website editor and use its usual insert-link option. Paste the guest address into the destination field and save the change. The names and placement of editor controls vary by website provider; you do not need a provider-specific connection from Candid Photos. Do not paste host credentials into any link field.
Publish, then test the published page
An editor preview is not always the same as the page guests will receive. Open the public or guest-accessible version you intend to share, follow the link and check the wedding name. Test without depending on your existing host session. If a link cannot be added in that part of the layout, choose a normal text section rather than inventing an unsupported embedding workaround.
Write link text that explains the next action
- Use an action and an object
- Share your wedding photos tells a reader more than Click here. Someone scanning the page can understand the destination without reading the surrounding paragraph. Avoid vague labels such as Our memories if they could mean a story about the couple, the professional photographer's portfolio or a slideshow rather than a place to contribute files.
- Describe the browser handoff
- A short sentence can say that the link opens your guest upload page and that no app, account or password is needed. Do not promise that the page has no form: guests still follow its identifying-detail and consent requirements. Tell them what they are being invited to do, without claiming the upload happens inside the wedding website.
- Match the wording to available actions
- Use Send us your photos if the guest page is upload-only. If guests can also browse, explain that separately rather than making the link sound like a public gallery for everybody on the internet. Mention videos or a guestbook only if you have actually made those options available for this event.
- Prefer clarity over themed language
- Playful wedding wording can surround the link, but the link itself should remain understandable. A guest should not need to decode an in-joke to know where photographs go. Keep the phrase concise enough to wrap neatly on a phone and distinct from nearby links for travel, gifts or RSVPs.
Place the invitation where guests will look for it
Before the wedding, keep practical information first
Travel, timings and access needs are likely to matter more than uploading photographs that do not exist yet. Put a short photo note in a relevant information section, not over the arrival instructions. If the ceremony is unplugged, say clearly when photography becomes welcome. The website should not encourage behaviour that conflicts with the officiant's instructions on the day.
During the celebration, make a phone visit useful
A guest who opens the site from a saved message should find the photo link without searching a long relationship story. A visible heading such as Wedding photos can help. Avoid placing the only link inside a decorative image, a tiny footer or a paragraph that becomes difficult to read on a small screen. Check the actual mobile page rather than assuming the desktop layout will shrink well.
Afterwards, update the surrounding sentence
Once the wedding has happened, replace future-tense instructions with a simple invitation to share a few favourites. Remove outdated travel notices if they obscure the relevant link, while preserving information guests still need. You are editing your own website manually; the collection does not automatically rewrite your site as the event passes through different stages.
Treat public placement as a separate access decision
A collection link is not the same thing as a list of named invitees. Guests need no password for the upload page, so think carefully before putting its address on an unrestricted website. The guest pages are kept out of search indexes, but publishing the link elsewhere can still make it available to people beyond your intended circle. An unlisted address is not a guarantee that nobody can forward it. If your wedding website is publicly accessible, consider whether a private message to guests would be a better place for the upload address.
Questions to answer before making the link visible
- Who can open the page where you are placing the link? Check the website's actual access arrangement rather than assuming only invited guests know it exists.
- What will a visitor see after following the link? Switching off the public gallery makes the guest page upload-only; it does not turn the address into a personalised invitation checked against a guest list.
- Have you explained the audience for submitted photographs? Browsing, host review and a room slideshow are separate decisions. Use the approval switch when you want to review submissions before they appear, without presenting it as a substitute for consent.
- Is there a private contact route for questions or removal requests? A person who is uncomfortable with a photograph should not need to post their concern on the wedding website for everyone to read.
Test the journey on the screen guests will use
Read the page at normal phone size
Check that the invitation is easy to find and the link can be selected without accidentally hitting a neighbouring control. Increase the text size using the device's own settings and see whether the surrounding copy remains usable. This is a test of your chosen website layout, not a promise that every design or device behaves identically.
Follow the link without the host session
Use a separate browser session to check the guest route. Confirm that it opens the intended event rather than a login screen, expired test or unrelated page. If your own website requires access before a guest can reach the link, test that first step separately so you know where a reported problem is happening.
Try a suitable test contribution
Select one non-sensitive photograph, enter the requested details and read the consent information. Watch the upload status instead of assuming the file arrived when the picker closed. Then check the host view. A successful page load and a completed upload are different checkpoints; testing both catches more useful problems than repeatedly refreshing the website.
Check the route back and the message around it
Whether your editor opens a new tab or the same tab, make sure the handoff is understandable. Avoid forcing a particular browser behaviour unless there is a good reason. Ask a willing tester to describe what they expected from the link label and what they found, without guiding every tap or treating confusion as their fault.
Use a website note, not a wall of instructions
The website needs enough information for an informed choice, not the entire help guide. Explain what is welcome, where the link goes, who can see the pictures and whether there is a preferred date. Keep detailed troubleshooting elsewhere so willing guests can reach the upload page promptly. These invented examples show different visibility arrangements; choose one only after checking that it describes your event accurately. Replace the bracketed address using your editor's ordinary hyperlink control.
- Example: guests can browse
- We would love a few favourites from your view of the wedding. Share your wedding photos at [guest upload link]. The page opens in your browser without an app or account, and our wedding guests can browse the collection. Please share only pictures the people shown are comfortable with. Contributing is optional.
- Example: sending to the hosts
- If you took a picture you would like us to have, use Send us your wedding photos at [guest upload link]. This guest page is for uploading rather than browsing other people's pictures. There is no need to take or send anything especially for us. Thank you for being part of the day.
- Example: after the wedding
- Thank you for celebrating with us. If you would like to share photographs, our guest link is [guest upload link]. We hope to finish collecting by [preferred date], before the collection closes. A few favourites are welcome, and no photos or no wish to share is completely fine.
Keep the link useful through the collection's lifetime
A website can remain online longer than the collection it links to. Plan for that difference. Preview includes seven days online, 20 photos, 10 contributors and 500 MB, with no videos or downloads. Gather costs a one-off $19 USD per event for 200 photos, 30 videos, 5 GB and one month online, including standard downloads and a written guestbook. Do not leave wording that promises a long-running downloadable archive beside a trial link that cannot provide it.
Celebrate costs a one-off $39 USD per event for 750 photos, 100 videos, 20 GB and three months online, with original-quality downloads, a slideshow and a video guestbook included. Keepsake costs a one-off $69 USD per event for 2,000 photos, 300 videos, 50 GB and six months online, with two extra managers and the included features of Celebrate. Paid plans allow unlimited contributors but still have finite file and storage allowances. Choose for the expected collection rather than the sophistication of your wedding website. Check the real closing date, download in time and manually remove or update the website invitation when it is no longer useful. An old link should not keep asking guests to do something they can no longer complete.
Common questions about linking from a wedding site
Can guests upload without leaving our wedding website?
The setup described here is an ordinary hyperlink to a separate guest page, not an embedded uploader. Make that handoff clear in the surrounding text. Do not promise an in-page form or a website-builder integration based on the existence of a share link.
Should we put a QR code beside the website link?
A clickable link is usually the useful route for someone already reading on their phone. A matching QR code can serve printed materials or a second screen, but should not replace the link. Both should lead to the same checked guest destination.
What if the website editor removes our link?
Use the editor's normal supported text-link feature and check its own publishing instructions. Candid Photos provides the guest destination, not control over another website's editor. You can send the guest address in an appropriate private message while resolving your website issue.
Will changing the website text change the collection?
No. Editing your website note does not change the event's visibility, capacity or closing date. Make any event decisions separately, then bring the wording into line with the settings. Test again if you replace the destination address.
Make the link simple and the destination deliberate
Create the event, copy its guest address and test it before adding one descriptive link to your wedding website. Keep the invitation short and the audience clear. Guests can then move from practical wedding information to a place that actually receives their pictures.
Event photo sharing
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.