Whether the file came from a customer, a marketplace seller or your own digitizer, a few minutes on screen can save a hoop full of wasted garments. Every step below uses free tools that run in your browser.

Step 1: Open the file in a viewer

Open the file in the free PlixaLabs DST file viewer. It reads the file in your browser without uploading it and shows the design, width and height, stitch count, color stops, jumps, thread length and estimated run time, with stitch-by-stitch playback. If you only have a PES or another format, your machine’s own software or the embroidery file converter can help.

Step 2: Confirm the size

Compare the width and height with the order. A left chest logo that arrives at jacket-back size, or the other way round, is the easiest mistake to catch and the most expensive to miss. Remember that resizing a stitch file on the machine changes its density; if the size is wrong, ask for a corrected file rather than scaling it.

Step 3: Sanity-check the stitch count

Stitch count should make sense for the size and how much of the design is filled. Enter the size and coverage into the stitch count estimator for a rough reference. A count far above the estimate for a small design can mean stacked fills or excessive density (a common cause of puckering); a count far below can mean thin coverage that lets fabric show through. Treat the estimate as a guide, not a pass mark.

Step 4: Match color stops to your thread plan

Count the color stops and check they match the colors in the design. DST files don’t store thread colors, so the viewer shows default colors: use its recolor option, or the color sequence sheet from your digitizer, to see the design as it will sew. An unexpected extra stop often means a stray object or a duplicated color.

Step 5: Look at jumps and trims

Turn on jump stitches in the viewer. Short travel under areas that will be covered is normal. Long jumps across open fabric should end in a trim; otherwise the operator has to clip them by hand, and loose threads can snag.

Step 6: Watch the sewing sequence

Play the design stitch by stitch and watch the order. Look for:

  • Backgrounds and fills sewn before the outlines and details that sit on top of them.
  • Each color finished before the next begins, without needless returns to an earlier color.
  • On caps, sewing from the center outward and from the bottom up (see our cap digitizing guide).
  • No big jumps back and forth across the design.

Step 7: Zoom in on small text and fine detail

Zoom in on lettering and thin lines. Letters that are too small tend to close up or look fuzzy once sewn. As a reference, Hatch Embroidery’s lettering guide lists 0.25 in (6 mm) as the minimum height for common fonts such as Tahoma and Verdana, and more for scripts. Very thin running-stitch details can disappear into textured fabrics.

Step 8: Estimate the run time

Use the embroidery run time calculator with your machine’s speed to plan how long the job will take per piece. A run time that seems far too long for the design is another sign that the stitch count is inflated.

Step 9: Test-sew before production

Sew one test piece on the same fabric, stabilizer, needle and thread you’ll use for the job, then check it against this list:

CheckPassFail: what it usually means
Size and placementMatches the orderWrong file size or hooping position
RegistrationOutlines sit on their fillsGaps: compensation, sequence or hooping
PuckeringFabric lies flat around the designDensity, underlay, stabilizer or hooping (see our puckering guide)
CoverageNo fabric showing through fillsDensity too light or underlay missing
LetteringEvery letter readable; counters openText too small or too little compensation
Thread breaksNone, or one clear causeDensity too high, stacked stitches or tension
Trims and loose threadsNothing to clip by handMissing trims in the file
FeelFlexible, not board-stiffDensity too high for the fabric

Print this page and keep it by the machine, or copy the table into your own QA sheet.

What common digitizing mistakes will you spot?

  • Auto-converted files: odd stitch angles, too many trims and fills where satin should be. See can AI digitize embroidery?
  • Stacked fills: hidden layers that double density and cause puckering.
  • Missing underlay: stitches sink and edges look ragged on the test piece.
  • Wrong size: a file scaled on the machine rather than re-digitized.
  • Flat sequence on a cap: registration drift and misaligned outlines.
  • Text too small: letters closing up at the finished size.
PlixaLabs

Found a problem? We’ll fix it

We fix or rebuild broken, auto-digitized or third-party files, quoted after a free file check.

Send us the file →

Frequently asked questions

Open it in a free browser-based viewer such as the PlixaLabs DST file viewer. It shows the design, size, stitch count, color stops, jumps and run time, with stitch-by-stitch playback, and the file isn’t uploaded.
Check the finished size, the stitch count for that size, color stops against your thread plan, jumps and trims, the sewing order, and whether small text is big enough to sew cleanly. Then test-sew on the real fabric.
DST files don’t store thread colors, only where color changes happen, so viewers and machines show default colors. Assign your own colors in the viewer or on the machine using the color sequence from your digitizer.
Yes. A viewer shows the stitch path, but only a sew-out on the real fabric, stabilizer and thread shows puckering, gaps, coverage problems and how small text really looks.
It depends on the size and how much of the area is filled. Use a stitch estimator as a rough guide for your size and coverage, and treat a count far above the estimate for a small design as a warning sign worth investigating.