
Count the files and their size
Leave enough room for wedding clips as well as photographs
Wedding photo and video storage planning has two tests: do the files fit the photo and video counts, and do their combined sizes fit the storage allowance? A collection can pass one and fail the other. Start with a few representative files, then make a deliberately cautious estimate rather than treating every photograph or clip as the same size.
Treat the collection as three separate allowances
The number on a guest list is not a storage estimate. One person might send two images; another might send a long, high-resolution clip. Paid plans do not impose a contributor-number ceiling, but the photographs, videos and bytes they contribute are still limited. Write down those three allowances separately. This prevents a generous-looking photo count from concealing a storage constraint, or spare storage from being mistaken for permission to exceed the video count.
- Photo count
- Count the photographs you are asking people to send, including contributions expected after the reception. If you request a selection from each household, use that request as an estimate rather than multiplying every seat by an arbitrary large number. A count is a ceiling, not a target that guests must fill.
- Video count
- Estimate ordinary clips and any recorded video contributions you intend to collect. Short messages are still video files. Check the event's actual usage as contributions arrive rather than assuming a guestbook feature gives you a separate, unbounded source of storage or an independent unlimited video allowance.
- Combined storage
- Add the sizes of the photo and video files you expect to receive. Both occupy space in the same event allocation. One large clip can use more space than a whole selection of pictures, so a plan based only on photo count leaves the most variable part of the estimate unexplained.
Take a small file sample before choosing an average
Use file information from pictures and clips similar to the ones you expect, not the dimensions of a thumbnail on a screen. A guest's phone settings, file format, video duration and recording quality can change the size substantially. The sample does not predict what everyone will send. It gives you a defensible starting point and shows whether your first assumption was much too small.
Ask for representative examples
Use a few ordinary photos, a short indoor clip and a longer outdoor clip from willing helpers. Avoid collecting private files just to measure them. You can inspect sizes on their own devices and record the numbers without uploading anything to the wedding collection.
Record a range, not one convenient file
Write down a smaller, middle and larger example for each media type. If one phone produces much bigger clips, keep that observation in the estimate rather than discarding it as inconvenient. It may represent exactly the relative who plans to record an entire speech.
Connect the assumption to the request
If you ask for brief highlights, estimate brief highlights. If you invite complete speeches, use samples with comparable duration and settings. Changing the wording from a short moment to the whole performance can change the storage problem even when the expected video count stays the same.
Round cautiously and revisit later
Use a larger plausible file size when you are uncertain, then revise the estimate after early contributions arrive. Do not treat a tiny compressed image received in a message as representative of a file chosen directly from the guest's phone library.
Work through one small mixed collection on paper
The following arithmetic uses hypothetical file sizes, not measured product averages or promised compression. For readable scratch calculations, 1,000 MB is treated as approximately 1 GB. Package storage is enforced in bytes, so these rounded decimal estimates are not exact entitlement calculations. This page is a planning walkthrough, not an upload-size calculator. Check the live collection's remaining allowance before relying on a close fit.
- Photographs
- Suppose you expect 180 photos and, purely for this example, allow 5 MB per photo. Multiply 180 by 5 to get 900 MB. The 5 MB assumption is not a statement about a normal phone image; substitute the sizes you observed when making your own plan.
- Clips
- Suppose the same example includes 20 videos at a hypothetical 80 MB each. That is 1,600 MB for video. Adding the photo estimate gives 2,500 MB, or roughly 2.5 GB in this simplified arithmetic. Notice that the smaller number of videos takes more space than the photographs.
- Compare all three results
- Gather includes 200 photos, 30 videos and 5 GB, so the example is below each stated ceiling with room in the estimate. It is not a guarantee that 180 real photos and 20 real clips will fit. Larger actual files could change the storage result without changing either count.
- Keep the working assumption visible
- Write the assumed sizes beside the total instead of keeping only the final 2.5 GB figure. If relatives start sending much larger clips, you can change one input and see why the estimate moved. A bare total hides the assumptions that make it useful.
Recognise two different ways to run out of room
Spare bytes do not cancel a count limit, and spare count does not cancel a byte limit. These two hypothetical failures are useful because they look different in practice. One needs attention to the number of files; the other needs attention to their sizes. Diagnosing which constraint matters is more useful than repeatedly telling a guest to retry the same batch or buy an unrelated extra.
The count fails while the size looks comfortable
- Imagine 260 photos at a hypothetical 4 MB each and 20 videos at a hypothetical 40 MB each. The arithmetic is 1,040 MB plus 800 MB, roughly 1.84 GB in total.
- That estimated storage is below Gather's 5 GB, but 260 photographs exceed its 200-photo allowance. Having space left does not make those extra photographs fall inside the included count.
- Review the photo request or the available photo allowance. Do not diagnose this as a connection problem simply because the total file size appears small.
The size fails while the counts look comfortable
- Imagine 150 photos at a hypothetical 8 MB each and 20 videos at a hypothetical 250 MB each. That is 1,200 MB plus 5,000 MB, approximately 6.2 GB.
- The counts sit below 200 photos and 30 videos, but this hypothetical volume exceeds Gather's 5 GB allocation. The long or large clips change the outcome without increasing the number of contributors.
- Review storage and the kind of material you are collecting. An add-on described as extra uploads raises a count; do not assume it also buys enough bytes to solve this example.
Choose headroom against the current package limits
A plan that fits only your smallest estimate is fragile. Leave room for a guest returning from travel, a longer clip you decide to keep or a set of photographs you forgot to include in the first request. There is no single correct margin for every wedding. Choose it from the uncertainty in your sample and how important it is to accept later contributions without changing your original plan.
- Preview for a small rehearsal
- The free package includes 20 photos, zero videos, 10 contributors, 500 MB and seven days online, with no downloads. It can test a few photo uploads, but it cannot test a real video contribution or serve as a downloadable mixed-media archive.
- Gather for a limited request
- USD 19 once per event provides 200 photos, 30 videos, 5 GB and one month online, with standard downloads and a written guestbook. Use both your expected file numbers and their estimated total size when deciding whether that is sufficient.
- Celebrate for a broader collection
- USD 39 once per event provides 750 photos, 100 videos, 20 GB and three months online, with original-quality downloads, a video guestbook and slideshow. Hypothetical totals of 600 photos at 6 MB and 80 videos at 140 MB reach about 14.8 GB, not an assurance about real files.
- Keepsake for more capacity and time
- USD 69 once per event provides 2,000 photos, 300 videos, 50 GB and six months online, with original-quality downloads and two extra managers. Larger allowances still need checking. A small number of very large recordings can make storage the governing limit even here.
Ask for a useful selection without turning guests into editors
Your invitation is part of the capacity plan. Asking for every frame and every recording creates a different workload from asking for favourite moments. Guests should not have to perform a technical conversion project before contributing, but they can choose between several nearly identical pictures. Make that request kindly. The purpose is to collect a varied account of the wedding, not to turn the remaining storage indicator into a competition.
Request variety before volume
Ask for moments the couple might have missed: a conversation between tables, a greeting outside or a detail from the room. A handful of different perspectives can be more useful than a burst of nearly identical frames. This is an editorial choice, not a claim that the software sorts duplicates for you.
Be specific about video length
Say whether you want a short highlight or an entire speech. If the full recording matters, plan for its actual size and a suitable connection. Do not ask somebody to discard an important original merely to force it into an estimate you made before considering that recording.
Keep originals outside the upload attempt
Ask guests to retain their chosen files until the upload is confirmed. The stored file is the one they send, so a compressed copy selected from a messaging conversation does not become a higher-quality original later. Select the source intentionally when quality matters.
Send manageable batches
A smaller first batch makes it easier to identify a failed transfer and confirm what arrived. It does not bypass a limit or guarantee that later batches will fit. Keep checking the actual result rather than assuming every file selected in the picker has already reached the collection.
Keep transfer time separate from storage capacity
A collection can have plenty of space while a guest's connection is too slow for a large clip. Equally, a fast connection cannot solve a full allocation. Treat a stalled upload as a question to investigate, not evidence of one particular cause. Read the page's message, check whether any files succeeded and preserve the original files while you decide what to try next.
- Confirm that the guest is using the correct event link and that submissions are still open. An expired or closed collection is a timing issue rather than a file-size estimate gone wrong.
- Check the event's current photo count, video count and storage use. Do not rely only on a spreadsheet prepared before the first contributions arrived.
- For a connection issue, let the guest try again later on a reliable connection. A QR code gives them the destination; it does not provide connectivity or store a queue of files offline.
- Keep the browser page open until the upload finishes and inspect the result before resending everything. Blindly repeating a whole successful batch can complicate the collection you are trying to assemble.
- If the file itself is unsuitable, follow the actual error guidance or ask for help. Do not promise that changing the filename or splitting a batch will make every format or size acceptable.
Plan the space needed after the event closes
Online storage is only one part of keeping the collection. Before downloading, check the free space on the device receiving the archive and decide where a separate backup belongs. An archive may need space both for the downloaded file and for extracted contents, depending on how you handle it. Leave working room rather than matching the available disk space to a rough media estimate with no margin.
Choose the download quality deliberately
Gather provides standard downloads. Celebrate and Keepsake provide original-quality downloads, while Preview has no downloads. If your keeping plan depends on the files as submitted, make that choice before the wedding rather than discovering the distinction at the final handover.
Verify the saved collection
Open a selection of photos and videos from the downloaded archive, including a larger clip and a file contributed late. Check that the files are readable rather than only checking that a download finished. Keep the archive and any separate backup in locations you can identify later.
Separate an extension from a backup
Six more months online costs USD 9 and twelve more costs USD 15, starting at the existing expiry. Extra time does not increase the collection's storage allocation and is not a second independent copy. Decide whether you need more online access, more local space or both.
Storage questions the headline photo count cannot answer
Is there a fixed number of megabytes per wedding photograph?
No. File sizes vary with device settings, format and the particular file. All sizes used in these examples are hypothetical; inspect representative files and leave room for larger ones when making your own estimate.
Can unused video places become extra photo places?
Do not treat the allowances as interchangeable. The plan states separate photo and video counts alongside storage. Choose the right named allowance rather than assuming unused capacity of one kind transfers to another.
Does a slideshow duplicate the capacity I should budget?
Do not invent a second full collection in your estimate merely because you display the existing photographs. Plan around the submitted media and check actual usage. Equipment and connectivity for the room display are separate practical concerns.
Does hiding the gallery free storage?
No. Gallery visibility controls guest browsing, not the size of uploaded files. A collection used only for receiving contributions still needs enough photo count, video count and storage for what arrives.
Make a capacity estimate you can explain
Write down expected photo and video counts, the hypothetical sizes you used and a larger-file alternative. Compare all three allowances, then choose a download and backup plan. A few visible assumptions are more useful than a precise-looking total with no connection to the files your guests will send.
How it works
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.