A folder answers one question: where does this file live? A photo answers three or four: where it was taken, when, who is in it, and what you might need it for. The moment those answers disagree, the folder has to lose one of them.
That is not a reason to abandon folders. It is a reason to stop treating them as the only way to organise a library. Android gives you three separate mechanisms, and they do different jobs.
Why folders break down on a phone
Camera folders are a filing system invented by the camera, not by you. On a typical Android phone the library is already split across DCIM/Camera, Pictures/Screenshots, Download, WhatsApp Images and one folder per app that has ever saved an image. None of those are decisions you made.
The split gets worse when a photo belongs in more than one place. A receipt photographed at lunch is a work expense and a personal record. A photo from a family trip is Goa, 2026 and the people in it. A folder forces you to pick one and remember the choice months later.
The test is simple: if you have ever thought “which folder did I put that in?”, the folder is the problem. Search and tags are the two ways out.
What are tags, albums and collections on Android?
Three words that get used interchangeably, and should not be:
- An album is a folder as Android reports it — the bucket a file sits in. It is real, it is shared with every app, and it comes from where the file was saved.
- A tag is a label added by a gallery app, stored by that app rather than in the file. One photo can carry any number of tags, which is the whole point.
- A collection is a named set of photos, chosen by you. It behaves like a project folder that does not move the underlying files.
Folders and albums are one-to-one. Tags are many-to-many. Collections are a shortcut for “these ones, for now”.
How does ReelRoll handle tags and collections?
ReelRoll keeps tags in its own database, not in the photo’s metadata. Three things happen automatically or near-automatically:
Manual tags are applied from a photo’s tag sheet. They are normalised to lowercase and stripped to letters, digits and underscores, and capped at twenty characters, so #Goa Trip! becomes goa_trip. That is worth knowing before you build a vocabulary: spaces and punctuation will not survive.
Album-derived tags come from the folder name Android reports. ReelRoll splits the album display name into words, drops stop words, numbers and file extensions, and keeps up to two tokens. A folder called Goa 2026 yields goa; Camera yields nothing worth having. Videos also pick up video and reel, and every item carries reel as a fallback label.
Collections are named lists you create, rename and fill by picking several photos at once. They are stored separately from tags, and a collection’s name is what the item shows as its title while you are inside it. A collection is the closest thing to a folder, except the photos stay where they are.
Search then filters the library as you type, matching a photo’s tags, title and album name. Tap a tag chip and it becomes the query. That is the part that makes tags useful rather than decorative: the label is a filter, not a note.
What are the honest limits?
Tags belong to the app, not the file. If you switch gallery apps, or plug the phone into a laptop, the tags do not travel. There is no sidecar file next to the photo and no EXIF field being written. That is the trade for not letting an app rewrite your originals.
The current build also has limits worth knowing before you commit an evening:
- Tagging is one photo at a time. There is no multi-select tagging, so a 5,000-photo library is a collection job first and a tagging job second.
- A tag can be removed from an item, but there is no rename across the whole library. Pick the vocabulary carefully, because changing it later is manual.
- A tag removed from every photo still appears in the suggestion list; the row survives even when nothing uses it.
- Uninstalling the app can take the tags with it. The database is app-private, so Android’s backup may restore it, but the links are media-store ids and a restored library is not guaranteed to match. If a tagging scheme matters to you, export or back up before a reinstall or a phone change.
Those are real costs. They are also why the next section matters more than any feature list.
What tagging scheme actually survives?
The schemes that last are small, boring and decided in advance. Three axes cover most libraries:
- Who or what — people, pets, the subjects you actually look for. Keep this list under twenty tags and never invent a synonym.
goaandgoa_tripare the same tag with two names, and now search needs both. - Where or when — place and year. Album-derived tags do most of this for free if your folders are decent, so check what the automatic tags already say before adding more.
- Why you kept it — a small set such as
receipt,reference,document. This is the one that pays off years later, because it is the only axis the camera never records.
Everything else belongs in a collection. A trip, a renovation, a wedding you are assembling an album for — those are temporary sets with a beginning and an end, and they should not permanently clutter the tag vocabulary.
One more rule: do not tag screenshots. If a photo is a screenshot, it already has a folder and a filename pattern, and tagging it adds noise to every search.
What should you do with 10,000 photos?
Do not start at the beginning. The first photo in the library is the least likely to be looked at again.
Start with the last twelve months, because that is the part you actually browse. Tag by event, not by subject: the event is what you will search for, and the people are usually obvious once you have found the event. Build one collection for whatever you are working on right now — a trip, a gift, a house move — and let it expire when the project does.
Then stop. The goal is not a perfectly labelled archive. It is a library where a search for goa returns the trip rather than a folder you have to open and scroll.
If you are choosing a gallery to do this in, the comparison of Android gallery apps covers which ones tag locally, which keep tags in a sidecar, and which are really backup services. The short version: check where the tags live before you invest in them.