Folders or Tags for Reference Images?
Folders answer "where does this file belong?" Tags answer "how might I want to find it?" You can use both without copying an image into a folder for every subject it contains.
Give folders a stable job
Organize by a shoot, source pack, project, or another context unlikely to change. A photograph can remain inside its original shoot folder even when you later use it for a lighting study.
Keep a folder's purpose clear. A tree mixing clients, colors, favorite artists, and approval states at the same level becomes hard to predict. Choose one organizing principle at each level. In refern, a folder can also hold named links, such as the source pack's page or the project brief.
Use tags across those boundaries
The same photograph might receive stone, arch, and side-light tags. Another project folder can contain images with those tags too. Search can bring the relevant entries together without requiring a second copy in a "side light" directory. In refern, a folder toolbar search can be pinned so it stays applied as you change folders, or saved as a smart folder.
Use hierarchies to organize a vocabulary when useful, but check how the app's filter matches parents and children. The visual tag tree and a specific saved query are different things. In refern, adding a tag writes only that tag unless you turn on parent tags, and browsing a tag in the Tag Hierarchies sidebar can include every tag below it.
Decide with a small example
| Question | Likely home |
|---|---|
| Which shoot supplied the original? | Folder plus source record |
| Which images show backlighting? | Tag |
| Which references belong on this project board? | Canvas selection or project tag |
| Which images need source review? | A no:source search, or a clearly defined status label or tag |
| Which set should update as metadata changes? | Smart-folder rules |
These are suggested roles, not a required taxonomy. Test them on one real project before reorganizing your archive.
Understand what the software saves
In refern, ordinary workspace indexing reads existing folders in place. Imports and copy operations can create files. Linked copies can represent one physical source in several placements, but they share media and metadata; use independent files when you actually need separate versions.
Tags and other organizing work are workspace data. They are not automatically embedded into each original image. Back up both the media and the workspace's data location.
Change only what is getting in the way
If you can already find a reference, do not rebuild the tree just to make it look systematic. Add a tag when you miss a cross-folder search. Rename an ambiguous folder when it repeatedly causes confusion.
For implementation steps, use tagging, smart folders, and workspace setup.