A network plan for the reception
Plan guest uploads around the connection your venue has
The venue says Wi-Fi is included. That is the start of a conversation, not a complete plan for wedding photo sharing on venue WiFi. Find out how guests join, where the connection reaches, and what happens when a room full of phones starts sending files. A small practical test can expose problems while there is still time to change the instructions.

Ask the venue about access, coverage and ownership
Speak to the person who understands the guest network, not only the person arranging the tables. A venue may have separate networks for guests, staff, payment equipment, and audiovisual systems. Your invitation should name the one guests are allowed to use. Ask who can help during the wedding if access stops working and whether that person will actually be on site. The couple should not discover at dinner that the only person with the network details left after the ceremony. Record the answers in the event run sheet rather than relying on a remembered conversation.
Questions to settle during the venue visit
- Joining
- What is the exact guest-network name? Is there a shared password, an individual voucher, a room-number requirement, or a browser sign-in page? Can day guests join without being overnight residents? Ask for instructions you are permitted to reproduce.
- Reach
- Does coverage extend to the reception tables, terrace, ceremony space, and projector position? Thick walls and detached rooms can make the experience uneven. Ask where a reliable test should be performed, then also test where guests will actually sit.
- Restrictions
- Are there per-device limits, access timeouts, or restrictions on large uploads? Does the venue reserve bandwidth for essential services? Do not assume that permission to browse a menu also means the network is intended for many simultaneous camera-file uploads.
- Responsibility
- Who can investigate a portal problem or an outage on the day? Agree how the guest helper contacts that person without interrupting the couple. Network changes and access exceptions belong to authorised venue staff, not an improvised guest workaround.
Test a newcomer joining from the beginning
A staff laptop that has been connected for months is not a good substitute for a newly arriving guest. Test with a phone that has not already completed the venue's access process, where practical, and follow the same instructions a guest would receive. Do not erase browser data from a phone with unfinished uploads just to manufacture a clean test. Use another device or ask the venue how to test the sign-in journey safely. The goal is to observe access, not to remove useful recovery information from someone's existing browser.
Choose the official guest network
Read the network name carefully and verify it with staff. Avoid similarly named networks that might belong to nearby businesses or personal hotspots. If credentials are required, use only those supplied for guests and keep staff-network details off public signs.
Complete the captive portal
Watch for the phone's sign-in notification or the venue's browser page. Accept the applicable terms and complete legitimate required fields. If the page does not appear, ask staff for the approved way to open it instead of bypassing security checks or inventing a login address.
Prove general internet access
Open a fresh ordinary web page. Seeing an old page that was already loaded can be misleading because the browser may be showing cached content. A connected Wi-Fi icon proves association with a network, not successful access to the wider internet.
Open the wedding guest link
Confirm that the correct event appears and that the upload form is usable. Guests use a browser with no event app, account, or password required. If the venue itself asks for a Wi-Fi password, explain that it is a separate network-access step.
Send a representative file all the way through
Page loading is only part of the test. Sending a photograph uses the upstream connection and reaches services that an ordinary browsing check may not exercise. Choose a harmless image, submit it through the guest page, and wait for the result. Ask the host to locate it in the collection. If approval is switched on, check the review area rather than concluding that an absent gallery thumbnail means the transfer failed. Use an image everyone involved is comfortable testing with; there is no reason to upload a private family picture during a technical rehearsal.
Record a complete test result
- Note the room, approximate time, phone, browser, and network name. Record whether venue sign-in was needed and whether the guest instructions were enough to complete it without staff assistance.
- Write down whether the camera decoded the QR, whether the event page opened, and whether the chosen file reached a completed result. These are distinct stages and may fail for different reasons.
- If videos are part of the invitation and available on the event, test a modest representative clip as well. A successful tiny image does not demonstrate that every large video will be practical on the same connection.
- Ask the host to confirm receipt and the expected visibility. If a room screen is planned, use its own authorised address and device for a separate display check.
- Record the conditions honestly. A test in an empty afternoon room is useful evidence, but it does not guarantee the same performance during a full reception.
Walk the guest route rather than trusting signal bars
Coverage should be checked along the route people will actually take. A strong connection at reception may fade in a stone-walled dining room or outside on the terrace. Signal bars describe the phone's radio link, not the available upload capacity or the reliability of the venue's internet service. A short practical check from each important space is more useful than declaring the whole property connected after standing beside an access point. Work with staff so tests do not obstruct setup or interfere with equipment networks.
- Arrival and welcome sign
- Check that guests can stand safely near the sign without blocking the entrance. If this is the only well-connected spot, do not encourage a crowd to remain there uploading large selections. Make the link easy to keep and allow people to contribute later.
- Dining tables
- Try the guest route from a table near the edge of the room as well as from the centre. Place instructions where people can read them without reaching across plates. If coverage varies, brief the helper rather than claiming every seat will work equally well.
- Terrace or separate room
- Treat another building or outdoor area as its own test location. A phone may cling to a weak network instead of moving to a better connection. Let the guest choose whether to wait or use mobile data; do not change their settings without permission.
- Display position
- A projector laptop may sit in a technical corner that guests never visit. Test that exact position and any permitted wired connection. Good Wi-Fi at the tables does not prove the display computer can stay connected at the back of the room.
Make room for ordinary network contention
Guests share the venue connection with other activity. Video calls, cloud backups, supplier work, and another function in the building may all affect capacity. You do not need to calculate a precise number of uploads per minute to plan sensibly. Avoid inviting the entire room to send its largest videos at the same instant, and do not turn photo sharing into a race. A reminder that people can select a few favourites now and send the rest later reduces pressure on both the network and the guests.
Use a quiet invitation
Put the link on tables and mention it at a natural pause rather than demanding an immediate upload during a speech. People can contribute when their phones and connection are ready. There is no need to interrupt the meal to prove participation.
Keep test traffic modest
A helper should not keep sending large files just to see whether the network has recovered. Recheck access with a small test when useful, then observe actual file messages. Too many duplicate tests can consume collection capacity without giving better evidence.
Do not sell storage as speed
A larger event package changes allowances and included features, not the venue's upstream connection. Check capacity when an upload is refused, but do not tell the couple that buying more storage will make a weak wireless link faster.
Protect essential venue operations
Do not move guests onto a staff or payment network to improve photo sharing. Ask the venue for a permitted alternative or accept later contributions. Wedding pictures matter, but they should not compromise the services keeping the event running.
Write network instructions guests can follow once
Keep the venue-access instruction separate from the event invitation. Otherwise guests may think that a Wi-Fi password is an account password for the collection, or that scanning the wedding code automatically joins the wireless network. It does neither. One instruction gets the phone online; the other opens the guest page. If the venue has a complicated portal, ask for a concise official explanation rather than copying an old instruction from another wedding. Check that day visitors can actually supply any details the portal demands.
A simple instruction hierarchy
- Connection line
- Use wording such as: 'Need internet? Join the venue guest network shown here and complete its sign-in page.' Include credentials only if the venue has authorised you to display them. Keep confidential technical information off stationery.
- Collection line
- Follow with: 'Scan our wedding code or open the address below to send your chosen photographs.' Explain that the event opens in the browser without an app or account. The camera recognising the QR and the page loading are separate steps.
- Completion line
- Ask guests to keep the upload page open until it confirms the file result. A selected picture or local preview is not proof of delivery. If the browser reports a failed file, the helper can read that message rather than asking for another scan.
- Later option
- Say: 'If the connection is busy, keep your pictures and use this same link later while our collection is open.' This gives guests permission to return to the celebration without implying that an unfinished upload will complete offline.
Keep a live room screen on its own checklist
The guest network plan and the room display plan overlap, but neither proves the other. Guests send files through the contribution page. The live display uses a separate token-protected /s/<slug>/slideshow address, opened on the machine connected to the screen. Give that full authorised link privately to the operator. Do not publish its token in guest instructions, and do not show the host dashboard on the projector while investigating connectivity. The display computer needs its own successful connection and content test.
- Ask whether the venue offers a permitted wired connection at the display position. If so, test it with the actual laptop and adapter. A cable is not proof of internet access until the browser check succeeds.
- Rehearse a newly accepted photograph reaching the live display, not only an image that was already loaded. A picture remaining on screen does not prove that new contributions can arrive during an outage.
- Agree who can blank the projector if the page shows an error or private information. Keep host controls on a separate device where possible, with a clear operator hand signal or contact route.
- Prepare an approved holding image or a decision to leave the screen blank if connectivity fails. This is an external contingency, not an offline slideshow or video-streaming guarantee from the service.
Treat any remote viewing request separately. A working reception screen is not a promise of remote broadcast, and a successfully uploaded video does not establish a live streaming service. Keep expectations aligned with the browser collection and the equipment you have actually tested.
Choose a fallback before a connection is lost
Options that can help on the day
- A guest may choose mobile data if reception, allowance, and roaming costs make sense. Ask before changing networks, especially while files are already transferring.
- A venue-approved alternative connection may be suitable for the display machine or helper. Test it with staff and keep access details within the intended group.
- A private message containing the same guest link lets attendees return later. Keep the destination consistent so the couple does not have to chase files across several unrelated services.
Assumptions to leave out
- Do not promise offline upload or guaranteed delivery after a browser is closed. Guests should keep originals and deliberately revisit unfinished submissions on a working connection.
- Do not assume a personal hotspot has enough capacity for the whole reception. Its signal, data plan, battery, and permitted use all need consideration before offering it.
- Do not advise clearing browser data as a first fix. The uploader may have useful saved recovery state, and removing it cannot repair the venue's internet service.
After an outage, tell the helper what has changed and ask guests to inspect existing upload results before starting again. Keep any follow-up reminder within the collection's actual online period. Gather includes one month, Celebrate three months, and Keepsake six months; Preview lasts seven days. Those windows are planning limits, not a reason to rush everyone into using a poor connection during the wedding.
Venue connectivity questions worth answering plainly
Does no app mean no internet is needed?
No. Guests use the browser instead of installing an app, but opening the live collection and sending files still require internet access. A QR can be decoded without a connection while its destination remains unreachable.
Can the venue guarantee every guest upload?
A network test can show that the route works under the tested conditions, not guarantee every later file transfer. Device behaviour, file size, access restrictions, event limits, and reception load can all affect the result.
Should we announce the Wi-Fi password over the microphone?
Follow the venue's policy and consider whether everyone in earshot is meant to have it. Clear authorised written instructions are often easier to follow than a password spoken once. Never announce staff-network credentials as a shortcut.
What if guests refuse to join the venue network?
Let them choose mobile data or contribute later, if they want to. Photo sharing is optional, and a guest does not need to change their privacy preferences or accept an unwanted network connection to enjoy the wedding.
Plan around tested access, not a Wi-Fi logo
Take one phone through the real guest journey, record the result, and give the helper an authorised contact and a later-upload message. That is enough to make network limitations manageable without turning the reception into a technical exercise.
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.