To sell embroidery machine files online, deliver the machine formats your buyers actually use, publish hoop size, finished dimensions, stitch count and color sequence, and stitch out every size you advertise. A PNG preview or successful software export does not prove that a PES, DST, JEF or VP3 file will sew cleanly on fabric.
This guide is for embroidery digitizers selling reusable designs. Its original asset is a stitch-out release card that ties each delivered file to a physical test, machine setting and buyer-facing specification.
Create a Stitch-Out Release Card
| Field | Record for each size | Why the buyer needs it |
|---|---|---|
| File formats | PES, DST, JEF, EXP, VP3 or other delivered extensions | Confirms machine compatibility |
| Finished dimensions | Width × height in mm and inches | Prevents hoop-fit surprises |
| Hoop used | Advertised hoop size and orientation | Makes the test reproducible |
| Stitch data | Stitch count, color stops and trims | Sets time and thread expectations |
| Test material | Fabric, stabilizer, needle and thread | Explains the physical result |
| Evidence | Front and back photographs of the actual stitch-out | Shows density, pull and jump behavior |
Hatch Embroidery's current file-format reference distinguishes editable working files such as EMB from exported machine stitch files and lists formats used by different machine families. Ask buyers to confirm their model's manual; a brand may support more than one format and older machines can differ.
Deliver Formats by Machine Job
Do not put one “universal” label on every archive. Create a manifest that maps each file to its purpose:
- PES or PEC: commonly used by Brother, Baby Lock and related machines.
- JEF or JPX: used by many Janome and Elna workflows.
- DST: widely exchanged as a stitch format, but may not preserve all color information.
- EXP: used in Melco and some Bernina workflows.
- VP3 or related formats: used across supported Husqvarna Viking and Pfaff workflows.
- EMB or another source format: editable working file only when the buyer's license tier includes it.
Treat this as a packaging map, not a promise that every machine in a brand family accepts every listed extension. Publish the exact formats in the ZIP and never substitute a preview image for a stitch file.
Stitch Out Every Advertised Size
- Export each retail machine format from the approved source.
- Load the file through the same transfer path a buyer uses.
- Confirm design dimensions and orientation on the machine before stitching.
- Use the stated fabric, stabilizer, needle and thread setup.
- Photograph the front and back without hiding puckering or jump stitches.
- Record thread breaks, trims, color stops and any manual intervention.
- Compare the finished result with the product preview and release card.
Resizing a stitch file can change density and underlay behavior. Test every sold size as its own release; do not scale one successful sample in a mockup and imply that all sizes were stitched.
Package the Buyer ZIP
Use folders by size, then keep all formats for that size together. Include a color chart, release card, license and start-here guide. Use filenames that expose dimensions and version, for example `leaf-border-100x100mm-v1-1.pes`.
State whether the buyer may sell physical embroidered items, use the design for client work, alter it or share the machine file with a production partner. Permission to sell a finished patch is different from permission to redistribute the PES or DST file. Do not include fonts, characters, logos or artwork you do not have the right to sell. This is a licensing framework, not legal advice.
Preview Real Stitches
Lead with a photograph of the actual stitched sample, then show the software rendering as a labelled technical preview. Include finished size and fabric in the caption. Close-ups should reveal edges and fills; the back view can show how dense or clean the test really was.
PayRequest can host the product page, collect payment through a connected provider and release the approved ZIP after successful payment. Create a digital design product and use secure file delivery so the order stays tied to the tested release.
Final Release Gate
Publish only when every included size has a physical stitch-out record, every delivered extension opens through the intended machine workflow, the license separates physical-product use from file redistribution and the buyer ZIP matches the manifest. Complete one buyer-view purchase and extraction on desktop and mobile before sharing the link.