Importing files
Import keeps evidence. It does not invent certainty.
Satin Studio currently imports:
- PES, PEC, and DST machine stitch streams;
- SVG vector artwork;
- TTF and OTF font assets.
See File formats and status for the current matrix.
Machine files
PES, PEC, and DST files open as preserved stitch streams. The app can show stitches, color blocks, jumps, trims, stops, and thread order. DST color stops do not guarantee thread RGB/catalog identity, so keep a worksheet when colors matter.
That is intentional. A machine file usually does not contain the editable design that created it. It contains instructions for a machine. If Satin Studio later reconstructs fills, runs, satin columns, or text-like regions, reconstruction must be reviewable and reversible.
Use machine-file import for:
- checking what a purchased file really sews;
- finding visible jumps or bad trims;
- resizing with warnings;
- preparing a new export from an old stitch stream;
- building production notes when the original source is gone.
Artwork files
SVG is artwork input. It can contain paths, shapes, colors, transforms, and text. Artwork still needs embroidery decisions: stitch type, density, underlay, pull compensation, thread mapping, sequence, and trims.
A clean SVG is easier to digitize than a noisy one. Remove hidden shapes, stray points, tiny specks, and accidental backgrounds before treating the artwork as production input.
Raster image import is planned. When it arrives, it should start as a reference or tracing workflow, not as a promise of automatic production stitches.
Font files
TTF and OTF files can be added as project font assets. Use this when exact text matters. A project font travels with the project, so text shaping does not depend on whatever fonts happen to be installed on another device.
Text can still be risky. Small letters, narrow counters, serifs, towel fabric, and satin-style stitches can fail. Trust measured warnings over the screen appearance.
Privacy boundary
Do not save or share a file unless you intend to put it in the workspace. Local preview and analysis should stay local until the project is saved or a share/export action is taken.