Matching an armor plate to one screenshot from a two-hour film

A build lives or dies on getting one detail right — the exact curve of a pauldron, the stitching on a costume glimpsed for three seconds in a trailer, a material that has to read as metal from ten feet away at a convention. That reference exists somewhere in a phone's camera roll or a saved-images folder. Finding the right screenshot again, mid-build, with fabric already cut, is the part nobody plans for.

Where build reference actually piles up

Most cosplay makers are not keeping one reference set per character; they are accumulating a mix — canon art screenshotted from a show or a game, con photos of other builders' interpretations saved for construction ideas, material swatches photographed at a fabric store, and their own progress photos taken to track fit. Each piece is easy to save in the moment. None of it is organised for "find every reference for this exact armor piece," which is the question that comes up constantly once cutting has started.

Canon art and progress photos, kept on one board

A .coii-canvas is pretty-printed JSON living in your own folder, so a build board survives being copied, backed up or handed to a commissioned collaborator the same way any other file would — no export step and no account for them to log into first.

tag:any:armor,pauldron rating:>=4         rated armor reference for this build
in:Pauldron has:notes                     scoped to one piece, with fit notes
type:image tag:any:fabric-swatch          material references across builds

tag:any:a,b matches either tag, rating:>=4 keeps results to reference that actually held up, and in:Pauldron scopes a search to one piece's folder without losing the rest of the build out of reach. A term the parser does not recognise renders as free text rather than an error, so a half-remembered detail still returns something to narrow down from.

One folder per build, searched together or apart

Splitting reference by character or by build is the natural way most makers already work, and none of those folders need merging to be searched as one library. in:Pauldron scopes a search to a single piece's folder, while a plain tag:any:armor search reaches armor reference across every build in the workspace, regardless of which character or convention it was gathered for.

Rating what actually worked once it was built

Reference that looks right on screen does not always translate once it is built at scale, and six months later it is rarely obvious which screenshots actually led to a piece that read well and which led to a rebuild. Rating reference after a piece is finished — four stars for the screenshot whose proportions actually worked in foam or fabric, one star for an angle that turned out to be misleading — turns rating:>=4 into a shortlist worth trusting on the next build that needs a similar piece.

What happens to reference sent by a commission client

Cosplay reference does not only come from personal research — a client commissioning a build often sends their own screenshots, a Pinterest board exported as files, or reference photos of themselves for fit. None of that needs special handling: drop it into the client's build folder inside the workspace already registered, and the watcher picks it up on its own, ready to tag the same as anything gathered independently.

Material swatches as their own searchable set

Fabric and material references — a swatch photographed under a store's lighting, a foam sample tested for a specific finish — are worth keeping searchable across every build rather than refiled per character, since the same material often gets reused on an unrelated piece a year later. Tagging a swatch by material rather than only by the build it was bought for means tag:any:fabric-swatch returns every option tried, across every character, the next time a similar texture is needed.

Last-minute reference the week before a convention

The week before a convention is when reference needs move fastest — a missing detail spotted on a rewatch, a fellow builder's photo shared for a technique, a fit reference taken in a rush. None of that needs a special workflow: drop the new file into the build folder already registered, and it is indexed, taggable and searchable within moments, ready to sit alongside reference gathered months earlier without any extra step.

What a rating system prevents mid-build

A build under deadline runs on trusting the reference already gathered rather than re-researching a detail that was already settled weeks ago. Rating a screenshot or a swatch as soon as it is confirmed useful — four stars for the angle that actually shows how a seam should sit, one star for a shot that looked promising but turned out misleading once test-fitted — means rating:>=4 answers "which reference can I trust right now" instantly, which matters most in exactly the week there is no time to double-check research from scratch.

Comparing this to keeping everything on Pinterest

Pinterest is genuinely where a lot of cosplay research starts, and this page will not argue against that — it costs nothing and nothing beats it for discovering new interpretations of a character. Pinterest has no account-free option, no offline mode, and no way to search by a property like which build a piece belongs to or how it rated once constructed, because a pin carries what the service knows rather than what a file on a Mac knows. The honest split is to keep discovering on Pinterest and land the reference that actually gets used — the screenshots worth returning to, the swatches worth reusing — as files in a folder searchable by more than a board title. The round-up of Pinterest alternatives for artists covers the wider field if a hosted, discovery-first tool is still the goal for that half of the job.

Keeping build reference searchable across a change of software or tools

A maker's collection of canon art and technique reference tends to outlast whichever pattern software, 3D-printing slicer or drafting tool happens to be in use for a given build, and a reference set kept only inside one of those tools' project files does not travel when the tools change. Keeping screenshots, swatches and progress photos as ordinary files in an ordinary folder, tagged by character and material rather than by which app produced a pattern, means the archive survives every switch in software a maker's career will see — registering the same folder again after changing tools costs one re-index, not a rebuild of seasons of gathered reference.

Building a reference habit that survives more than one convention season

A maker's reference needs tend to outlast any single build, and a folder structure built entirely around one convention's deadline does not carry forward cleanly to the next season. Tagging by character, material and technique rather than filing only by convention means an armor reference gathered two seasons ago is exactly as findable today by tag:any:pauldron as it was the week it was saved, regardless of which con it was originally collected for.

Backing up a build archive

Reference and progress photos for a build are not the kind of material that should exist in only one place, especially mid-construction, and because everything Coii Ref writes lives inside the folder it was pointed at — the index, thumbnails and canvas-ready proxies included — whatever already backs up that folder backs up the whole searchable archive along with it. Copying the workspace folder to another drive, or to a second Mac entirely, copies the whole thing, tags and ratings included.

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, on Apple Silicon or Intel, as two native builds.

The app's entire outbound network activity is a 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 and the folder watcher all keep working permanently, so an unfinished trial never turns into a build archive that can no longer be searched the week before a convention.

Working between a home workshop and a shared maker space

Makers who split build time between a home workshop and a shared maker space's computer do not need one workspace to cover both — registering the same build folder separately on each machine gives each one its own local index of what is actually stored there, with nothing to sync and no account tying the two together. Licensing covers three Macs on one purchase, which in practice covers a home machine, a laptop and a shared-space seat.

What a con-photo folder is worth after the convention ends

Photos taken of other builders' work at a convention do not stop being useful once the event is over, provided they were tagged by the technique or character they showed rather than left in an unsorted camera-roll dump. A shot of a clever joint solution photographed at a con two years ago is exactly as findable today by tag:any:articulated-joint as it was the weekend it was taken, ready to solve the same problem on an entirely different build.

Sharing a build archive with a commissioned collaborator

Some builds involve a second maker handling one piece — a commissioned armorer, a wig stylist, a prop maker — and the reference for that piece needs to reach them without setting up a shared account or exporting a folder into an email chain. Pointing their Coii Ref install at a shared folder on a drive both of you already have access to gives each machine its own local index of the same files, so a tag either of you applies while researching is visible to the other, without a server to run for one collaboration.

Who this actually suits

Someone with a real accumulation of canon art, con photos and material swatches spread across more than one build, who wants a specific piece found by search rather than scrolled through by eye with fabric already cut. If the actual daily habit is mostly discovering new interpretations rather than re-finding saved reference, Pinterest remains the better tool for that half of the job. The tattoo artist page covers a related but different craft built around client consults rather than build seasons, and the fashion designer page covers a related job built around seasonal collections rather than a single character. For the general version of the search argument without the build-specific framing, the reference-manager page makes the same case plainly.

Thirty days, every feature, no card and no account: download it and point it at whichever build's reference has been piling up the longest. Tag the screenshots that actually worked once built first — that is the search that pays off the next time a detail has to be matched from three seconds of footage.