Skip to content

An art director sends three words — "more brutalist," "less saturated," "read as colder" — an hour before a pitch, and the fastest path to answering is almost never a new search on the internet. It is the four years of architecture photos, material studies and old paintings already sitting in folders you have been adding to the whole time, if you can actually search them fast enough to matter before the meeting.

Where a folder full of years stops being searchable by eye

A working concept artist's reference folder does not stay small. Environment studies, materials, lighting references, anatomy, old personal work kept for a specific pose — it accumulates project after project, and scrolling it works until it very suddenly does not. The point where it breaks is usually mid-deadline: you know you shot or saved the exact reference for this problem eighteen months ago, on a different project, and finding it by eye costs twenty minutes you do not have.

Tags help until the folder crosses a few thousand files and a rename quietly breaks whatever kept track of them. A spreadsheet of "what's in which folder" goes stale the moment you reorganise for a new project. The underlying issue is the same one every time: the metadata about a reference and the file itself live in two different places, and the two drift apart.

Answering "more brutalist" in one line

/type:image tag:any:brutalist,concrete rating:>=4 -is:favourite
typeimagetagany:brutalist,concreterating>=4notisfavourite
84 items
Eighty-four candidates for "more brutalist," typed while still on the call — the good ones you never got round to starring, not a fresh search on the internet.

Tag as you build the collection, rate what actually held up on a past project, and the query line reaches all of it later: type:image or type:video, tag:any:a,b for either tag, rating:>=4 for what you starred well, -is:favourite to exclude what is already pinned elsewhere. AND across keys, OR inside a comma list, no parentheses — the same shape whether you are searching four hundred files or forty thousand.

tag:any:overcast,dusk width:>=3000     mood references that hold up printed
has:notes no:tags                      annotated but never filed
added:>2026-01 tag:any:sci-fi          this year's science-fiction folder only

A term the parser does not recognise becomes free text instead of an error, so a half-remembered word still returns something while you refine it.

From a shortlist to a board an art director can see

outpost-exterior-pass-2.coii-canvas
Eight plates saved as Outpost exterior — pass 2.coii-canvas, a plain JSON file in your own project folder rather than a row in an app.

Drag a shortlist onto a canvas and it becomes Something.coii-canvas, pretty-printed JSON saved wherever you keep the project's files. It names the images it uses without copying them, so the board sits beside — not instead of — the folder it was built from, and it can move with a project folder to another drive without an export step.

There is no sharing link and no live comment thread; sending a board to someone else means sending the file, and they need Coii Ref installed to open it. If a hosted, client-facing board is the actual job, PureRef and dedicated moodboard tools cover that better than this page pretends to.

Building a folder structure that survives more than one project

A common pattern among concept artists who eventually adopt a search-first tool is to stop organising by project and start organising by subject instead — Architecture, Materials, Lighting, Anatomy — because tags do the job folders used to do, and a subject-based folder plus a tag for the project it was used on covers both questions at once: "show me weathered metal" and "show me what I used on the outpost job." Neither structure is required by the app; both work, because the query line reaches into subfolders the same way regardless of how deep the hierarchy goes.

type:image tag:any:outpost,pass-2 rating:>=4    what actually made the cut
tag:any:architecture -tag:used                  unused architecture stock

Where -tag:used assumes you tag images once you have actually put them on a board — a habit worth building specifically because it turns "have I used this before" from a memory test into a one-line answer.

Old projects, new tags, without a re-import

A folder from a project two years ago does not need to be re-indexed to be searched today — it only needs to be registered once, and after that the watcher keeps it current if anything about it changes. Going back and adding tags to old material after a new project makes them relevant again works the same way it always did: tag the file, and every saved view built on that tag picks it up immediately, because a view re-parses its query rather than storing a fixed list of matches from the day it was saved.

Photo reference and your own paintings, one index

A concept artist's folders usually mix collected photo reference with personal studies and old finished paintings kept for a specific pose or lighting solution. Coii Ref does not distinguish between the two — both are images to the index, both take tags, ratings and notes the same way, and both show up in the same search. tag:any:pose rating:>=4 returns your own figure studies and a saved photograph equally, if both carry the tag.

What happens to a reference the client sent you directly

References do not only come from your own collecting — an art director drops a folder of look-development images into a shared drive, or a client sends three photographs by email that define the whole direction. Those files need nothing special: drop them into a project folder inside the workspace you already registered, and the watcher picks them up on its own, ready to be tagged and rated the same as anything else. There is no separate "inbox" to manage and no import dialog to run for a handful of new files — the folder is the only thing that has to be true, and Finder already knows how to put a file into one.

Comparing this to keeping everything in Photoshop or Procreate

Some concept artists never leave a folder-and-drag-in workflow at all, pasting references directly into a working file as a reference layer. That approach works and this page will not argue against it for a single piece — the trouble shows up a year later, when the reference lives only inside finished files scattered across projects, invisible to any search and impossible to reuse without opening the file it is buried in. Registering the same folder of source references with Coii Ref does not replace pasting a reference into a working document; it means the version outside that document — the original you saved — stays searchable on its own, independent of which project file it eventually got used in.

What a shortlist looks like under real deadline pressure

The scenario worth testing during the trial is not a calm afternoon of tagging — it is the version that actually happens, which is a note landing mid-afternoon and a shortlist needed before the next call. That is a single query, saved as a view beforehand if the same kind of note tends to repeat project to project: a "cold and industrial" view built once during a slow week answers the same request instantly the next three times it comes up, because the view re-parses its tags rather than needing to be rebuilt from scratch each time.

What it costs and what it runs on

$19 once, three Macs, updates included, nothing that renews. The trial runs 30 days with every feature enabled, no card and no account required to start. Requirements are macOS 11 Big Sur or later, Apple Silicon or Intel, as two native builds.

Network activity is limited to the licence check on Activate and a launch-time read of a server's Date header only, so a wound-back clock cannot extend a trial. No in-app updater means no update check, and there is no analytics or crash reporting.

Past day thirty of an unpaid trial, one category of action stops: growing the library, meaning registering a new folder, running the importer, or starting an index by hand. Search, tags, ratings, notes, canvases and the folder watcher all keep working permanently, so an unfinished trial never turns into a library you can no longer read.

Working across more than one machine or a shared drive

A studio job sometimes means a reference folder lives on a shared drive rather than a personal one, and a freelancer often works between a desktop and a laptop depending on where the day happens. Coii Ref treats each folder you register as its own self-contained workspace — the index, thumbnails and proxies live inside it — so a shared drive mounted on a second Mac can be registered there too, each machine building and keeping its own local index of the same files. Nothing about that setup requires a server or an account; it is the same trick a personal external drive uses, applied to a drive more than one person happens to plug in.

Licensing covers three Macs on one purchase, which in practice covers a desktop, a laptop and a studio machine without a second payment, though each one indexes independently rather than sharing state live the way a hosted tool would.

What a rejected direction still owes you

Concept work produces a lot of material that does not survive a review — a direction gets killed, and the reference gathered for it usually gets abandoned along with the paintings. That material is not wasted if it stays searchable: tag it by subject rather than only by the project it was gathered for, and a killed "outpost, brutalist" direction's reference becomes available the next time brutalism comes up on an unrelated brief, rather than buried in a folder named after a project nobody is working on anymore. The search line does not care which project a file was originally gathered for — only what it is tagged and rated as now.

Who this actually suits

Someone with years of accumulated reference already on disk, working under deadlines where re-finding something beats re-searching for it. If your reference habit is mostly a handful of images pinned around your canvas while you paint — not a large searchable archive — PureRef or a similar floating tool answers that more directly than a search-first app does.

For the broader case this page specialises, the general reference-manager page makes the same argument without the concept-art specifics, and the moodboard-focused version covers what happens once a shortlist becomes a board. Against the two most capable full libraries, refern adds an on-device tagger and search by meaning that this app does not have, and Eagle copies what you import into its library rather than indexing it in place — both worth fifteen minutes if you are still deciding.

Thirty days, every feature, no card and no account: download it and point it at the folder the next brutalist brief will actually come from. Index the oldest project folder you still have first — that is the one where years of half-remembered reference turn out to already be exactly where you left it, just finally searchable in the time it takes to type a tag.

Questions

Can I search references by material or mood, not just filename?
Yes, by tag. `tag:any:rust,weathered` or `tag:any:overcast,dusk` returns everything carrying either tag, across every folder in the workspace, from one query line.
Does it handle both photo reference and my own concept paintings?
Yes. Both are images to the index — the same tags, ratings, notes and search apply whether the file is a photograph you saved or a painting you made.
Can a client or art director see the board?
Not through the app — there is no sharing link or hosted view. A `.coii-canvas` file can be sent like any file, but the recipient needs Coii Ref installed to open it.
Does it import my existing PureRef boards?
No. The only importer reads a refern library. A PureRef scene stays a PureRef scene; pointing Coii Ref at the same image folders costs nothing but the first index.
What does it cost?
$19 once, three Macs, updates included, nothing that renews. The trial is 30 days with every feature, no card and no account.