Troubleshooting & support

Common stitch-out problems

Symptom	Likely cause	Where to look
Gaps at the edges of a fill/satin	Too little pull compensation or no underlay	Underlay, Satin column
Thread breaks / needle strain	Density too high, or tiny stitches	Density & resizing, export min-stitch filter
Thread piling on the inside of curves	Short stitches off	Satin column
Too many colour changes	Colours not sequenced/sorted	Colour sequence & sorting
Lots of jumps / trims	Objects not branched, or colours not sequenced	Branching & routing, Colour sequence & sorting

The single best habit is to test-sew on scrap before committing to a finished piece.

The Simulation view is an experimental feature that can also be a useful sanity check — playing a design back in sewing order can help you spot ordering, jump and colour-change issues before you sew.

Recovering unsaved work

If Octostitch closed unexpectedly, relaunch it — you’ll be offered the chance to restore your last autosaved work. See Saving & autosave.

Crash logs

If the app crashes, it writes a crash report you can send us. Crash logs are saved in Octostitch’s app-data folder, under a crash subfolder — on Windows that’s:

%APPDATA%\octostitch\crash\crash-<timestamp>.log

(On macOS/Linux, under the equivalent config directory, e.g. ~/.config/octostitch/crash/.)

Each log contains the app version, your OS/architecture, and the error with a backtrace. Attaching the most recent one to a support email helps us fix the problem faster.

Getting support

Email support@octostitch.com with a description of what you were doing, and — if relevant — the most recent crash log and the design file (.ostch). You can also reach the docs and support links from Help → About OctoStitch inside the app.

Prefer social? You can also message us on Instagram at @octostitchembroidery.