Skip to main content

PES versions

PES uses #PES plus four version digits. The version matters for PES-side metadata such as editable objects, hoop/page fields, thread tables, previews, and addendum blocks.

Satin Studio currently treats PES imports as stitch-preserving imports: it reads the embedded PEC stitch payload when the PES prefix points to a compatible payload. Satin Studio does not promise to preserve every version-specific PES metadata field.

For byte-level details, see PES file structure.

VersionSignatureSatin Studio statusNotes
v1#PES0001Imports compatible PEC payloadsOlder PES generation.
v2#PES0020Imports compatible PEC payloadsOlder PES generation.
v2.5#PES0025ResearchingDocumented by external references; needs validation.
v3#PES0030Imports compatible PEC payloadsOlder PES generation.
v4#PES0040Imports compatible PEC payloadsv4+ may include PEC addendum data.
v5#PES0050Imports compatible PEC payloadsv5+ can define configurable threads.
v5.5#PES0055Imports compatible PEC payloadsReported by external tools/references.
v5.6#PES0056ResearchingDocumented by external references; needs validation.
v6#PES0060Available now for Satin Studio export subsetSatin Studio writes compact v6 with embedded PEC and addendum.
v7#PES0070Imports compatible PEC payloadsNewer PES generation.
v8#PES0080Imports compatible PEC payloadsNewer PES generation.
v9#PES0090Imports compatible PEC payloadsNewer PES generation.
v10#PES0100Imports compatible PEC payloadsNewer PES generation.

"Imports compatible PEC payloads" means Satin Studio can read stitch data when the PES prefix locates a supported PEC payload. It does not mean Satin Studio imports the PES-side editable design model.