Art Reference for Indie Game Dev: Organize Your Library (2026)

By refern | Last updated: June 2026

TL;DR: Solo and indie game devs juggle characters, tiles, UI, and VFX references simultaneously. The move that saves hours is a single library split by asset type, per-feature moodboard canvases pulled from that library, and provenance links that trace finished art back to the references that inspired it. This guide shows exactly how to set it up.

Running a game solo means wearing every art hat at once. You are the concept artist, the environment artist, the UI designer, and the VFX animator. Reference organization that works for a 10-image character moodboard breaks down completely when you have three hundred tile variants, forty UI button states, and a half-dozen VFX studies all living in the same "references" folder. By the second sprint, finding anything takes longer than making it.

This guide covers a lightweight but scalable reference library structure for indie game devs, using refern as the organizing layer. The same ideas translate to any tool you prefer.

Before You Start: Choose Your Tool

The three tools indie devs reach for most often are Eagle, PureRef, and refern. Each has a different center of gravity.

Eagle genuinely wins on format breadth: 99 previews on Windows, 108 on macOS, including fonts, audio, and 3D. If you need to preview every format in one place, Eagle is the stronger library tool. PureRef is genuinely excellent as a focused overlay. If you paint in Photoshop or model in Blender and want references pinned on screen with transparent-to-mouse color picking, PureRef does that better than anything else. The complaint that drives devs away from PureRef is that it has no search and no tags, so once a board has hundreds of images you cannot find anything without scrolling manually.

refern positions itself as "the intersection of Eagle-style organization and a PureRef-style infinite canvas," to borrow a phrase from an alpha user. It runs on Windows, macOS, and Linux (Eagle has no Linux client), it never copies your files (Eagle copies every import into its library), and the canvas is a first-class feature alongside the library. It also has a relationship graph view that neither Eagle nor PureRef offers.

If you already use Eagle and are happy with it, you can apply most of this guide there. The folder structure and tag naming approach is tool-agnostic.

Step 1: Structure Your Library by Asset Type

Solo devs tend to dump everything into one folder or into per-game folders. Both patterns collapse at scale.

A more durable structure splits references by the kind of art asset they inform, not by the game project they belong to. Most reference images are reusable across projects. A good tile-set style reference is just as useful in game two as in game one.

Suggested top-level folder structure:

References/
  Characters/
    Human/
    Creature/
    Silhouettes/
  Environments/
    Tiles/
    Backgrounds/
    Props/
  UI/
    Buttons/
    HUD/
    Menus/
    Icons/
  VFX/
    Fire/
    Water/
    Impact/
    Particles/
  Color Palettes/
  Typography/
  Style Study/

In refern, point a workspace at your References/ folder. refern indexes every image in place without copying anything. The SQLite index and thumbnails live in a sidecar file alongside your originals. If you decide to switch tools later, your folder is untouched.

For pixel art projects specifically, add a top-level tag for resolution class: 16px, 32px, 64px. When you need a 32-pixel character reference, a search for tag:32px type:image parent:Characters returns it in milliseconds. Tags in refern are hierarchical, so you can have palette > 4-color, palette > 8-color, and palette > 16-color as nested tags under a palette parent, which collapses neatly in the sidebar.

Step 2: Tag on Import, Not Retroactively

The biggest reference library maintenance mistake is collecting first and tagging later. Retroactive tagging never happens.

Set up directory metadata presets so that any image you drop into a folder gets its base tags automatically. In refern, right-click a folder, open settings, and configure a metadata preset. A file landing in VFX/Fire/ can auto-receive vfx, fire, and style-study tags the moment it arrives. You then add the two or three specific tags (palette, resolution, source style) while the image is fresh in your mind.

Keep your import habit simple:

1. Save the image with the browser extension (one click, folder targeting built in).
2. Add two to four specific tags in the quick-tag field before closing the save panel.
3. Star references that are immediately actionable (you plan to look at these this sprint).

The browser extension for refern works in Chrome, Firefox, and Safari with hover-save on every image. Eagle's extension also covers Edge and Brave if you use those. PureRef has no browser extension at all.

Step 3: Build a Per-Feature Moodboard Canvas

Every feature or art pass benefits from a focused moodboard: one canvas that holds only the references relevant to "the cave tileset" or "the main character idle animation." This canvas lives alongside your library rather than replacing it.

In refern, create a new canvas file inside your workspace. Drag images from the library directly onto the canvas. You can arrange them spatially, group related images with a named layer group, add a text annotation, paste a color swatch from the palette you are targeting, and draw rough composition thumbnails with the freehand tool. If you use an always-on-top overlay while you paint, refern supports pin-window-on-top, adjustable transparency, and mouse clickthrough, which is the same PureRef overlay workflow.

The key difference from PureRef here is that the images on your canvas stay linked to the library. In PureRef, the .pur file embeds its own copies of the images. If you add metadata or tags to an image later, the PureRef copy does not inherit those changes. In refern, the canvas references the image entity in the library, so a search in the library returns the image regardless of which canvas it appears on.

For solo devs, the practical moodboard organization looks like this:

• One canvas per major feature or art task ("cave tiles v1", "character animations sprint 3").
• Keep canvases in a Canvases/ folder inside your workspace.
• Name canvas files with the sprint or date so they stay sortable.
• Archive finished canvases rather than deleting them. You will reference them when the art director (which is also you) wants to revisit a style decision six months later.

Step 4: Use Provenance Links to Trace Shipped Art Back to References

Solo devs rarely document where their art came from. This matters more than it seems. When you revisit an asset six months later to create a variant or update the style, knowing what you were looking at when you made it saves hours of context reconstruction.

refern has typed entity links that handle this automatically:

Derived-from links. When you crop or adapt a reference in refern, the cropped version carries a derived-from link back to the source. The Linked References sidebar on any cropped image shows the original immediately. Search with derived:<source-id> to find everything you extracted from a single reference image.

Placed-in-canvas links. Every time you add an image to a canvas, refern records a placed-in-canvas link. Looking at any reference image, the sidebar shows every canvas it appears on. This is how you answer "which feature moodboards used this reference?"

Cross-reference links. Use these to connect related references that are not parent-child relationships. Two color palettes that inform the same scene. Three character silhouettes that influenced the same design direction. Cross-reference links are bidirectional and show up in both the sidebar and the graph view.

The relationship graph view in refern shows all of these connections as a navigable network. For a solo dev it functions as a project memory: you can open the graph on any image and see the full context of why that image was collected and where its influence ended up.

Neither Eagle nor PureRef has this. Eagle has no relationship system at all. PureRef has no cross-project metadata.

Step 5: Search Your Library Like a Database

The payoff from good tagging is search that actually works.

Some searches you will run constantly during a game project:

• tag:fire rating:>=4 to surface your best fire VFX references when you start an effects pass.
• tag:pixel-art tag:16px in:Characters to find small-format character references.
• color:#2b4a6e to find images that share the dark blue you are trying to nail in an environment.
• is:duplicate to clean up references you saved twice.
• linked-to:<canvas-id> to see everything referenced in a specific feature moodboard.

All of these run locally, instantly, against the SQLite index. No cloud, no API, no subscription required. For large libraries (the 27,000-image user who confirmed smooth performance during refern's alpha is a useful data point), the streaming pipeline keeps search fast.

Eagle has strong search with good fuzzy matching, and its AI Search plugin (available now for Eagle 4.0, local and offline) adds visual reverse-image search. PureRef has no search of any kind.

Common Problems and Fixes

"My library is already a mess of unsorted screenshots." Start fresh with the folder structure and a single folder called Unsorted/ for your existing dump. Tag and move items from Unsorted/ during low-focus time (waiting for a build, end of day). Even moving thirty images a day clears a large backlog in a month.

"I use PureRef for its overlay and don't want to give it up." You do not have to. Many devs use refern as their library and moodboard tool and keep PureRef for per-session overlays while they are in Photoshop or Blender. The two tools do not conflict. If you want to consolidate, refern's pin-window-on-top mode with transparency covers the same overlay workflow.

"I have been using Eagle and my library lives in Eagle's proprietary folder." refern includes an Eagle importer. It reads your Eagle library folders, tags, ratings, source URLs, and notes and brings them into a refern workspace without moving your original files. You keep the Eagle library intact as a backup during the transition.

"I collect a lot of pixel art references from Twitter and itch.io game pages." The refern browser extension handles this. Right-click any image or use the batch-save mode to pull multiple images from a page in one action. Images go directly to your chosen folder with tag-on-save.

Honest Limitations to Know

refern is a local-first desktop tool. There is no cloud sync yet (that is Phase 2 on the roadmap, planned but not shipped). If you work on multiple machines you will need to keep your workspace folder in a shared location yourself (external drive or cloud folder). Eagle has the same limitation; PureRef also has no sync. None of these tools solve multi-machine sync today.

refern has no font management. Eagle does, and if previewing fonts without installing them is part of your workflow, Eagle is the right pick there.

refern is newer than Eagle and PureRef. The community and third-party tutorials are smaller. Eagle has an extensive plugin ecosystem that refern does not have at launch.

There is also no auto-tagging yet. Local-model auto-tagging is planned for a future release but is not live. You tag manually for now.

Next Steps

Once your library is running, a few things compound the investment:

• Read the refern vs Eagle comparison if you are deciding whether to import an existing Eagle library or run both tools.
• Read the refern vs PureRef comparison if you want detail on the canvas and overlay differences between the two tools.
• Browse the what is a reference manager glossary entry for a clear definition of what the library layer actually does and why it matters.
• Look at what is a moodboard for a concise breakdown of the canvas side of the workflow.