The host promised Wi-Fi. On event day, the booth is set up in a vaulted cellar, the password doesn't work, the router sits two floors up, and by 9pm there are 180 phones on the same network. That's not an edge case — it's the normal case for roughly one event in three.
So the question that actually matters isn't whether a photo booth needs the internet, it's what keeps working without a connection, what just waits, and what genuinely fails. Cleanly separating those three categories saves you most of the scares on event day.
What keeps working without a connection
The entire capture path belongs in this category, and it needs to stay there: triggering the shot, the countdown, the camera, layout, filters, greenscreen background removal, the local preview and printing. All of that computes on the event PC. Software that has to ask a server for the countdown or the layout has no business at an event.
The QR code on the printout can also be generated offline — in the end it's just a pattern made from a string. Whether the guest finds anything behind it is a separate question, covered below.
The practical test: during setup, unplug the network cable and switch off the Wi-Fi. If a complete session including printing still runs, the capture path really is local. If not, at least you know before the event, not during the ceremony.
What just waits
Uploading to the gallery belongs here — provided the software has a durable queue. The distinction matters: an in-memory queue disappears after a restart or a crash, along with every photo that hadn't gone up yet. A durable queue writes every session to disk and works through it as soon as there's a connection again — even after a power outage, even the next morning.
At BoothDock, the Windows wrapper holds this queue, not the browser part of the app. That's a deliberate choice: the capture path is allowed to crash without taking the not-yet-uploaded photos down with it.
What that means for you on event day: the evening carries on as normal, guests get their prints, and the gallery fills in later — on the drive home over mobile data, or at home on your own connection. The only real downside is the guest who scans the QR code that evening and sees nothing yet. Tell them that up front, and it's information, not a complaint.
What really fails
Without a connection there's no live gallery for guests, no email delivery, no remote support, and no current booth status in the cloud. That's unavoidable — those features are the internet.
So plan for a backup path that doesn't depend on someone else's Wi-Fi: an LTE stick or a phone as a hotspot on the event PC. Photos need very little bandwidth; uploads run in the background and can take their time. A second, independent path to the internet costs a few euros a month and replaces hoping for the venue's Wi-Fi with something you control yourself.
The thing almost nobody checks: the licence
This is the risk that never shows up in a quote. Many programs check on startup whether the licence is still valid — and if the server doesn't respond, they refuse to run. That's the failure that really hurts: the technology is fine, the camera is cabled up, the printer is full of paper, and still nothing works, because a server in another country can't be reached.
Ask every vendor two things, and get both in writing:
- How long does the software keep running without a connection? It should be a number of days, not a phrase like "usually not an issue."
- What happens once that period runs out? A lockout or a restriction? That difference decides whether a missed sync costs you the event or just means a watermark.
At BoothDock, the event PC keeps running offline for 30 days after the last successful sync. If that period runs out, the booth isn't locked: it keeps capturing and printing, but adds a watermark to the image until contact with the hub is restored. That's a deliberate decision — software that stops working on someone's wedding night because nobody was online for four weeks does more damage than any watermark ever could.
And if the software crashes?
The second classic problem: nobody is standing next to the booth. The host is dancing, you went home hours ago, and at some point a process hangs. Without supervision, it stays hung until someone notices — in the worst case, the next morning.
A local watchdog process solves this — in product terms it's called a watchdog, and you should ask vendors about it by that name. It watches the guest-facing process and restarts it automatically if it disappears. The upper limit matters too, or a reproducible bug turns into an endless loop: at BoothDock, the watchdog gives up after ten crashes within 30 minutes and reports it instead of continuing to restart. A booth that restarts itself every twenty seconds isn't a running event — it's a failure that needs to reach you.
The checklist for choosing a vendor
- Does a complete session including printing work with the network cable unplugged?
- Does the upload queue survive a restart of the event PC?
- How many days may the booth run offline — as a number?
- What happens once that period runs out: a lockout or a restriction?
- Is there a watchdog that restarts the guest-facing process on its own after a crash — and that eventually gives up instead of looping forever?
- Can you see remotely whether a booth isn't reporting in — and since when?
These six questions take five minutes and separate software built for events from software built for good Wi-Fi.