Collecting and Organizing Graphics References
Reference is not inspiration. It's a working tool. The difference is that inspiration can be sought chaotically, but a working tool must be organized so any team member can use it when needed.
Most teams gather references haphazardly: a folder with pictures, a Pinterest board without categories, several PureRef files in different artists' folders. This works for a solo developer and stops working as soon as there's a second artist on the team.
Why Poorly Organized References Cost Time
Concrete situation: art director found the right reference for lighting during pre-production, but didn't record it in the shared system. Three months later, a texture artist does a set of assets with completely different light character—because the reference was only in the art director's head. Result: rework or compromise that blurs the style.
Another scenario: outsource artist receives a brief and asks for additional references. The team spends two hours finding "that exact" screenshot that was already collected but is nowhere to be found.
Organizing references solves both scenarios—but only if done right.
How Professional Reference Base is Built
Work starts with an audit of what exists. Random folders, Pinterest links, Slack screenshots—all inventoried and assessed: what's useful, what's outdated, what contradicts the chosen direction.
Category structure. Hierarchy not by "source type" (screenshots/photos/art), but by usage: lighting, color and palette, materials and surfaces, characters (by type: heroes, enemies, NPCs), environments (by biomes or zones), UI, VFX, animation and motion. This allows finding the needed reference by task, not by source.
Annotations. Bare pictures are bad references. Good reference is a picture with a note: what exactly in it is relevant. "Use: shadow character from foliage, ignore: character style." Without annotation, an artist can take something wrong from something right.
Versioning and relevance. Reference base should update as decisions are made. References that were "under consideration" and rejected—not discarded, but moved to archive with a note why. This prevents the same discussions from coming up three months later.
Tools: PureRef as primary workspace for visual collage, Notion or Confluence for structured storage with annotations and search, Google Drive / shared folder for large teams, Milanote for visually organized board. Tool choice depends on team size and existing workflow.
Collection process. Organizing references is not a one-time task. It's a process: who can add, how validation passes (art director or lead artist should coordinate additions to main base, otherwise it turns into chaos), how often revision happens.
For projects that go outsourcing: reference pack is an official document given to the contractor. It must be self-contained: an artist seeing the project for the first time should understand visual style just from it.
Timeline
Initial collection and organization for a project in active pre-production: 1–2 weeks. Full audit and reorganization of existing base for a project in production—3–5 days. System and process development for a team with subsequent handoff: additionally 2–3 days.
Cost is calculated after assessing scope of existing materials and requirements for final structure.