An upload failed

The file is too large

Each kind has a fixed ceiling and it has nothing to do with the guest s phone. A photo may be 25 MB and a voice note 50 MB, on every plan. For video the ceiling follows the plan, from 480 MB on the free tier to 9.4 GB on Grand.

What is checked is the real file on the server, not the size the phone declares. A device that misreports does not get through on that basis.

1. Look at the size. Photos may be 25 MB, voice notes 50 MB, videos from 480 MB to 9.4 GB depending on the plan.
2. Check the format. JPEG, PNG, WebP and HEIC for photos; MP4, MOV and WebM for video. Renaming does not help.
3. Send it again. For a dropped connection a second attempt is enough, ideally on mobile data rather than venue Wi-Fi.

Only video meets a ceiling in practice. Photos and voice notes never get close.

With video, length is the real limit

Alongside the file size there is a permitted recording length, and it comes from the event plan: 30 seconds free, then 5, 10 and 15 minutes. That limit bites on the guest page itself, before anything is sent.

Someone sending a longer clip from their camera roll hits the size instead of the duration. Both end the same way, and both are solved by a shorter clip.

The format is not one we read

We take what phones produce: JPEG, PNG, WebP and HEIC for photos, MP4, MOV and WebM for video, and M4A, OGG, WAV or WebM for voice notes. HEIC is the iPhone default and needs no conversion.

The file is checked at its header rather than its extension, so a renamed file does not get through and a corrupted one is caught in the same place.

The album is out of space

Every plan carries storage: 5 GB free, then 50, 100 and 250. Once it is used up the event refuses further files even though nothing is wrong with them, and the guest reads that the album has run out of space.

On the free tier a second limit applies: 60 contributions, checked at the door as well. If you expect a lot of video, changing plan before the party is cheaper than tidying up after it.

The connection dropped

An upload that breaks mid-way leaves nothing behind. The guest sees no confirmation and the file does not appear in your dashboard, because it never fully reached the server.

At a party this is the purely technical cause most likely to bite. A room of phones sending at once reaches a guest network s limit before it reaches ours, so the advice that works is: turn Wi-Fi off and send again.

The 3 rarer messages

Too many uploads just now means the per-guest rate limit, which allows 60 files a minute — a wait of a few seconds clears it. This event is not accepting uploads means the window is closed or the event is still a draft. And your browser cannot open this photo means an old format the phone stores but cannot render.

For the last one the page suggests the fix itself: take a screenshot of the picture and upload that.

What you can do beforehand

Run a test upload with a borrowed phone before the codes go on the tables, and include a video. You will then know whether your plan matches what your guests intend to send, rather than finding out during the evening.

When a guest reports a problem, ask for the kind of file and its length first. Those 2 answers narrow the cause to 1 sentence.