TLDR
Use one fixed sequence for every asset: Project_Item_Size_Style_Purpose_v##. A file called WildflowerFavor_Label_2in_Pink_Print_v03 tells you what it belongs to, what it is, its size, its variation, its job, and its revision before you open it. Keep the sequence consistent, omit fields that genuinely do not apply, and never use names such as final-final-new.
A useful craft file naming system should answer four questions at a glance: What is this asset? Which variation is it? What job does it perform? Is it the current revision? That matters when one cheerful little label turns into three sizes, four colorways, a printable sheet, a cutting file, two customer proofs, and an edited version with the date moved half an inch.
The goal is not to create a giant filing bureaucracy. It is to make the correct file obvious when you are ready to print, cut, upload, share, or reorder. Start with the same field order, use short controlled terms, and let folders handle broad project grouping.
Build your craft file naming system in a fixed order
My default pattern for craft projects is Project_Item_Size_Style_Purpose_v##. Use underscores between fields so the chunks are visually clear. Within a field, use a short joined term such as FavorLabel or ThankYouCard rather than adding a string of inconsistent spaces and punctuation.
| Field | What it identifies | Useful examples | When to omit it |
|---|---|---|---|
| Project | The collection, event, product line, or design family | WildflowerParty, PantryLabels, MoonCat | Almost never |
| Item | The particular asset within that project | FavorLabel, StickerSheet, Invitation, Cutline | Never when a project contains multiple pieces |
| Size | The finished dimensions or named size tier | 2in, 3x5in, SmallJar, A5 | When only one size exists and confusion is unlikely |
| Style | A meaningful colorway, material, finish, or design variation | Pink, Navy, Matte, Clear | When there is no production-relevant variation |
| Purpose | The job performed by this particular file | Source, Print, Cut, PTC, Proof, PressPDF | When the item name already makes the job unambiguous |
| Revision | The intentional change number | v01, v02, v10 | Only for disposable exports that cannot be confused with current work |