The mechanics of the clip
Event video upload: how a guest's clip reaches your collection
Somebody filmed the speech on a phone in a hallway, and now it needs to be on your laptop at full size. This is the whole path that clip takes, including the four places it usually gets stuck.
What an event video upload actually is
A page in the browser on the phone that already filmed the thing. The guest chooses a clip, gives a name, presses send. There is no app, no account, no transfer cable and no message thread compressing the file to a quarter of its size.
That is the whole design, and it exists because the alternative is worse in a specific and well-known way. Video sent through a chat app is re-encoded, cropped, shortened, and then scattered across eleven conversations on devices that will be replaced within two years. Video sent to a collection is the file as the camera made it, stored with the sender's name against it, in one place that the host can download in a single action.
The parts that are easy to get wrong are not mysterious: the file has to be a format the page recognises, small enough for the ceiling on that collection, sent while the allowance still has room, and downloaded before the page reaches its closing date. Four things, and each one is a page below rather than a surprise on the evening.
The four minutes, from the guest's side
They open the page
A camera pointed at the code on the table, or the link in the message, or the address typed on a laptop later. Whichever route, it lands on the same upload sheet in an ordinary browser.
They choose the clip
The phone's own picker opens, so anything already filmed is fair game, including the six attempts and the one that is good. A clip can be recorded on the page as well, which suits a message; it does not suit a three-minute speech somebody already has.
They give a name
One field, remembered for twelve hours. The guest adding the second half of the dance floor an hour later is not asked to introduce themselves again, and the entries are grouped by who sent them.
They press send and the queue shows what is happening
Files go up one after another with the count visible, so a guest uploading six items sees which one is moving and which one the network has stalled on. A rejected file is named rather than silently dropped, which is the difference between a guest retrying and a guest giving up.
They leave the page
Nothing stays open and nothing needs finishing. An interrupted upload is not a problem for the collection, and a guest who sends three clips on the Tuesday after the event is doing exactly what the page is built for.
Which files the page accepts
- MP4
- The default from every Android phone and most cameras. Whatever the container, the content of the file is checked rather than trusting the name, so a mislabelled file is refused with a reason rather than landing as a broken tile.
- MOV
- What an iPhone records, including the higher-efficiency variants. Clips from the camera roll keep their orientation and their length, which matters more for a speech than for anything else.
- M4V
- The store-download container some older devices hand out. Accepted alongside MP4 rather than being refused for having the wrong extension.
- WebM
- The format a browser records in, which is why it is on the list: a clip filmed straight into the page comes back as WebM and has to be accepted by the same rules as a file from a camera.
- Photographs, in the same submission
- JPEG, PNG, WebP, HEIC, HEIF, GIF and AVIF go to the same page as the clips, with a 15 MB ceiling per still against 100 MB per video. One guest, one name, one mixed set of files.
How big is too big
Two separate limits exist and people confuse them. The first is per file: a single video upload is capped at 100 MB, roughly four minutes of phone footage, which covers any clip a guest will plausibly send and excludes the twenty-minute film somebody made in 2019. A still is held to 15 MB. The second is the storage ceiling on the collection, which is a total rather than a per-file number and is the one that surprises hosts, because video is heavy in a way photographs are not.
- Free preview
- 500 MB of storage and 20 photographs, with no video allowance at all. It is a photograph trial, not a video one.
- Entry package, nineteen dollars
- 5 GB of storage with 30 clips allowed. Ten minutes of phone video comfortably fills a gigabyte, so a wedding collecting speeches and dance-floor footage is a 5 GB conversation rather than a settled one.
- Middle package, thirty-nine dollars
- 20 GB and 100 clips, with original-quality downloads. This is the tier that a video-collecting event is actually buying.
- Top package, sixty-nine dollars
- 50 GB and 300 clips, twenty-four months online. A large wedding, a multi-day event, or a family that films everything.
When a clip ceiling is reached the collection stops accepting rather than quietly dropping, and the numbers can be raised: fifty extra clips for nine dollars, a hundred for fifteen, bought against the same event. Storage and clip count are the two constraints worth checking before a hundred guests are handed a link, and both are cheaper to fix in advance than to discover at half past nine on the night.
When the upload stalls, and what the guest sees
Hotel and venue wifi is the usual culprit
A congested conference network uploads a photograph happily and crawls on a two-minute clip. The queue retries on its own with a visible state, so the honest advice to a guest is to send the clips on mobile data rather than the venue network.
A backgrounded browser tab can stop the run
Some phones suspend a page the moment it leaves the screen. The guest who wants to send six clips should keep the page open until the count finishes, which is a line worth putting on the printed card.
A refused file says why
Wrong contents, too large, a type that cannot be uploaded here. The reason is shown against that file and the rest of the batch keeps going, so one bad clip does not take the submission with it.
Nobody is locked out by a failure
A guest whose upload did not finish can come back to the same address the following day and send it from their camera roll. Nothing about the page assumes the attempt happens inside the event.
Recording in the browser against uploading a file
Record on the page
- Nothing to find, nothing to choose: the camera opens and the message is made there.
- Suits a wish, a toast, a ninety-second note from an aunt.
- Short by design, which keeps the storage bill honest.
- Depends on the room's signal at the moment of recording.
- The guest cannot preview it properly before sending.
Upload from the camera roll
- Whatever was already filmed, at full length and original size.
- Suits the speech, the first dance, the three-minute office group film.
- Sent on the guest's own schedule, often the following morning.
- Uses the phone's picker, which everybody already knows how to use.
- Needs the file to sit inside the per-file and per-plan ceilings.
A collection that is good at both is the one that survives an event. The page does the message; the camera roll does the footage, and the guest should not have to decide which one they are bringing.
The host settings that decide whether a clip can arrive
- Video uploads allowed on the collection, which is a switch rather than a default you should assume.
- A clip ceiling that matches the event, or an upload pack added before the link goes out.
- Storage left, not merely clip count left.
- The guestbook switched on if you also want written or filmed messages.
- Submissions held until accepted, if the clips are a surprise for whoever the event is for.
- The gallery view closed, so contributors can send without browsing everybody else's footage.
Every one of these is on the collection settings, before the address is handed out. A guest meeting a page that cannot take their file is the failure that loses the clip permanently, because they will not try twice.
What the clip becomes once it lands
The file is stored as sent. A small preview is generated on the guest's phone during the upload so that the gallery page loads quickly for everybody else, and the original stays behind it: the tile you click in the gallery is the preview, the file in the archive is the recording. That split is the reason a collection of a hundred clips browses on a hotel network without anyone noticing it is full of video.
Clips and photographs sit in one timeline with the sender's name attached, so the horizontal film of the toast lives next to the formal portraits rather than in a separate app. Where the slideshow is part of the collection, those clips play on the room's screen in the same rotation as the stills, each held for a length you set, with sound as a switch rather than an accident.
Getting the video back out
Standard downloads come with the entry package and give you the collection as usable files. Original-quality downloads come with the two packages above it, which is the difference that matters for anything a family intends to edit, print from, or keep properly. Either way the archive contains the clips as they arrived, the photographs, the written messages and the names, taken down in one action rather than ninety save dialogs.
Take it in the first month. A collection has a closing date counted from the event, warning mail goes out before it arrives, and video is the part that is genuinely unrecoverable afterwards, because it is the file nobody forwarded and nobody else has.
The photographs are on four phones. The video is on one, and that phone gets replaced in eighteen months.
Questions about uploading event video
Can a guest upload a video without an account?
Yes. The link opens a page in their browser, they choose the file, give a name once, and send. Nothing is installed and no price is shown to a contributor.
How large a video can the page take?
A single upload is capped at 100 MB, about four minutes of phone video. A clip larger than that should be trimmed on the guest's own phone before it is sent, or filmed shorter in the first place.
Which formats work?
MP4, MOV, M4V and WebM. The content of the file is verified rather than the extension, so a file that claims to be one thing and is another is refused with a reason.
How many clips can one event collect?
Thirty on the entry package, a hundred at thirty-nine dollars, three hundred at sixty-nine, and more through upload packs of fifty clips for nine dollars or a hundred for fifteen.
Does video eat the storage allowance?
Yes, and quickly. Five gigabytes is the ceiling on the entry package, twenty on the middle one and fifty on the top, which is the number worth checking before a room full of guests is asked for footage.
Can I stop a clip appearing before I have seen it?
There is a switch on the collection settings, off by default, that holds new submissions until the host accepts them. Anything turned down stays out of what everybody else sees.
Do guests see each other's video?
Only if you leave the gallery view open. The contribution page can be set so a guest uploads and writes without browsing the rest of the collection.
What happens to the clips when the collection ends?
The page comes down and the archive you downloaded is what exists. Standard files are available on every paid package; the original quality comes with the two above the entry one.
Check the two ceilings before you print anything
Clip count and storage are separate limits, and a collection that has room for thirty clips can still be full of photographs. Look at both numbers before the address goes on a table, because the guest whose file is refused does not try again.
See what each package holdsLet the clip come from the phone that filmed it
Open a collection with video allowed, put the address where the phones already are, and take the download in the first month while the file sizes are still the only thing to argue about.
Video and guestbook messages
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.