GalleryVault Start an event

Phone photos got beautiful. They also got heavy.

Every camera upgrade in your pocket is also a storage problem, and events are where it shows up.

Published · 8 min read

The cameras in ordinary phones got remarkably good over the last several years. High-end handsets moved from twelve-megapixel main sensors to forty-eight-megapixel ones, with some Android flagships going considerably higher, and video moved from 1080p being normal to 4K at high frame rates being normal.

All of that quality is stored as bytes, and the bytes went up with it. This is the quiet reason collecting event photos is more awkward than it was a few years ago.

Roughly what things weigh

Exact sizes depend on the phone, the scene and the format, so treat these as orders of magnitude rather than precise figures:

  • A twelve-megapixel photo in a modern compressed format: around 2 to 3 MB.
  • A forty-eight-megapixel photo in the same format: around 5 MB, sometimes more.
  • A forty-eight-megapixel photo in a raw format, which the pro modes encourage: on the order of 75 to 100 MB each.
  • 4K video at 30 frames per second: roughly 170 MB per minute.
  • 4K video at 60 frames per second: roughly 400 MB per minute.
  • Professional-grade video formats on a phone: multiple gigabytes per minute.

A nuance worth knowing, because it explains why people's estimates are so far off: on many phones the default photo is still around twelve megapixels even though the sensor can do forty-eight. The larger files only appear when someone has turned the high-resolution mode on. At an event with a hundred guests, some of them have.

An event's worth of arithmetic

Take a wedding with a hundred and fifty guests. Suppose a third of them upload, and each of those fifty people contributes twenty-five photos averaging 4 MB. That is 5,000 MB, so roughly 5 GB, from stills alone.

Now add video, which is where the real weight is. Forty one-minute clips at 4K60 is roughly 16 GB on its own. A few people shooting longer clips, or in a raw or professional mode, can add another ten gigabytes without anybody noticing.

So a well-attended wedding where guests actually participate lands somewhere in the tens of gigabytes. Not hundreds of megabytes, which is what people guess.

Why messaging apps are not the answer

Chat apps solved this problem by destroying the files. When someone sends you a photo through a messaging app, it is usually recompressed hard and often scaled down, which is why a photo that was 5 MB arrives as a few hundred kilobytes and looks fine on a phone screen and falls apart the moment you try to print it or crop into it.

That is a reasonable trade for a conversation and a terrible one for an archive. If the only copy of a singleton photograph reaches you through a chat app, the good version is gone. And singleton photographs are the ones most worth having.

A chat app is a way to show someone a photograph. It is not a way to give someone a photograph.

What this means for collecting

Three practical consequences. First, video dominates the total, and GalleryVault collects photos only for now, so plan for clips to live somewhere else. Second, know the ceiling: each photo can be up to 500 MB in JPEG, PNG, WebP or AVIF, which covers any high-resolution shot; raw files are not accepted, because of their format, not their size.

Third, get your copies out while access is open. The whole collection comes down as a ZIP, in parts of up to 500 photos when it is large. Either way keep a copy somewhere you control, because access windows close and your own drive does not.

The upside of all this weight is real, though. The photographs your guests take now are good enough to print, which was not true of phone cameras a decade ago. That is precisely why it is worth the trouble of collecting them properly rather than letting them arrive as chat-app mush. It is also why sharing the gallery back is worth doing at full quality.

Keep reading

For your kind of event