Keeping Your Embroidery Files Organised (and Why It Pays)
This is the least interesting article on this site and probably one of the most useful. Every embroidery business eventually loses time to a file nobody can find, or runs the wrong version of a design across fifty garments.
What to keep, beyond the DST
Most people keep the machine file and nothing else. That's the mistake. For each design you want:
1. The native source file. The working file from whatever software digitized it — EMB (Wilcom), or the equivalent. This holds editable objects rather than finished stitches, and it's the only thing that allows a proper resize later. Ask for it; you paid for the work.
2. Every machine format you were given. DST, PES, JEF, EXP. Costs nothing to store, and saves a conversion request when you buy a different machine.
3. The original artwork. The vector or high-res raster the design came from. If the file ever needs rebuilding, this is the starting point.
4. A written spec. Thread numbers, finished dimensions, the fabric it was built for, stitch count, and the date. This is the part that lives in someone's head and leaves when they do.
A naming convention that survives
The test of a naming convention is whether someone else understands it in two years. Something like:
client-design-size-fabric.ext
So: acme-logo-3.5in-polo.dst, acme-logo-2.5in-cap.dst, acme-logo-3.5in-polo.emb.
Why each part earns its place:
- Client first — files sort together alphabetically
- Design name — obvious, but be consistent (always "logo", never sometimes "mark")
- Size — the most common cause of running the wrong file
- Fabric — a cap file and a polo file are genuinely different builds
Avoid: dates in the filename (they tell you nothing useful about which to run), "final" and "final-v2" and "final-USE-THIS", and spaces, which break some machine interfaces.
Folder structure
Keep it shallow. Deep nesting is where files disappear.
/clients
/acme-corp
/artwork original logos
/source .emb native files
/machine .dst .pes .jef
spec.txt thread numbers, sizes, notes
One folder per client, four things inside. That's enough for almost any operation, and it's obvious to a new employee without explanation.
The spec file is the valuable part
A plain text file per client, updated when anything changes:
ACME CORP Logo — left chest Size: 3.5in wide Fabric: piqué polo Stitches: 8,400 Threads: Isacord 3743 (navy), 0015 (white) Digitized: Aug 2026 Logo — cap front Size: 2.5in wide Fabric: structured cap Threads: same as above
Thread numbers are the crucial line. They're what makes a reorder eighteen months later match the original run rather than being approximately right — the point that matters most for corporate uniform work across multiple sites.
Version control, lightly
When a design is revised, don't overwrite. Keep the old file and add the new one with a clear distinction — acme-logo-3.5in-polo-v2.dst — and note in the spec file what changed and why.
You will occasionally need to reproduce an old order exactly, and "we changed it at some point" is not a satisfying answer to a customer holding a garment from last year.
Backups
Digitized files represent real money — often thousands of dollars of accumulated work for an established shop. Treat them accordingly: one working copy, one automatic cloud sync, and ideally one offline copy.
Worth noting that a good digitizing provider keeps your files too, so a hard drive failure isn't necessarily catastrophic. But relying on someone else's retention policy as your only backup is not a plan.
Why this pays
Reorders are the most profitable work in embroidery — no digitizing cost, no setup learning, straight to production. Good records turn a reorder into a five-minute job. Bad records turn it into an hour of searching, a re-digitize you shouldn't need, or a batch that doesn't match what you shipped last time.
We supply files in every format and keep your specification on record, so if your copy goes missing, ours doesn't. Ask us for your thread numbers if you don't already have them written down.