Skip to content

A creative director asks for "cropped, but with a structured shoulder" two weeks before a line has to be presented, and the fastest way to answer that well is rarely a fresh round of trend research. It is five seasons of runway stills, swatch photos and sketches already saved somewhere on the Mac — if they can actually be pulled together in an afternoon instead of a re-scroll through folders named after collections that shipped two years ago.

What a season's reference folder turns into after a few years

It never stays one clean set. Runway stills saved during show season, swatch photos taken at a mill visit, phone shots of a stranger's coat on the street, sketches scanned the same afternoon they were drawn — all of it collecting in a folder named after whichever season needed it. That works fine for one line. It stops working the moment next season needs "the structured shoulder from two years ago," because the folder it lives in is named after a collection that already shipped and nobody remembers to check there first.

This season's silhouette board, already pinned to the wall as a file

ss27-structured-shoulder-research.coii-canvas
Eight plates saved as SS27 — structured shoulder research.coii-canvas, a plain JSON file in the season's own project folder rather than a row inside an application.

Drag a shortlist onto a canvas and it becomes Something.coii-canvas, pretty-printed JSON saved wherever the season's other working files already live — beside the tech packs and the fabric orders, not inside a separate app's storage. It names the images it uses without copying them, so the board can move with the project folder to another drive without an export step, and it can be pinned up digitally on a studio screen the same way a board of printed swatches gets pinned to a wall.

Finding "cropped, structured shoulder" across five seasons of saves

/type:image tag:any:cropped,structured-shoulder rating:>=4 -is:favourite
typeimagetagany:cropped,structured-shoulderrating>=4notisfavourite
58 items
Fifty-eight cropped, structured-shoulder references, rated, pulled from five past seasons in one line — not a re-scroll through folders named after collections that already shipped.

Tag a still, a swatch photo or a sketch for what it demonstrates — cropped, structured-shoulder, bouclé, raw-edge — and it stays reachable no matter which season's folder it lives in: tag:any:a,b matches either tag, rating:>=4 keeps it to references that actually made it into a past collection. AND across keys, OR inside a comma list, no parentheses.

type:image tag:any:bouclé,tweed rating:>=3    fabric references, rated
has:notes no:tags                              annotated but never filed
added:>2025-09 tag:any:street                  this year's street-style folder only

A term the parser does not recognise renders as free text rather than an error, so a half-remembered word still returns something worth narrowing from.

Keeping a tag vocabulary consistent across seasons

A studio that has run five or six seasons accumulates its own private shorthand for silhouettes and fabrics — "the SS24 shoulder," "the tweed we used for the coat capsule" — and that shorthand only pays off if it is applied the same way every time rather than reinvented season to season. Deciding early that a silhouette is always tagged by what it is rather than by which season first used it means tag:any:structured-shoulder finds every relevant still in one line two years from now, rather than finding half of them because half were filed under a slightly different word for the same shape. The tag itself is just text typed into the app; using the same word twice is the only discipline involved, and it is far cheaper to keep from the start than to fix retroactively across half a dozen seasons of folders.

Renaming a tag later does not mean re-tagging every file by hand. A saved view built on a tag re-parses its query every time it opens, so correcting the tag on the files that carry it is enough — any view built against it simply reflects the fix from then on, without anyone having to rebuild the view itself.

Working with a second designer or an assistant on the same archive

A studio job often means more than one person touching the same season's folder — a lead designer curating the direction and an assistant pulling runway stills and swatch photos through the week. Because the database, thumbnails and proxies all live inside the project folder itself rather than inside a separate account, a second person working from the same shared drive sees the same tags and ratings the moment their own copy of the app re-scans the folder — there is no server keeping two people in sync, only the same folder both machines happen to be reading. Licensing covers three Macs on one purchase, which in practice covers a lead's desktop, a laptop and an assistant's machine without a second payment, though each machine keeps its own local index rather than updating live the way a hosted tool would.

Trend research on Pinterest, search back home for what already exists

A lot of a season's early direction gets discovered on Pinterest before a single swatch is ordered, and nothing here argues against that — it stays the fastest way to see what a trend looks like once a hundred people have already pinned it. What Pinterest was never built to do is search a designer's own five seasons of saved runway stills and swatch photos, because those pins live in an account rather than in a folder that can be indexed. Most working designers end up doing both: Pinterest for what is happening now, Coii Ref for what has already been collected and rated on past collections.

Comparing this to a lookbook shared live with the studio team

A studio presenting a season internally often builds the moodboard as a shared, commentable board a whole team opens at once, which is Milanote's job — documents, notes and a link anyone on the team can open without installing anything. Coii Ref has none of that: no sharing link, no account, no live comment thread. Sending a .coii-canvas file works, but a teammate needs the app installed to open it. Where Milanote is the presentation surface, this is the search that finds what goes on it.

Comparing this to a swatch pinned over the sketch pad

A different, earlier stage of the job is pinning a single reference image directly over a sketch pad or a tablet while drawing a silhouette, which is PureRef's job — always on top, transparent to mouse clicks, floating over whatever else is open. Coii Ref answers the question before that one: out of five seasons of saved stills and swatches, which reference is actually the right one to pin to the floating board in the first place.

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. It needs macOS 11 Big Sur or later, on Apple Silicon or Intel, as two native builds.

The app's whole outbound network activity is a licence check on Activate and a launch-time read of a server's Date header, so a wound-back clock cannot extend a trial. There is no in-app updater, so no update check, and no analytics or crash reporting.

Past day thirty of an unpaid trial, growing the library — registering a new folder, running the importer, starting an index by hand — needs a licence. Search, tags, ratings, notes, canvases and the folder watcher all keep working permanently on whatever was already indexed.

Working across a studio machine and a home one

Swatch photos taken at a mill visit and runway stills collected at home across several seasons rarely need to be one workspace. Register the studio drive on the studio machine and a personal archive on a home Mac, and each keeps its own local index, with nothing syncing between them and no account tying the two together. Licensing covers three Macs on one purchase, which in practice covers a studio desktop, a laptop and a home machine without a second payment.

What a shelved collection's research is still worth

A season that gets cut or heavily reworked does not have to take its silhouette research down with it, provided that research was tagged by what it shows rather than only by the season it was gathered for. A structured shoulder study shelved two years ago is exactly as useful the next time a structured shoulder comes up on an unrelated line, found by tag:any:structured-shoulder regardless of which season's folder it happened to sit in.

What a fabric-sourcing trip's photos are still worth a season later

A mill visit or a trade fair usually produces a burst of photos taken on a phone in an afternoon — a weave nobody has ordered yet, a trim, a colourway seen once — and that material is easy to lose track of because it was never gathered with a specific season in mind. Registering the folder it landed in costs nothing beyond the first index, and tagging each photo by what it actually is rather than by the trip it was taken on means a bouclé weave photographed eighteen months ago surfaces next to one taken last month, from the same tag:any:bouclé search. Which trip a photo came from stops mattering the moment it is tagged by what it shows.

The same habit pays off across an entire career rather than just one season of sourcing trips. A designer who has been photographing fabric and trim at mills for a decade has, without ever meaning to build one, a private catalogue that is often more specific to their own taste than any supplier's own lookbook — the weaves and colourways that actually got ordered, not the full range a mill publishes. That catalogue is only worth what it is worth once it can be searched by what is in the photo rather than by which folder from which year it happens to sit in, and a phone photo taken in a hurry on a factory floor is exactly as searchable as a runway still shot professionally once both carry the same tag.

Who this actually suits

Someone with a real accumulation of runway stills, swatch photos and sketches across more than one season, working under a deadline where re-finding a past reference beats re-searching trend sites from scratch. If the daily habit is mostly a single swatch pinned over a sketch pad while drawing, PureRef answers that more directly. If the season's board has to be a link a whole studio team opens and comments on, Milanote is the more direct tool. For the adjacent, more product-driven case, the interior designer page covers related ground, and the general search argument without the fashion framing is at the reference-manager page. The rest of the moodboard-shaped comparisons are at the library's roundup of moodboard apps.

Thirty days, every feature, no card and no account: download it and point it at whatever season's folder has been accumulating the longest. Tag last season's strongest silhouettes first — that is the search that answers "cropped, but structured" before the presentation is two weeks out instead of two hours.

Questions

Can I find a silhouette or a fabric by what it looks like, not which season I saved it?
Yes, by tag. Tag a still or a swatch photo `cropped` or `bouclé` as you save it, and `tag:any:cropped,bouclé` returns every match across every season's folder at once.
Does it handle runway stills, swatch photos and my own sketches the same way?
Yes. All three are images to the index, and all three take the same tags, ratings and notes — a sketch and a runway still can carry the same silhouette tag.
Can a team member see this season's board?
Not through the app — there is no sharing link or hosted view. A `.coii-canvas` file can be sent like any file, but they need Coii Ref installed to open it.
Does it import boards I built in Milanote or Pinterest?
No importer reads either one. The only importer reads a refern library. Pinterest and Milanote boards stay where they are; pointing Coii Ref at the same saved images 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.