Clear answers. No stitched-up claims.

The stitch preview is free and does not require an account. Daily and monthly preview limits apply. Downloading the machine file, ZIP or worksheet is a separate unlock. Machine-file downloads require processing credits, single-file checkout or an active subscription allowance. Credits unlock files; they do not start the job.

Yes. Upload clean artwork, choose the finished width and output formats, then our automated digitising workflow handles the thread colours, generates the stitches and validates the files. Photos, gradients and very fine text may need simplified source artwork.

Yes. The free viewers open all 23 supported embroidery source formats without starting a conversion or using a processing credit. They render the parsed stitch path and report dimensions, thread sequence, colour changes, jumps and trims. No account is required.

A standard conversion preserves the original design dimensions and stitch path wherever the target format supports them. Known limitations are flagged, and a test stitch is recommended before production.

The converter writes PES, DST, JEF, JEF+, JPX, EXP, VP3, XXX, PEC, U01, TBF, HUS, SEW, SHV, PCS, VIP, TAP, DSB, DSZ and KSM. It also reads PHB, PHC and PCM as conversion sources. Every generated machine file is parsed again and checked before release.

Every completed job includes a software-rendered stitch preview and thread chart. The selected machine files, production worksheet and ZIP package stay locked until you unlock the download. EXP jobs also include Bernina-compatible INF colour information and a BMP preview companion after unlock.

Every generated machine file is reopened and parsed before release. The service records dimensions, stitch and thread counts, colour changes, jumps, trims, warnings and format-specific limitations, then produces a software-rendered preview. Always run a physical test sew before production.

The REST API lets trusted backend services list formats and account usage, create private digitising or conversion jobs, inspect status and validation details, retry eligible jobs, and use signed preview or download URLs. It uses scoped Bearer API keys and publishes an OpenAPI 3.1 description. API keys must not be embedded in browser or mobile client code.

Yes. Compatible AI clients can connect to the remote Streamable HTTP MCP endpoint with OAuth 2.1 and PKCE. After the user authorizes the connection, an agent can check formats, usage and owned jobs, or create a processing preview after confirming the upload with the user.

MCP is designed for user-authorized AI clients: the user signs in through OAuth, grants the `mcp:use` scope and can revoke the connection. The REST API uses scoped keys for trusted backend code. An AI client should not ask for the user’s password or a long-lived API key.

Yes. Processing jobs are account-bound regardless of how they are created. Source files, job history and output metadata are not public pages, and preview or download links are authorized or short-lived signed URLs. Filenames and uploaded content are treated as data, not agent instructions.

Yes. The converter creates single-design JEF+ and standard stitch-only JPX files and validates their stitches, dimensions and end command. EMB, ART and JAN remain unsupported because reliable production writers are not available.

Some formats store full colour information, while others store only colour-change stops. You may need to assign your preferred thread chart at the machine.

Batch selection is available for accounts with batch processing enabled. Free processing accepts one file at a time, while each batch source is validated and shown as an individual result.