Photo capture and printing don’t need an internet connection at all – only sharing does. But even sharing doesn’t need a connection at the time of the event – which changes the practical answer more than it first appears.
What genuinely needs a connection – eventually
Email, SMS, WhatsApp, Facebook posting, and cloud upload destinations (Dropbox, Google Drive, FTP, the online gallery) all need the booth PC to reach the internet at some point – see our support section for the general troubleshooting steps when they don’t.
Booth Junkie doesn’t need that connection to exist at the event itself, though. Every share request is stored in the Upload Queue, and the software sends everything through the moment a connection becomes available – whether that’s ten minutes later or the next morning back at the office. A completely offline event isn’t a failure state: guests can still request their photo by email, SMS, or social share exactly as normal, and the software simply holds the request until it can be delivered.
An unexpected upside of delayed delivery
Sending shares the next day isn’t just a fallback for bad venue wifi – some operators do it deliberately, even when a connection is available on-site. At an evening event with a lot of alcohol involved, such as a wedding, guests are usually caught up in the moment and don’t pay much attention to what’s on the photo beyond themselves. A photo (or the email/SMS it arrives in) that lands the next morning gets a second look with a clearer head, when the operator’s branding on the print, the digital image, or the message itself actually gets noticed. A guest with fond memories of the night before who can immediately see who supplied the photo booth is far more likely to reach out for their own event than one who scrolled past a photo half-distracted at 11pm.
The failure mode that looks like a connection but isn’t
Many venues run guest wifi behind a captive portal – a browser page guests have to log into or accept terms on before the connection actually works. A booth PC connecting to that network shows as “connected” at the OS level, but nothing actually reaches the internet until that browser login is completed, which nothing running headless on a booth PC can do.
Technically, a captive portal works by intercepting outbound requests before they reach their real destination and silently redirecting them to its own portal page instead. So when Booth Junkie (or any other software) tries to reach an email server or a cloud upload API, it doesn’t get a straightforward connection failure – it gets a response back, just not the one it was expecting: usually the portal’s own login page where an API reply should have been. From the software’s point of view, that’s not a recognisable error, so it can fail in confusing ways rather than with a clear “no internet” message.
Even where a captive portal has already been logged into once, many are configured to automatically time the session out – typically anywhere from five minutes to half an hour – unless they detect an actual user actively browsing a page. A background upload from a booth PC doesn’t look like that kind of activity, so a session that was working fine at the start of the night can silently drop and stop working again later, with nothing on the booth itself having changed.
Captive portals also commonly sit behind a restrictive firewall that only allows standard web browsing and email traffic through, and blocks everything else. This can affect more than just photo sharing: if a booth is set up to print over the network rather than via a direct USB/local connection, that same firewall can block the print traffic too.
What to actually do about it
Booth Junkie’s recommendation is straightforward: never rely on a venue to provide your internet connection. Bring your own – a dedicated mobile hotspot device is ideal, or the hotspot feature built into your own mobile phone is a perfectly good alternative if you don’t have a dedicated device. A professional photo booth operation should be self-sufficient wherever possible, rather than depending on infrastructure you don’t control and can’t troubleshoot on the night.
And if a connection genuinely isn’t available – your own hotspot included – remember that this isn’t the failure it might first appear to be. The Upload Queue means guests can still be offered every sharing option as normal; the images will simply be delivered once a connection is available, whether that’s later that night or the next day.