Exports and machine files

Export writes a machine file from the open project state.

Choose an output format supported by the target machine. Satin Studio validates the project against that format before it writes the file. The file-format reference lists each available importer and exporter.

Preflight

Preflight is the final check. Confirm:

• output format;
• machine profile;
• hoop and safe area;
• dimensions;
• stitch count;
• thread order;
• stops;
• trims and jumps;
• unresolved warnings;
• selected colorway if colorways are used;
• project version.

If a value is wrong, fix the project before export.

Machine file versus project

Keep the saved project. The machine file is for sewing.

Use the project when you need to:

• edit objects;
• change text;
• change the hoop;
• alter thread mapping;
• regenerate an export;
• review warning history;
• reproduce a production run.

Opening your own exported machine file later is worse than reopening the source project.

Export package

A complete handoff can include more than the machine file:

• PES or DST file;
• preview image;
• stitch count, trims, stops, color blocks, and runtime estimate;
• thread order;
• material requirements;
• construction steps;
• production notes;
• worksheet or checklist, including the selected colorway name, proof background swatch, and colorway-specific production notes;
• proof link when sharing is enabled.

Keep file names boring and useful. Satin Studio includes the active saved colorway in downloaded PES/DST filenames; add version or target-machine wording when that avoids confusion.

Before sewing

At the machine, check the physical setup again:

• hoop matches export;
• fabric matches assumptions;
• listed stabilizer, backing, blank, needle, and specialty thread are present;
• thread order is readable;
• any RGB-only source colors have been matched to real spools, using worksheet catalog suggestions only as starting points;
• any source-color map rows marked as split across multiple project threads are intentional or have a saved confirmation;
• any near-duplicate source-color cleanup was merged or intentionally kept separate on purpose, not just because screen colors looked close;
• programmed stop order and reasons are intentional;
• construction-step pause reviews, Step timing labels, saved stop-timing verification / stop numbers, and any manual pause plan match the real workflow;
• resized imported stitch blocks were test-sewn or reconstructed;
• warnings were accepted for a reason.

If any of those changed, go back to the project and export again.