
From collection to files
Take a complete, checked copy off the website
A successful click is only the beginning when you download all wedding guest photos. You need the transfer to finish, the ZIP to open, and the photographs and videos inside to be usable. This walkthrough separates the host archive from guest viewing and explains what to verify before treating a downloaded collection as safely received.
Define what a whole-collection download contains
Candid Photos provides a host-side archive that streams the collection's media files into one ZIP. That is different from saving a picture shown in the gallery grid: a small display preview is not the archive file. It is also different from asking each guest to download the entire collection. Plan the full transfer as host work, then decide separately whether anyone else should receive particular files. The archive is a container for photographs and videos, not a finished book, a family slideshow project or an export of every piece of information shown on the website.
Rejected media is excluded. Do not use that rule to assume the bundle is a ready-to-publish set of accepted pictures: review outstanding submissions and sensitive content before redistributing anything. The downloadable collection can also change while guests are still uploading. Record when you took the copy and what contribution deadline it represents. If you download on Tuesday and a relative adds pictures on Thursday, Tuesday's file has not updated itself. A named, dated snapshot gives you a useful reference when you later compare the website with what is on your computer.
Match the download expectation to the purchased plan
- Preview is for trying the collection
- The free plan allows 20 photos, no videos, 500 MB and ten contributors for seven days. Downloads are not included. Use it to understand the guest upload experience, not as a promise that a trial collection will provide a downloadable archive without a suitable paid plan.
- Gather provides standard downloads
- For a one-off USD 19 payment per event, Gather includes 200 photos, 30 videos, 5 GB and one month online, with a written guestbook. Describe its download entitlement as standard. Do not silently promise original-quality delivery when explaining this plan to somebody preparing a print project.
- Celebrate includes original quality
- Celebrate costs USD 39 per event and provides 750 photos, 100 videos, 20 GB and three months online. Original-quality downloads, written and video guestbooks, and slideshow are included. Original quality means the uploaded file, not a reconstruction of a better version that stayed on the guest's phone.
- Keepsake increases capacity and time
- At USD 69 per event, Keepsake includes 2,000 photos, 300 videos, 50 GB and six months online, original downloads, written and video guestbooks, slideshow and two extra event managers. Larger allowances do not make local disk space unnecessary; plan where the finished ZIP and extracted files will fit.
Prepare the receiving computer before starting
- Choose a computer and destination you control. A shared work machine or a public downloads folder may expose personal pictures to people who were not intended to receive them. If you must use a shared device, agree where the files will go and who can access that location.
- Check free disk space for both the ZIP and the extracted contents. Compressed photographs and videos do not necessarily become much smaller inside an archive. Leave working room rather than assuming the available storage allowance equals the exact size of the transfer.
- Use a stable connection and keep the computer powered. Avoid beginning a large download just before travelling, closing a laptop or switching networks. The archive is streamed to the browser, so the receiving connection matters throughout the transfer, not merely when you press the button.
- Locate your browser's download list and destination folder in advance. Knowing where completed and partial files appear makes troubleshooting easier. If the destination is an automatically synchronised folder, be aware that another upload may begin after the download; check the local file first rather than trusting a cloud status symbol.
A desktop or laptop is a practical recommendation for handling a large ZIP, not a requirement for guests to contribute. Guests upload in their browser without an app, account or password.
Take the archive in a deliberate sequence
Open the host collection
Use your signed-in host access rather than the guest QR address. Confirm that you are looking at the correct wedding, especially if you have collected pictures for more than one event. Check the plan and download setting if the action is unavailable. A guest page that opens successfully does not demonstrate that the host archive entitlement is active.
Finish the review that defines this snapshot
Look for outstanding submissions and decide whether the collection is ready for this download. You can take an early safety copy before the final deadline, but label it as such. Do not delete uncertain material just to make a count look tidy; resolve the decision or keep a clear note of what remains to be checked.
Start once and watch the browser result
Allow the transfer to complete before opening the file. Repeatedly pressing the action can create confusing partial or duplicate downloads without improving the connection. Check the browser's status rather than assuming a filename appearing on disk means all bytes have arrived. Record an error message if the transfer stops so that you can describe the actual failure.
Name the received snapshot clearly
Once the file is complete, give the saved copy a local name that includes the wedding and download date. Preserve the ZIP while extracting a working copy into its own location. Renaming the container locally is a filing decision; it does not change the collection online or create a separate event within the product.
Extract the ZIP and inspect what came out
Use your computer's archive extraction tool to unpack the completed ZIP. Do not merely look at the file list inside the container and conclude that everything works. Open photographs from the extracted location and play videos beyond their first frame. Choose samples from the beginning, middle and end of the file list, then check any particularly important moments individually. A selection of readable files is useful evidence, but it does not prove that every other file is healthy. For a collection that matters greatly, allow time for a more thorough inspection.
The archive may include a text note when a stored file could not be read. Look for those notes rather than counting every entry as a successful photograph or video. Compare your expectations with actual media files and investigate mismatches while the event is still accessible. Numbered archive filenames help keep entries distinct, but they are not a reliable timeline of the wedding. The download order follows the collection's file entries, not necessarily the moment each camera took its picture. Save questions about sequence for a later local organisation pass; first establish that the files you expected have actually arrived.
Understand the difference between original and best available
An original-quality download preserves the file that was submitted. If a guest uploaded a screenshot, a heavily edited copy or a picture previously saved from a messaging conversation, the service cannot restore detail that was lost before upload. For a favourite photograph that looks unexpectedly small, ask its contributor whether the camera version is still on their phone. Explain which frame you mean and why you want it, rather than asking them to resend their whole library. A direct upload of that better source can be more useful than repeatedly downloading the existing file.
Likewise, an unfamiliar file format is not automatically corruption. Your computer may need suitable software to display a photo or play a particular video. Keep the received source unchanged while trying another compatible viewer or making a separate conversion for a specific purpose. Do not overwrite the only copy with an experimental export. If you intend to print, assess dimensions and crop suitability separately; if you intend to edit video, check sound and playback in the software you plan to use. The archive solves retrieval, while those later tasks have their own quality checks.
Troubleshoot the stage that actually failed
- The action is not available
- Check that you are using host access, that the event remains available, and that downloads are enabled for an eligible plan. Preview has no download entitlement. Do not try to work around an unavailable action through a guest address; resolve the setting or plan question and use support if the displayed state still does not make sense.
- The browser stopped receiving
- Keep the failure message and note whether the connection changed or the computer slept. A partial ZIP is not a checked archive. After addressing the local problem, make a fresh attempt and distinguish the new file from the incomplete one. Avoid deleting a previously verified snapshot while you are still trying to receive its replacement.
- The ZIP opens but a file is missing
- Inspect any missing-file notes and check whether the item was rejected or arrived after the snapshot. If a file that should be present cannot be read, report the event and relevant filename through support without posting private images publicly. You may also ask the contributor to retain their source while the issue is investigated.
- A video does not play
- Try a compatible local player before concluding that the transfer failed. Compare file size and any error details with the rest of the download evidence. When asking for help, describe whether extraction failed, playback failed or audio is absent; those are distinct symptoms and call for different checks.
Account for late uploads without overwriting your evidence
Take an early archive if the pictures are important, then take a final one after your stated upload deadline. Keep their dates distinct. Extract the later copy into a new local folder rather than merging it blindly into the earlier one, where repeated filenames and operating-system replacement prompts can obscure what changed. Compare the contents manually or with a local file comparison tool you understand. Candid Photos does not promise built-in duplicate sorting or folder organisation for this task. An upload made twice may need your judgement even when the two pictures look identical.
Write a short local receipt for yourself: the download date, the contribution cutoff, any known missing files and whether you checked the important videos. This need not be an elaborate catalogue. Its value is that somebody revisiting the folder later can distinguish a complete final transfer from a provisional copy. If you hand the archive to your partner, ask them to extract and open it on their own device too. Do not remove the earlier verified copy until the later one has passed those checks and you have a separate preservation plan.
Finish before the collection's closing date
Use the event's actual online end date to schedule retrieval. The included periods are finite and run from the event date, so a plan described as one month online is not a fresh month starting whenever you remember to download. Put the first transfer comfortably before the deadline, leaving room for slow connections, a busy weekend or support questions. A warning message is helpful, but your own calendar should carry the task. Do not wait until the last evening to discover that your computer has no room for the files.
After checking the archive, arrange a separate backup rather than treating a single local ZIP as the entire preservation strategy. A second copy on an independent destination reduces dependence on one device; opening that copy confirms more than seeing a successful copy notification. Keep sensitive material out of casually shared folders. If the online collection has already closed, ask support what options exist for your specific event, but do not assume restoration is available or guaranteed. The dependable plan is a download completed and verified while the collection is accessible, followed by storage you actively maintain.
Questions about the host ZIP
Can I tell every guest to take the full ZIP?
No. This guide describes the host-side whole-collection archive, not a promised bulk-download feature for guests. If relatives need copies, review the files and arrange an appropriate selection or handoff with permission.
Will the archive include the written guestbook?
Do not plan around a written guestbook export. The ZIP is a media-file archive; arrange any separate use of written messages with their authors rather than assuming a printable transcript is included.
Does downloading remove the online collection?
Taking a copy is a retrieval task, not an instruction to delete the event. The collection's settings and finite online period still matter, and any uploads made after your snapshot require a later download if you want to retain them.
Is an extracted folder already a backup?
It is a usable copy, but one device remains one point of failure. Keep the untouched archive and arrange another checked copy separately, then use a working folder for edits, print selections and sharing.
Give the download its own place on the calendar
Check your plan, choose a receiving computer and leave time to inspect the result. A completed, readable archive is the useful finish line, not the moment you press download. Start with the plan comparison if you have not yet chosen the event's download quality.
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.