How to open a DST file
What the format contains and how to open it on iPhone, iPad, Mac and Windows.
Open pageGuide
How to check a DST file before embroidery
Most DST problems show up in the first minute of looking at the design: the wrong size, an unexpected stitch count, a colour change nobody planned for. Here is a short checklist you can run on a phone.
- Pre-production checklist
- Hoop fit
- Stitch count
- Colour changes
The six-point check
Run these in order. The first three catch most real-world mistakes.
- Compare the design size in millimetres against the hoop you plan to use, leaving room for the fabric and any appliqué.
- Read the stitch count and sanity-check it against the price and time you quoted.
- Count the colour changes and match them against the thread list for the job.
- Look at the stitch path in fullscreen and check the design is oriented the way you expect on the garment.
- Confirm the design name and folder match the job, especially when several revisions exist.
- Export a PNG preview so the confirmed numbers are recorded with the job.
Why these six, and not more
Everything on this list is information the DST header already carries or that the stitch data already describes. You are not judging whether the design is beautiful, and you are not estimating how it will behave on a specific machine — you are catching the mistakes that come from opening the wrong file or misreading a number.
Size, stitch count and colour changes are the three values that turn into money and machine time. Orientation and identity are the two that turn into a re-stitch. The exported preview is what stops the same question being asked again next week.
What a viewer can and cannot verify
Being precise here matters: a viewer shows what the file says, which is not the same as proving the design will sew out correctly.
| Question | A DST viewer can answer | Needs production software |
|---|---|---|
| How big is the design? | Yes, from the header | — |
| How many stitches? | Yes, from the header | — |
| How many colour changes? | Yes, from the header | — |
| Does the design fit my hoop? | Yes, by comparison | — |
| Is the stitch path oriented correctly? | Yes, visually | — |
| Is the density right for this fabric? | No | Yes |
| Will it pucker or pull on this material? | No | Yes |
| Are trims and jumps optimal? | Partly, visually | Yes |
Checking hoop fit properly
Compare the header size against the usable sewing field of the hoop, not the hoop's outer dimensions. A 100 × 100 mm hoop does not give you a 100 × 100 mm sewing area.
Leave margin for the fabric edge and for any appliqué that will be placed by hand. If the design is within a few millimetres of the field edge, it is worth re-checking before the hoop goes on the machine.
Using the stitch count well
Stitch count drives both price and production time, so it is the number most likely to be compared against a quote. When the count is far from what you expected, the usual cause is opening a different revision of the design rather than a corrupt file.
If two files look identical but their counts differ by thousands, they are not the same design, even if the file names suggest otherwise.
Colour changes and the thread list
The header records how many machine stops the design expects. That is the number of thread changes the operator has to plan for, and it should line up with the thread list prepared for the job.
A mismatch here is often not an error. It usually means someone edited the colour sequence after the thread list was written, and the two documents need to be brought back in sync.
Questions about checking DST files
Can a viewer tell me whether a DST file is production-ready?
No. A viewer shows the design and the values in the file. Judging density, pull compensation and machine behaviour needs production software and, usually, a test sew-out.
Is the size in the header always correct?
It is what the file declares. A design edited in one tool and saved by another can carry a stale extent value, so a visual check of the stitch path is worth doing as well.
Why does the stitch count differ from what my machine reports?
Some machines add or count stitches differently around trims, jumps and colour changes. Small differences are normal; large differences usually mean a different revision of the design.
How can I record the check for a job file?
Export the PNG preview with its specification block and store it with the order. It captures the exact size, count and colour changes that were confirmed.
Should I check on a phone or on a computer?
For size, count, colour changes and a look at the stitch path, a phone is enough and it is usually the device that is actually on hand. Deeper production checks belong on a desktop.
Keep reading
Run the check on the phone you already have
Stitch Viewer shows size, stitch count, colour changes and the stitch path for any .dst file, on iPhone and iPad.
Download on the App Store