We tested 6 wedding photo apps with the same wedding
I make WeddingQR, one of the apps in this test.
We tested six apps in the western US on November 12, 2026. Each speed result is the median of 5 runs. On November 17 we repeated the guest upload-button test for GuestCam and WeddingQR. See the November 17 timings.
The apps and plans: WeddingQR (a paid gallery on our test account, with no storage connected), GuestCam (the $49 Standard plan with its $45 MagicFind add-on), Kululu (free), Wedibox (free), Joy (free) and POV (free). Kululu's host dashboard was measured on an event on its Plus plan. The upload time, photo quality and bad connection tests come from a trial run the day before, with one reported run each. Each card names the plan tested.
What we learned from the test galleries
Scanning a code, picking photos and finishing an upload are three different waits. In the November 12 test, opening the picker took 1 tap on WeddingQR and 2 on Wedibox. GuestCam asked for a name before the picker, and Kululu showed an iPhone conversion prompt. We timed the steps the guest actually took, including those prompts.
A quick first screen didn’t always mean a quick upload. In the single poor-connection trial, Kululu finished sending our three photos in about 25 seconds. WeddingQR, GuestCam and Wedibox took about 45 seconds. On downloads, the GuestCam photo we checked and the three files we retrieved from Dropbox matched the originals. Each result below identifies the plan tested.
How fast the guest page opens
Each card shows a simulated mobile visit to a small test gallery. Lighthouse scores cover performance, automated accessibility checks and browser best practices. The timings below them show when the main content appeared, when the upload control worked and how much data the page loaded.
The indexing row records whether we saw a request for search engines to omit the page. We checked on November 11, with GuestCam rechecked on November 17. Hosts who need to restrict access should check the gallery’s entry controls.
The upload button time comes from separate timed visits at iPhone size, on the same slow connection. A tap that does nothing doesn't count: the clock stops at the first successful tap on the upload control. For GuestCam, that includes navigating its welcome screen and automatically filling its name step. This measures the path to the control, not just when a button becomes interactive. See the test conditions and individual timings.
How long it took to choose photos on November 17
We opened each gallery in a fresh browser, followed the guest steps to choose a photo, then revisited the link in the same browser profile. We repeated this five times per app on the same GitHub-hosted Ubuntu 24.04 runner, alternating which app went first. Chrome emulated an iPhone 15 with 150 ms latency, 1.6 Mbps down, 750 Kbps up and a 4× CPU slowdown.
Each time below starts when the guest link opens. We recorded when a tap on Upload first advanced the flow and when the system file chooser opened. For GuestCam, the first visit included its welcome screen and an automatically filled name. Returning guests kept their existing session.
| App and visit | Working upload button (median) | File chooser open (median) |
|---|---|---|
| GuestCam, first | 6.1 s | 6.4 s |
| GuestCam, returning | 1.6 s | 1.7 s |
| WeddingQR, first | 0.6 s | 0.6 s |
| WeddingQR, returning | 0.4 s | 0.4 s |
All 20 visits completed and counted. On first visits GuestCam's upload button worked in 5.9–6.7 seconds. Four WeddingQR visits took about 0.5–0.6 seconds and one took 4.8 seconds. The November 12 round used a residential connection and a different computer, so compare the apps within each round.
Download the individual measurements (JSON) or run the same test on your own galleries (scripts and instructions, ZIP).
November 12 score cards
A guest's first visit
WeddingQR
Paid plan- Main content shows
- 3.8 sMiddle half: 3.5 s to 4.0 s
- Upload button works
- 0.4 sMiddle half: 0.4 s to 0.4 s
- Data loaded
- 709 KBMiddle half: 709 KB to 710 KB
- Asks search engines to omit page
- Yes
GuestCam
Paid plan- Main content shows
- 12.8 sMiddle half: 11.9 s to 12.8 s
- Upload button works
- 9.3 sMiddle half: 9.2 s to 9.5 s
- Data loaded
- 1.8 MBMiddle half: 1.8 MB to 1.8 MB
- Asks search engines to omit page
- Yes
Joy
Free plan- Main content shows
- 13.0 sMiddle half: 13.0 s to 13.2 s
- Upload button works
- Missing
- Data loaded
- 2.6 MBMiddle half: 2.6 MB to 2.6 MB
- Asks search engines to omit page
- Yes
Kululu
Free plan- Main content shows
- 17.4 sMiddle half: 17.4 s to 17.4 s
- Upload button works
- 16.1 sMiddle half: 15.8 s to 16.6 s
- Data loaded
- 2.5 MBMiddle half: 2.5 MB to 2.5 MB
- Asks search engines to omit page
- Yes
Wedibox
Free plan- Main content shows
- 35.7 sMiddle half: 35.4 s to 36.2 s
- Upload button works
- 27.8 sMiddle half: 27.8 s to 28.1 s
- Data loaded
- 6.1 MBMiddle half: 6.1 MB to 6.1 MB
- Asks search engines to omit page
- Yes
Coming back later
The same phone opening the page a second time, with what the browser kept from the first visit.
WeddingQR
Paid plan- Main content shows
- 1.0 sMiddle half: 1.0 s to 1.0 s
- Upload button works
- 0.4 sMiddle half: 0.4 s to 0.4 s
- Data loaded
- 32 KBMiddle half: 32 KB to 33 KB
- Asks search engines to omit page
- Yes
GuestCam
Paid plan- Main content shows
- 2.2 sMiddle half: 2.1 s to 2.2 s
- Upload button works
- 1.2 sMiddle half: 1.2 s to 1.2 s
- Data loaded
- 14 KBMiddle half: 14 KB to 14 KB
- Asks search engines to omit page
- Yes
Joy
Free plan- Main content shows
- 3.0 sMiddle half: 2.9 s to 3.0 s
- Upload button works
- Missing
- Data loaded
- 131 KBMiddle half: 130 KB to 131 KB
- Asks search engines to omit page
- Yes
Kululu
Free plan- Main content shows
- Missing
- Upload button works
- 2.7 sMiddle half: 2.6 s to 3.3 s
- Data loaded
- Missing
- Asks search engines to omit page
- Yes
Wedibox
Free plan- Main content shows
- 2.2 sMiddle half: 2.2 s to 2.2 s
- Upload button works
- 1.8 sMiddle half: 1.8 s to 2.0 s
- Data loaded
- 16 KBMiddle half: 16 KB to 17 KB
- Asks search engines to omit page
- Yes
POV
POV's QR link opened a page on POV's own website in our phone browser, which asks guests to get the app. We measured that page and show it on its own, since it isn't a gallery page.
POV
First visit, Free plan- Main content shows
- 14.4 sMiddle half: 14.3 s to 14.5 s
- Upload button works
- Missing
- Data loaded
- 2.5 MBMiddle half: 2.5 MB to 2.5 MB
POV
Coming back, Free plan- Main content shows
- 4.8 sMiddle half: 4.8 s to 4.9 s
- Upload button works
- Missing
- Data loaded
- 428 KBMiddle half: 427 KB to 429 KB
The host dashboard
This is the page where the couple sees the photos, loaded the way a computer on a fast connection would load it (Lighthouse's desktop setting). The first visit is signed in with the browser's saved files cleared. Coming back is the next load in the same browser. We don't link these reports, because they show the signed-in account.
First visit
WeddingQR
Paid plan- Main content shows
- 0.9 sMiddle half: 0.9 s to 0.9 s
- Data loaded
- 993 KBMiddle half: 993 KB to 993 KB
GuestCam
Paid plan- Main content shows
- 2.5 sMiddle half: 2.4 s to 2.5 s
- Data loaded
- 2.0 MBMiddle half: 2.0 MB to 2.0 MB
Joy
Free plan- Main content shows
- 5.5 sMiddle half: 5.1 s to 5.5 s
- Data loaded
- 5.1 MBMiddle half: 5.1 MB to 5.1 MB
Kululu
Paid plan- Main content shows
- 3.0 sMiddle half: 3.0 s to 3.1 s
- Data loaded
- 2.3 MBMiddle half: 2.3 MB to 2.3 MB
POV
Free plan- Main content shows
- 3.6 sMiddle half: 3.6 s to 3.6 s
- Data loaded
- 5.6 MBMiddle half: 5.6 MB to 5.6 MB
Wedibox
Free plan- Main content shows
- Missing
- Data loaded
- Missing
Coming back
WeddingQR
Paid plan- Main content shows
- 0.3 sMiddle half: 0.3 s to 0.3 s
- Data loaded
- 66 KBMiddle half: 66 KB to 66 KB
GuestCam
Paid plan- Main content shows
- 0.7 sMiddle half: 0.7 s to 0.7 s
- Data loaded
- 22 KBMiddle half: 22 KB to 22 KB
Joy
Free plan- Main content shows
- 1.3 sMiddle half: 1.0 s to 1.3 s
- Data loaded
- 164 KBMiddle half: 164 KB to 164 KB
Kululu
Paid plan- Main content shows
- 0.6 sMiddle half: 0.6 s to 0.8 s
- Data loaded
- 52 KBMiddle half: 52 KB to 52 KB
POV
Free plan- Main content shows
- 0.4 sMiddle half: 0.4 s to 0.4 s
- Data loaded
- 20 KBMiddle half: 19 KB to 20 KB
Wedibox
Free plan- Main content shows
- Missing
- Data loaded
- Missing
Taps to upload
We counted every tap, typed field and screen from opening the QR link to the moment the phone's photo picker opens. Each count was the same in all 5 runs. Some apps ask for more after the photos are picked, as the notes below the table say.
| App | Taps | Typed fields | Screens | Taps coming back |
|---|---|---|---|---|
| WeddingQR | 1 | 0 | 1 | 1 |
| GuestCam | 4 | 1 | 4 | 1 |
| Kululu | 4 | 1 | 4 | 2 |
| Wedibox | 2 | 0 | 2 | 2 |
| Joy | No upload button for guests on the free plan | |||
| POV | Not counted: guests upload through POV's app | |||
- WeddingQR opens the picker from the first button. It asks for the guest's name after the photos are picked, so guests type one field there.
- GuestCam asks for the guest's name first, then shows an iPhone tips sheet before the picker.
- Kululu asks for the name first, then shows a “Using iPhone?” notice that makes the guest wait 5 seconds before it can be closed. That's why its picker opened at 22.4 s, well after its button worked.
- Wedibox asks for nothing before the picker. After picking, the guest taps Next and then Upload.
Joy guests can only look at photos on the free plan. POV sends iPhone guests to a small piece of its app called an App Clip, and Android guests to a web version (POV's business page, checked November 2026). We didn't test either one.
Upload time
A new guest sent the same 3 photos (730 KB together) on the same slow mobile connection. The clock ran from choosing the photos until the app said they were in. GuestCam shows no “done” message, so its clock stopped when its “Optimizing” message went away.
| App | 3 photos | Notes |
|---|---|---|
| WeddingQR | Not measured | We didn't run this test on WeddingQR's test gallery. The bad connection tests below include WeddingQR. |
| GuestCam | Not counted | This run doesn't count under our rules: the test computer got too busy during it. |
| Kululu | 6.1 s | |
| Wedibox | 12.3 s |
These test photos are small. Photos straight from a phone are much bigger, so expect longer times at a real wedding.
Quality kept
As the host, we downloaded photos back and compared them with the files the guest sent: one photo each from WeddingQR, GuestCam and Kululu, and all 3 from Dropbox. “Same file” means every byte matched.
| App | Same file? | Size | File name |
|---|---|---|---|
| WeddingQR | Yes, 1 photo | 240 KB | Maria_rooftop-flash.jpg |
| GuestCam | Yes, 1 photo | 274 KB | park-sunset.jpg |
| Kululu | No, a smaller file at the same width and height | 117 KB of 216 KB (54%) | Maria_2026-11-11_02-14-00_hv89sg.jpg |
| Dropbox | Yes, all 3 photos | 216 KB274 KB240 KB | birthday-flash Maria.jpgpark-sunset Maria.jpgrooftop-flash Maria.jpg |
- WeddingQR gave a ZIP of originals. Each file name starts with the guest's name.
- GuestCam was tested with one photo, downloaded from the host gallery. The downloaded file matched the original and kept its filename.
- Kululu (free plan) sent a ZIP with a smaller copy of the photo under a new name, plus a second copy with a caption on it. Kululu says its paid plans keep the original quality. We checked that on a Plus event on November 12, outside the timed tests: Download All gave back all 3 photos byte for byte, plus a captioned copy of each.
- Dropbox (a file request) gave all 3 photos in one ZIP, each with the guest's name added to the end of its name.
- Joy (free plan) said Download all would email a download link. Joy’s plan table describes free downloads as web-sized copies.
- Wedibox wasn't tested: our saved host sign-in had run out. Its plans page says the free plan has no original-quality ZIP (checked November 2026).
- POV wasn't tested.
We compared file contents and filenames. The three source photos contained no capture date or location.
A bad connection
Wedding venues often have weak signal, so we tried three bad moments with the same 3 photos:
- Signal drops: the phone goes offline for 15 seconds right after the first photo starts sending.
- Poor connection: a very slow, laggy line for the whole upload.
- Page closed: the phone goes offline mid-upload, the guest closes the tab, and opens the link again 2 minutes later with signal back.
We took the page itself offline. A background helper some web apps use (a service worker) keeps its connection in this kind of test. The guest never pressed anything after the problem started. We counted the photos in each gallery before and after.
| App | Signal drops | Poor connection | Page closed |
|---|---|---|---|
| WeddingQR | Count unclear. Another test upload to the same gallery ran at the same time, so we can't tell how many of these photos arrived. It showed “Uploads paused after a connection problem”, then “All photos failed to upload” with a retry button, and did not try again by itself. | 3 of 3 arrived. Done in 46.3 s*. | Not measured. The test script could not finish this run. |
| GuestCam | 0 of 3 arrived. It showed “Some of your uploads have failed. Do you want to retry them?” and did not try again by itself. This run doesn't count under our rules: the test computer got too busy during it. | 3 of 3 arrived. Done in 43.7 s. | 0 of 3 arrived. Nothing on the reopened page said what happened. |
| Kululu | 3 of 3 arrived. It kept “Keep this page open” on screen and carried on by itself when the signal came back. It said the upload was done 5.4 s after the signal came back. This run doesn't count under our rules: the test computer got too busy during it. | 3 of 3 arrived. Done in 25.1 s. | 0 of 3 arrived. Nothing on the reopened page said what happened. This run doesn't count under our rules: the test computer got too busy during it. |
| Wedibox | 0 of 3 arrived. It showed an error, then “Thank You!” and “3 photos uploaded” while the phone was still offline. | 3 of 3 arrived. Done in 44.8 s. | 1 of 3 arrived. Nothing on the reopened page said what happened. |
* The test script was looking for WeddingQR's old success message, which had just changed to “3 photos added to the gallery”. This time is read from the run's own record of the screen.
WeddingQR's page-closed test didn't run. WeddingQR asks “Is this you?” when a new guest types a name an earlier guest used, and our test guest's name was already in the gallery. The sheet was taller than the phone screen, so the script couldn't reach “No, that's not me”. We didn't test POV's guest uploads or Joy's paid guest uploads.
What we changed after this trial, before round 1: WeddingQR now tries again by itself when the signal comes back (November 11). It keeps trying for about two and a half minutes before it asks the guest to tap Retry. And “No, that's not me” now stays on screen however many photos the earlier guest sent (November 12). We haven't run these bad connection tests again since, so the table shows WeddingQR as it was in the trial.
What else loads on a guest's phone
On November 12, 2026 we opened each guest link in a fresh phone browser and listed every other company the page contacted before the guest tapped anything. For WeddingQR we used our public demo gallery. This was from a US connection. None of the pages showed a cookie banner during those US visits.
- WeddingQR contacted only weddingqr.app and Cloudflare's web analytics. No advertising or remarketing tags and no third-party cookies. Our own check on November 12 found three problems, and we fixed all three the same day. Our analytics (PostHog) recorded how guests used the page and set a cookie that lasted a year. Now guest pages send only anonymous usage counts, with no recording and no analytics cookie. A guest who downloaded another guest's photo got a copy that still showed where it was taken and which phone took it, and the original files could be opened by their address. Now guests get copies with the location and phone details removed, and only the gallery's hosts can open the original files.
- GuestCam, rechecked November 17: the test gallery's landing page loaded Intercom chat, Cloudflare web analytics and a media-player resource. We observed no Google Ads, Meta pixel or PostHog requests. GuestCam says it removed advertising scripts from the guest portal. This was one fresh US browser visit, not every interaction or region.
- Kululu loaded Google Ads, Mixpanel, Sentry, Intercom and Rewardful on the free guest gallery.
- Wedibox loaded Google Ads, Google Analytics, Microsoft Clarity and Microsoft Advertising on the free guest gallery.
- Joy loaded Google Analytics, Microsoft Advertising, Pinterest and New Relic.
- POV's landing page loaded Google Ads remarketing, Google Analytics and Mouseflow, and set a Meta cookie.
Remarketing tags can support advertising audiences; observing a tag doesn't establish how a company uses the data or why it included the script. In the November 12 captures, Kululu and Wedibox sent the gallery's link to Google, and Joy sent the album's link to Pinterest.
Where photos are kept and how to export them
A gallery’s hosting window determines how long guests can return to it. A download or a copy in your own drive can outlast that window. Plan details below come from the linked vendor pages.
WeddingQR
- Guests can upload without a connected drive. If you connect Google Drive, OneDrive or Dropbox, originals copy to your account in a folder for each guest, including earlier uploads. Those copies are yours to keep and use space in that account.
- You can download every original in one ZIP. The photo we checked matched the original exactly.
- No face scanning.
- Asked search engines to omit the page: yes.
GuestCam
- Photos are kept on GuestCam's own cloud storage in the U.S. You can't connect your own storage.
- Standard ($49 per event): guests upload for 6 months, and photos are kept for 12. Premium ($97): 12 months to upload, kept for 14. Its dashboard shows a last day to download and says “Files are deleted after this day.” GuestCam says it automatically delivers downloadable backups and sends advance expiration reminders.
- Every plan can download all photos and videos in one ZIP, in original quality.
- MagicFind is an optional $45 add-on that searches event photos by face. GuestCam says facial information is isolated by event and associated data is deleted at storage expiration or on a host's explicit event-removal request. See our GuestCam review.
- Asks search engines not to index: yes. Our November 17 check found noindex and nofollow directives on the test gallery. They don't restrict who can open the link; GuestCam also offers an entry code.
- Sources, checked November 2026: pricing, security and privacy.
Kululu
- Photos are kept on Kululu's servers, on Google Cloud.
- Free: guests can upload for 24 hours, and photos are kept 7 days. Plus ($39): kept 3 months. Pro ($99): kept 1 year. After that they're removed. Kululu's privacy policy says it emails you at least 30 days before deleting your data.
- Download all is on Plus and Pro only, as one ZIP of originals. Free hosts can download photos one at a time or a few at once, at reduced quality (54% of the file size in our test).
- Asked search engines to omit the page: yes.
- Our Kululu review covers the $39 Plus plan we paid for: what guests see, what it deletes and when.
- Sources, checked November 2026: pricing, data safety, download all, privacy policy.
Wedibox
- Photos are kept on Wedibox's own servers.
- Free: 50 uploads. Wedding ($49): 6 months to upload, kept 1 year. All-In-One ($79): 1 year to upload, kept 2 years.
- When storage ends, Wedibox says the gallery is archived, with a warning 7 days before. Its help says to download while storage is still active, and to extend storage to get access back.
- The download-all ZIP is on Wedding and up, “at the size each file was uploaded”. Its help page also says large files are made smaller during upload so they finish on venue wifi.
- Asked search engines to omit the page: yes.
- Our Wedibox comparison has what other guests' phones were sent in our test.
- Sources, checked November 2026: pricing, plans compared, pricing comparison, when storage ends, download all, how uploads work.
Joy
- Photos are kept on Joy's own cloud. Joy's FAQ says they're stored in high resolution.
- Joy's plan page inside the app (checked November 2026): the free plan keeps full-quality photos for 3 months after the event, and guests can only look. Plus ($39.99) adds guest uploads, up to 1,000 items, 1 month to upload and 6 months of storage. Premium ($79.99) allows 2,000 items, 3 months to upload and 12 months of storage.
- On the free plan, Download all sends an emailed link, and Joy calls the free downloads web-sized copies (see Quality kept above).
- Asked search engines to omit the page: yes.
- Sources, checked November 2026: FAQ, Joy in ChatGPT.
POV
- Photos are kept on POV's own servers in the U.S.
- POV says photos don't expire from your gallery. Its terms also say it can delete content at any time, with or without notice.
- You can download the full gallery from POV's website.
- Asked search engines to omit the page: there's no gallery page to check. The QR link opened a page on POV's own website.
- Sources, checked November 2026: business page, terms, privacy.
Dropbox file requests
- Files go straight into a folder in your own Dropbox. Guests don't need a Dropbox account. The free Basic plan holds 2 GB.
- Files stay as long as your account does. Dropbox may close a free account after 12 months with no sign-in or file activity, after several reminder emails.
- Select all and Download gave one ZIP of the original files in our test.
- Asked search engines to omit the page: yes.
- Sources, checked November 2026: file requests, inactive accounts, Basic plan, MCP server.
- What guests and hosts see: our Dropbox file requests review.
How we tested
- Every app hosted the same small wedding, “Emma & Noah's Wedding”, with the same 3 guest photos and, where the app has one, the same cover photo. GuestCam's gallery also held a fourth photo we used to try its face search. POV's photos live in its app, so its web pages had none. Our own gallery was set up the same way, on our live site, and we didn't warm it up before the tests.
- Speed: Lighthouse 12.8.2 in Chrome on an Apple M2 MacBook in the western US. Guest pages used Lighthouse's phone setting, which copies a mid-range Android phone with a slowed-down processor on a connection of 1.6 Mbps down and 750 Kbps up. Timed visits used Chrome with Playwright's iPhone 15 emulation (393 × 659 viewport), with 150 ms network latency, 1.6 Mbps down, 750 Kbps up and 4× CPU slowdown applied through Chrome DevTools Protocol. These desktop emulations are not measurements on real phones.
- Round 1 ran on November 12, 2026, with the apps in a shuffled order and 5 runs of each page and visit. We show the middle result. Where the timings differed between runs, the card shows the middle half of them.
- We checked how busy the test computer was before each app's runs and watched it during every run. Runs where it got too busy didn't count and were taken again. So were runs where Lighthouse failed. Every run that didn't count is kept in our raw data.
- Kululu's host dashboard was measured right after the round, at the same settings. The saved sign-in for our free Kululu test account had run out, so we measured the dashboard of an event on Kululu's Plus plan in our own Kululu account. The dashboard is the same page on both plans.
- Our trial run the day before found a bug in WeddingQR: the upload button showed before it worked. We fixed it before round 1, so round 1 measured the fixed page. The trial also gave the upload time, quality and bad connection results above.
- Our raw data also has blocking time, layout shift, request counts and script sizes for every page. We left them off the cards to keep them easy to read. You can also download the November 12 GuestCam and WeddingQR upload-control timings for first and returning visits, including step timings, throttling and recorded exclusions. Private gallery links and machine identifiers are omitted.
- What this doesn't cover yet: real phones, other parts of the world, wedding-sized galleries with hundreds of photos, and measurements across many different days. Apps also change, so these results are for November 2026.