Using Google Drive or Dropbox for group photos

A shared folder is where most groups start, and it deserves more respect than it usually gets. Drive and Dropbox keep your originals untouched, the privacy model is clear, and everyone already knows what a folder is. What breaks is not the storage. It is that a file manager is a terrible place to look at photos, and an even worse place to ask thirty people to put them.

What a shared folder gets right

Be clear about this before replacing it, because these are the properties that matter most and plenty of purpose-built photo apps fail them:

• Your originals stay originals. No re-encoding, no downsizing, no surprises three years later.
• Privacy is legible. A folder is shared with specific people or it is not. There is no feed, no algorithm, and nothing is learning from your library.
• No lock-in. It is just files. Dragging them somewhere else is a drag-and-drop, not a migration project.
• Everyone owns a copy of the mental model. You do not have to teach anyone what a folder is.

If your group is five organized adults who all use laptops, a shared folder may genuinely be the right answer and you can stop reading.

Where it quietly fails

Phone uploads are the real blocker. This is the one that kills it. Getting photos from a phone’s camera roll into a specific subfolder of a shared Drive takes six or seven taps through a share sheet, and the person has to pick the right folder from a list of folders. Multiply that by forty parents, most of whom will try once. The archive ends up holding photos from the three people who are good at computers.

Browsing is grim. Thumbnails in a grid of filenames is not how anyone wants to revisit a season. There is no slideshow worth putting on a TV, swiping through on a phone is awkward, and IMG_4207.HEIC tells you nothing about what it is.

Nobody names anything consistently. Without structure imposed by the tool, you get Fall 2026, fall season, Season Photos FINAL, and New folder (2). Your own homepage problem, in miniature.

Permissions confuse people. Drive’s sharing model has edge cases that trip up experienced users, let alone the grandparent you are trying to include. “Anyone with the link can edit” is one misclick from a public archive, and “request access” emails pile up on the organizer.

Permissions are per person, not per group. Drive lets you make parents editors and the alumni list viewers, and that works. But every new family means adding people one by one or sharing a link, and editors can rename or remove each other’s files. There is also no way for someone to ask for a photo of their kid to come down, short of emailing whoever runs the folder.

Duplicates multiply. When three parents upload the same tournament and someone adds the group-text export on top, you get four copies of the same moment and no tool that notices.

Drive versus Dropbox versus Google Photos

Worth untangling, because people conflate them. Drive and Dropbox are file storage: originals preserved, poor photo browsing. Google Photos is a photo product: good browsing and search, but built around one person’s library, and contributions to a shared album count against each contributor’s own quota. Drive and Google Photos are separate products with separate storage behavior even though they share an account, which is a common source of confusion when a group thinks it is doing one and is doing the other. See Fika vs Google Photos for groups.

The middle ground groups actually want

Most groups want the folder’s properties with a photo product’s interface: originals kept intact, membership that is obvious, contributing that takes two taps from a camera roll, and something pleasant to browse years later. That combination is the whole reason a group photo service exists as a category.

In Fika, collections do what folders were doing, but the structure is part of the product rather than a naming convention you have to enforce. Invite your members once and contributing is two taps from the camera roll in the phone app. Roles separate contributors from view-only family. Duplicate detection catches the four copies of the same tournament. Originals stay at full quality, and downloading a whole collection gives you a zip of real files, so the no-lock-in property you liked about the folder is still there.

If you are migrating from a folder

Do it in one pass rather than gradually, or you will run both for a year. Make the collections first so there is somewhere for things to land, upload the existing folder contents from a computer by dragging them in, then invite the group and point them at the new place. Leave the old folder read-only for a season as a safety net rather than deleting it on day one. Groups that keep both “just in case” indefinitely end up with half an archive in each.