SATIN project
Status
| Field | Value |
|---|---|
| Extension | .satin |
| Ecosystem | Satin Studio |
| Format family | Editable project package |
| Open / import | Yes |
| Export | Yes |
| Confidence | Native project format |
What it contains
A .satin package carries an editable Satin Studio project. It preserves the source objects and the assets needed to keep editing them; it is not a wrapper around one exported machine file.
Typical package members include:
- a versioned package manifest;
- the editable project source;
- SVG artwork, reference images, and imported stitch sources;
- project font assets;
- proofs, worksheets, and selected export artifacts;
- hashes for every member.
Local undo history is not part of project source. Workspace versions and audit records remain outside the package unless you explicitly include a handoff report.
Opening a package
Satin Studio validates the manifest, member paths, sizes, hashes, and project version before opening content. Newer optional fields survive a save without being discarded. A package that requires unsupported features stops with a specific explanation.
The original package remains available as import evidence, so a damaged asset or unsupported member does not disappear during diagnosis.
Exporting a package
Choose Export project package when another person needs editable source or when a job needs a portable archive. You can include proofs, worksheets, and machine exports, but the project source remains authoritative.
A machine operator who only needs PES or DST should receive the machine file and worksheet rather than the complete editable package.
Safety rules
- Member paths are relative and cannot escape the package.
- Member sizes and total unpacked size are bounded.
- Hashes are checked before project content is trusted.
- Assets are parsed as data; embedded scripts and external resource loads do not run.
- Machine exports inside the package never replace project source.