Step 1 of 8
Choose the collection you want to keep
Give guests one contribution link, a clear request and a named person who will review the files. Decide first whether you want an archive of original photographs, a gallery guests can browse, or selected memories for a wedding video. Those are different outputs; do not choose a tool for one and assume it supplies all three.
AlbumMap collects guest memories for an organizer to review and use in a slideshow or map video. Its contribution page is not a gallery of everyone’s submissions. If your main goal is a downloadable photo archive, check original-file retrieval before choosing your collection method.
Guest photographs can complement the professional record. Agree with the photographer and planner when phones are welcome; a reception collection does not require guests to photograph an unplugged ceremony.
Step 2 of 8
Set up the organizer side before printing a sign
- Name the collection owner and a wedding-day helper. Agree who can receive the files and what the couple may share afterward.
- Choose slideshow style when the photographs are the story. Choose a map video only when the locations add meaning.
- For AlbumMap, sign in and save the album before creating the contribution link. Open Guest uploads and use Copy link or the Contribution QR code.
- Open the actual guest destination in a separate browser. Check the event name, required fields and submission route before distributing it.
- Agree a collection deadline and an archive plan. Check export access and publication permissions before promising the finished gift.
The guest-contribution FAQ explains the account and link controls. Guests can submit in a browser without an account or an installed app; the organizer needs a saved account project. A private contribution URL is different from the password used for an interactive-map viewer.
Step 3 of 8
Explain what the guest will do
The AlbumMap form asks for Name, offers Message or memory and accepts Media. In map mode it also requires a Map location: choose a suggestion so the location is set. Slideshow contributions do not require a map stop. Give guests an example of a city or venue rather than asking for their home address.
Guests choose Upload for review after preparing their contribution. Selecting files or watching Memory preview is not the final submission. The organizer receives the submission in Guest uploads and decides whether to Approve or Reject it.
An unsigned guest can return from the same browser to edit their submission; signing in first supports returning with that account on another device. Tell the helper this distinction so they do not promise cross-device editing to someone who submitted anonymously.
Ask for one or two favorites, with a name or short explanation where needed. Someone who could not attend can contribute an older photograph or a wish; they should not have to manufacture a wedding-day picture.
Step 4 of 8
Use a short reception sign and one reminder
Reception sign: “Caught a moment we missed? Add one or two favorite photos or a short clip for [Couple] at [contribution link]. This collection goes to [organizer] for review and the agreed wedding keepsake. Please upload by [date and time zone]. For help or a removal request, contact [helper].”
Put the QR code beside the direct link, not in place of it. Replace every bracketed field and check the destination before printing. Place the sign where reception guests can pause without blocking the photographer or ignoring the ceremony’s phone rules.
Use the wedding photo QR printing guide for code size, layout and the actual printed scan test. This page handles the collection and review; a QR code does not itself add a password or restrict forwarding.
One follow-up can say: “Thank you for celebrating with us. If you would like to add a favorite photo or clip, please use [same link] by [date and time zone]. We are reviewing the collection for [agreed audience and use]. There is no need to send anything you would rather keep private.”
Step 5 of 8
Review the files without turning the wedding into a sorting project
Start with a few contributions as they arrive. Check that the file opens, people are recognizable, speech is audible where relevant, and the contribution belongs to this wedding. Ask for a replacement only when the issue prevents the intended use.
| Review decision | What it means for this collection |
|---|---|
| Keep for the couple | A useful private memory, with the contributor’s context and any limits preserved. |
| Consider for a wider share | A separate selection requiring review of everyone shown and the intended audience. Uploading is not blanket public-use permission. |
| Exclude from the edit | An accidental file, duplicate, private moment or item the contributor wants removed. Excluding a scene and deleting its source are different decisions. |
Use the organizer’s Approve and Reject controls for inclusion in the project. Those controls do not replace a separate decision about social posting, publicity or the couple’s personal archive.
The guest-upload privacy guide covers audience choices and removal requests in more detail.
Step 6 of 8
Check files, plan limits and storage as separate questions
Ask guests to retain their originals until you confirm the transfer you need. A playable preview or finished wedding video does not establish that you can retrieve an unchanged camera file. Test that requirement with a small permitted file; use another agreed transfer method if your archive needs are not met.
Read the current upload FAQ for accepted formats and source-file limits, and pricing for the final guest count and export access. Free permits guest collection but excludes those guests from video exports. Video-credit exports allow up to four included guest contributions. Collection access alone is not a promise of an unlimited group export.
For a private wedding, agree on the audience and delivery method before collecting photos or exporting the video.
A finished video download is available for 48 hours, with its expiry shown in the dashboard. Download it in time. That window is separate from saved-album retention and from the original-photo archive you arrange. A deleted album remains in the Recycle Bin for 30 days before permanent deletion; use the displayed date for the specific album.
Product references rechecked 26 October 2026: FAQ and plans and export terms. Recheck them for your project before inviting guests.
| One permitted-photo rehearsal | Record before closing collection |
|---|---|
| Contributor’s original | Original name, byte length, pixel dimensions and SHA-256 value. |
| Organizer’s retrieved file | Download from the chosen transfer destination; record the same four fields. |
| Comparison | Matching SHA-256 values establish identical bytes for these two files. A mismatch needs investigation; dimensions alone do not prove identity. |
| Separate archive | Copy the verified file and its source record to the couple’s independent storage and reopen it there. |
If the chosen video workflow does not offer the original-photo retrieval you require, collect the originals through a separate agreed transfer destination. Do not ask the couple to rely on frames extracted from the finished MP4 for printing or preservation. Use this table as your own transfer record. The worked comparison below establishes the preservation of one uploaded original; it does not establish a complete guest-download archive.
Step 7 of 8
Compare a preview with the file you uploaded
A 26 October 2026 synthetic trial sent a numbered PNG card through the guest form and approved it into the owner’s saved slideshow. The owner could see the correct picture. Saving the already-loaded preview asset exposed a smaller display copy:
| File checked | Format and dimensions | Size |
|---|---|---|
| Original selected for upload | PNG · 640 × 360 pixels | 10,256 bytes |
| Owner-visible preview asset | WebP · 240 × 135 pixels | 1,214 bytes |
| Original loaded by the owner’s media editor | PNG · 640 × 360 pixels | 10,256 bytes; byte-identical to the upload |
The preview had a different SHA-256 checksum. A later check opened the approved photo in the owner’s media editor, which displayed the original filename, 10 KB and 640 × 360 pixels. Exporting that already-loaded original through browser asset inspection recovered exactly the uploaded PNG bytes and matching SHA-256 checksum. This establishes that the original remained available for this one file, alongside its smaller preview.
The editor’s normal control was labelled Download edited image, with Crop set to Original and Rotate at 0 degrees. It reported a 640 × 360 download, but the browser download listener returned no saved file within 25 seconds. The inspection export and the normal download attempt are different results: a built-in original-photo download was not verified. No edited version was saved to the album.
For a wedding archive, keep the camera originals separately and test the chosen service’s original-file download. Compare dimensions and, when an unchanged copy is promised, the checksum against the source. A sharp-looking thumbnail or a playable finished video cannot establish that archive.
The dated guest submission and review example records the contribution and correction steps. A normal archive-download workflow and complete video handoff remain unverified; the original-file comparison above does not establish those outputs.
Step 8 of 8
Hand off a small, understandable archive
Keep verified originals, working copies and the selected wedding edit in separate folders. Record who supplied an older picture, approximate dates and any sharing limits. A useful handoff might contain “Originals”, “Working”, “Couple selection” and a short file index.
Make a separate backup in a destination the couple controls, and test opening a few files there. A second folder on the same device does not protect against losing that device. Agree who will keep access to the collection and when the link should be locked.
For the creative next step, choose a wedding video structure or a printed album. The collection is successful when the couple can find and use the memories they wanted, even if most files never appear in a video.
For a celebration spread over several days or places, the destination wedding memory-map plan shows how to turn the approved collection into a journey from arrival to the farewell gathering.
Finish line
Route complete: 8 steps
Need to check something again? Jump straight back to any stop.
- 1Choose the collection you want to keep
- 2Set up the organizer side before printing a sign
- 3Explain what the guest will do
- 4Use a short reception sign and one reminder
- 5Review the files without turning the wedding into a sorting project
- 6Check files, plan limits and storage as separate questions
- 7Compare a preview with the file you uploaded
- 8Hand off a small, understandable archive
Helpful answers
Frequently asked questions
Do guests need an AlbumMap account?
No account or installed app is required for a guest contribution. The organizer must sign in and save the album to create its contribution link. Anonymous editing later depends on returning from the same browser.
Can guests browse all the wedding uploads?
The AlbumMap contribution page is for sending and managing the guest’s own submission. It does not expose other guest submissions or let guests edit the organizer’s main project.
Does the QR code protect the upload link with a password?
No. It opens the contribution URL. Share that link with the intended people; interactive-map viewer passwords belong to a separate sharing feature.
Does a video download replace the original-photo archive?
No. Check whether your collection method provides the original-file retrieval you need, preserve verified originals separately and make a separate backup.
