A smarter file system for fabric designers

A fabric design library rarely stays tidy for long. Early sketches become vector artwork, then layered source files, repeat tiles, colourways, print-ready exports and mockups. Without a consistent naming system, even a small collection can become difficult to search, especially when a customer needs an exact production file.

Consistent names and a logical folder structure turn that accumulation into a usable design archive. They reduce duplicate work, make approvals easier to trace and help new team members locate assets without relying on institutional memory. The goal is a system anyone can follow without extensive training.

Australian studios often operate across markets, wholesale orders and direct sales, so their files need to support both creative development and commercial record-keeping. Dates, measurements, colourways and order references must remain clear even when work moves between a home studio, a production supplier and a courier.

The strongest system is not necessarily the most elaborate. A few agreed rules, applied consistently, will usually outperform complex software that nobody maintains. It should also be simple enough to apply to existing work, including files created before the naming convention was introduced.

Start with a clear naming grammar

A useful filename identifies the design, colourway, version and technical state without trying to describe every detail. A stable project code can connect all artwork in a collection, while the design name makes the asset recognisable. Descriptive labels are particularly useful for small labels that manage several related patterns at once.

For example, botanical-drift__coral__v03__repeat-ready__300dpi__2025-08-14.tif is easier to interpret than coral_final_FINAL2.tif. The double underscore separates major fields, while hyphens connect words within a field. The example also tells a designer whether the file is tiled, what resolution it uses and when it was created.

Keep names lowercase and avoid punctuation that can cause problems across operating systems. Although Australian paperwork commonly uses day-month-year dates, use YYYY-MM-DD inside filenames because it sorts chronologically. Use version numbers such as v01 and v02, but leave status labels such as “review” or “approved” in the folder structure or metadata so filenames remain stable.

Build a searchable folder map

Organise the library by project or collection rather than scattering the same design across folders called “new”, “exports” and “finished”. A practical top-level structure provides predictable locations for active and historical work.

  • 01_Active_Projects
  • 02_Design_Library
  • 03_Production_Ready
  • 04_Sales_and_Orders
  • 05_Admin_and_Templates
  • 90_Archive

Each active project can then use the same internal sequence. This keeps briefs, working artwork and customer approvals together without mixing them with the permanent design library.

  • Briefs_and_Moods
  • Sketches
  • Colourways
  • Artwork_Sources
  • Approved_Artwork
  • Deliverables

Approved artwork should be copied into the approved folder rather than moved, leaving the working area intact until the project closes. Production-ready exports belong in their own protected area, while order files should be created only when a customer or stockist confirms a requirement.

Templates, colour profiles and supplier specifications should have a dedicated home so every new project inherits the same standards. Keep the active library uncluttered by moving superseded collections to the archive, but do not delete approval history, supplier correspondence or the source files needed to reproduce a product.

Add metadata that prevents costly mix-ups

Filenames are useful for scanning, but metadata handles details that would make a name unwieldy. A digital asset management system or even a carefully maintained spreadsheet can record the designer, client, collection, fabric type, print technique, colour count, repeat dimensions, status and approval date. Tags should also capture the intended market or application, such as dressmaking, homewares or commercial upholstery.

The metadata should distinguish source artwork from derivatives. Layered Adobe Illustrator or Photoshop files belong in the source collection, while flattened TIFF, PNG and PDF exports belong with deliverables. Record the intended colour space, resolution and output profile so a print-ready file is not mistaken for a screen mockup or resized social-media image.

When a label collaborates with an Indigenous artist, metadata should record the artist’s name, attribution requirements, cultural permissions and any restrictions on commercial use. These details are more than administrative notes; they support Indigenous Cultural and Intellectual Property expectations and prevent approved artwork from being reused outside its agreed scope. Wider discussions about credit and participation can be informed by creative community perspectives, while the studio’s permissions record remains the operational source of truth.

Control versions without losing working history

Never overwrite a file that another person may already have opened or approved. A dependable revision sequence uses v01, v02 and v03, with a short change log explaining what changed. Status can move through clearly defined stages such as working, in review, approved and superseded.

Save working files separately from exports, and record which version received customer approval. If a colour changes after sign-off, create a new version rather than replacing the approved one. This makes it possible to identify the exact artwork used for an order and to restore an earlier colour if a production problem is discovered.

Each delivery should include a small, controlled package containing the final artwork, repeat dimensions, colour references, specifications and any required readme. Archive that package with its approval date, supplier details and order reference. Naming and versioning improve retrieval, but they do not replace backups; keep local, cloud and off-site copies according to a documented recovery plan.

Fit the system to Australian sales work

Australian designers frequently need files for several buyers at once. Stallholders trading at events such as Make It Modern at Melbourne’s Royal Exhibition Building or Surry Hills Makers Market in Sydney often need product images, pricing sheets and small presentation files alongside production artwork. Record the relevant collection and event as metadata, and use a dedicated sales folder for each event rather than renaming the master artwork repeatedly.

Order folders should contain the purchase order number, stockist name, design code, colourway, quantity in metres, lining details and delivery address. If the order travels through Australia Post eParcel, add the destination postcode and parcel reference to the packing record. This prevents a busy packing afternoon from confusing a blush colourway with rust or a one-metre order with a ten-metre order.

Keep tax and supplier records connected to the commercial folder, including GST invoices, receipts and payment details. The Australian Taxation Office generally requires business records to be retained for at least five years, although the exact obligations depend on the business. Do not force invoice numbers into every artwork filename; instead, link the order record to the relevant design and version. The same applies to measurements, which should consistently use centimetres and metres.

Make the standard a daily studio habit

Write the naming rules as a short studio guide and save it with the project templates. Include permitted abbreviations, date format, version syntax, colourway labels and examples of correct and incorrect filenames. Give one person responsibility for maintaining the guide, but invite the whole team to suggest improvements when a new production method creates a genuine need.

Review the library at regular intervals, such as at the end of each collection or quarter. Check for duplicates, broken links, missing previews and files stored outside the agreed structure. When a new member joins the studio, show them how to find a production asset and trace its approval history using only the naming system and metadata.

Choose one active collection today, create the standard folders, rename its key files and record the result in the studio guide. Make that first pass the model for every future project, so searching for a fabric design takes seconds rather than an afternoon.