Wedding QR code not working—or guests not uploading?

Use a phone that is not signed into the host account and follow the printed instructions exactly. Choose one ordinary photograph rather than a large batch. Note the last step that works: code recognition, page opening, event access, file selection, upload completion or gallery viewing.

That sequence narrows the problem quickly. A sign that scans correctly does not need redesign because a video is too large. A photograph hidden by a viewing setting has not necessarily failed to upload. Keep the original file on the guest's device while you investigate, and avoid repeated mass retries.

Check the printed sample, not only the digital design. Look for blur, low contrast, a damaged pattern, glare or a code printed too small for the expected distance. Leave clear space around it and test under the venue's actual lighting.

Try opening the encoded destination from an ordinary link. If that works, the issue is likely in the physical scan route rather than the gallery. Provide the link as a temporary fallback. Do not cover the sign with decorative elements or stretch the code while attempting a quick fix.

Inspect the destination carefully. It may point to an old event, a preview, an administrator screen or a page that no longer accepts contributions. Ask the host to copy the supported guest link from the correct event and test it independently.

A static QR code does not change merely because you edit text beside it. If the encoded link is wrong and you cannot control a legitimate redirect, replace the code itself. Check table cards, welcome signs and digital messages together so guests are not directed to several competing destinations.

Check whether the phone has a usable internet connection. Venue Wi-Fi may require a sign-in page, and a signal indicator does not guarantee a working route to the internet. Try the link on another permitted connection and see whether other guests experience the same problem.

Do not ask guests to disable important device protections or provide private account credentials as a workaround. If the venue connection is the obstacle, let them keep the photographs and use the link later. A calm explanation is more useful than repeatedly refreshing the page during the reception.

Ask the host to check whether uploads are enabled and whether the event is within its permitted upload window. A gallery can remain viewable after contributions close. If there is a password or access gate, confirm that the invited guest has the correct details.

Also check the specific route: a photo-only camera mode is not necessarily the general photo-and-video uploader. A guest looking for video contribution may be on the wrong screen. Explain the correct entry point rather than promising that every button accepts every media type.

Read the error message and compare the file type and size with the service's limits. PhotosPlease currently accepts photos up to 30 MB and videos up to 100 MB; these limits may change. Use the limit shown by the actual service.

Keep the original. If a clip is too large, make a shorter copy for the album or arrange another appropriate handover. Renaming an unsupported file extension does not change its contents. PhotosPlease checks the file's content type rather than trusting the name, so a misleading extension is not a solution.

Ask the host to inspect the event collection before asking the guest to resend. Moderation, gallery visibility, a scheduled reveal or the plan's upload allowance can affect what people see. In PhotosPlease, uploads over the plan's allowance are stored but held back for the host; the guest still sees a success confirmation.

A future film-roll reveal hides the guest gallery and slideshow until the reveal time. It is not proof that the image disappeared. Distinguish visibility from storage, then address the relevant setting or plan. Do not tell guests their files are lost without checking the host view.

Check the invitation. Did guests notice the sign, understand its purpose and know who would see the photographs? Were they asked during a convenient moment? A working system can still receive few uploads when the request is unclear or everyone is occupied.

Send one considerate follow-up with the direct link and an accurate deadline. Ask for a few favourites rather than the whole camera roll. Some guests will not have photographs or will prefer not to share, and that is not a technical fault to fix.

Record the time, affected device, last successful step and exact message shown. Include whether the same file worked on a different connection and whether another guest could contribute to the same event. These observations can help distinguish a single-file problem from a broader access issue without collecting unnecessary personal information.

Do not put passwords, private event links or unrelated photographs into a public support thread. Use the provider's appropriate private contact route and share only what is needed to investigate. A cropped screenshot of an error may be useful, but check that it does not reveal other guests' media or personal details.

Once the issue is resolved, repeat the one-file guest test and confirm the host result. Update the invitation only if the instructions changed. Tell affected guests whether their earlier contribution is already safe or whether a specific resend is needed. That final confirmation avoids a second wave of duplicates caused by uncertainty rather than another technical failure.