Keep the Editable Master and the Machine Export in Order

A folder containing twelve versions of a fern design can be less useful than a folder containing three clearly identified files. Which one still contains editable shapes? Which one went to the machine? Which one produced the sample you liked? If those answers depend on memory, the next change can undo work you meant to keep.

Give each design a traceable route from its best available source to a checked machine export. This guide addresses two tasks: preserving what you can still edit, and checking what changed during export or conversion. You will finish with a small archive structure and a comparison record you can reuse.

1. Identify what you actually received

Start with the untouched download or delivered package. Keep its instructions, colour worksheet, preview and licence together. Make a working copy before opening and saving anything. A file that software can open is not necessarily a file it can edit in the same way as its own native project.

An object-based embroidery master may retain shapes, stitch types, underlay, density, sequence and other construction settings. A machine export primarily carries the stitch instructions and supported machine commands needed for production. Reopening that export may give you individual stitch points or reconstructed objects; it does not necessarily restore the original design decisions.

Extensions such as EMB, ART and JAN are encountered in native design workflows, but inspect the contents in compatible software. Saving imported stitches inside a native container does not magically recover missing shapes. If your purchase includes only machine files, preserve those original files as your best available source. Do not label one “editable master” unless you have established what remains editable.

Artwork needs a separate place too. A JPG, PNG or ordinary vector drawing provides visual information, not a complete embroidery stitch plan. Digitizing adds decisions about direction, support, stitch order and fabric behaviour. Some embroidery software stores project settings within SVG, so an SVG used as an embroidery project is different from an ordinary illustration with the same extension. The contents and the software matter.

A PDF reference book is likewise not a machine file. Keep it with your visual references. When commissioning a conversion from artwork, state whether you need a machine-ready export, an editable project, or both; do not assume the delivery includes every source file.

2. Choose an export using the exact machine requirements

Read the receiving machine’s manual before choosing an output format. Record the supported extension, any required version, usable embroidery field and relevant design limits. Older equipment may also have media, filename or folder restrictions. Keep those details in a machine profile with the manual reference rather than relying on a remembered rule for an entire brand.

The following table is an orientation guide to the files you may find in an archive. It is not a compatibility list for a particular machine, and no extension guarantees suitable digitizing or the correct design size.

Software support has two directions: reading and writing. Being able to open a format does not prove that the application can export it. Compare the separate import and export lists in the software’s documentation. For an example of that distinction, see this documented list of readable and writable embroidery formats.

Choose software by the operation you need. A viewer may be enough to inspect a delivered file; changing the underlying construction requires more. The Stitchesly guide to embroidery software functions helps separate those requirements without buying a digitizing package just to organise downloads.

3. Separate the source, working version and delivery copy

Use one project folder per design. Inside it, separate the original delivery, editable work, machine exports and supporting records. These are example folder names, not instructions imposed by a machine or application. Your transfer device may need a much simpler structure.

• Original: the untouched package as received.
• Working: editable projects and deliberate revisions.
• Exports: machine files generated from named revisions.
• Records: thread sheets, export settings, sample notes, previews and permissions.

Name the working revision before you export. For example, fern-r03 identifies a revision more reliably than fern-final-new. In the archive, a descriptive export name might be fern-r03-70x95mm.pes. Those dimensions are an illustrative naming example, not measurements from the photographs in this article. Always take the real values from your own file.

If the machine requires short names, use a shorter transfer name and record the relationship. The archive can retain a descriptive name while the production copy uses a permitted one. Avoid renaming several unrelated designs to the same short filename on the same transfer device.

Keep each export connected to its source revision. If revision three changes the stem sequence, export it again from revision three. Do not patch an old machine file and leave its record pointing to an earlier master. Where a stitch-level repair is unavoidable, save it separately and explain the repair so that a later export does not silently replace it.

4. Export a copy, then reopen that copy

Use the application’s export or save-copy operation and select the destination format explicitly. Changing .pes to .dst in a filename changes the label, not the data. Keep the editable project in its native form and save the machine output separately.

Menu names vary. This official export workflow, for example, describes saving a machine-format copy while retaining the SVG project for later changes. Follow the equivalent documented process in your own application rather than treating one program’s menu sequence as universal.

Close or move away from the source view, then open the exported file itself. Confirm the filename and folder before inspecting it. Otherwise, it is easy to review the unchanged master and believe you have checked the conversion.

Record the following comparison. Fill the cells from your software; the blank record deliberately contains no invented stitch counts or claimed test results.

A count difference deserves investigation, but matching counts are not proof of matching behaviour. Programs may report commands differently, and identical totals can conceal a changed sequence. Inspect the stitch simulation, especially travel between separated elements and the transitions around appliqué steps. A preview image alone cannot show when the machine stops.

Do not use conversion as a repair for unsuitable density or a large resize. Changing the delivery format does not decide how much thread a small letter can hold. Return to a suitable source, obtain a correctly prepared size, or ask the digitizer to revise the design.

5. Keep thread information outside the thumbnail

A design that opens in unexpected colours has not necessarily changed its stitch order. Some formats or receiving programs substitute display colours. DST workflows particularly need a separate thread reference because the intended thread identity is not reliably communicated by a coloured preview alone.

Keep an ordered thread sheet with the export. Record each colour block in sequence, including a repeated colour that returns later. “Green, gold, charcoal” is a palette; “stem, leaves, seed heads” is a sequence of tasks. Depending on the design, the same thread can appear in more than one task and more than one block.

For appliqué, identify placement, securing and finishing steps explicitly. Their screen colours may be chosen to force useful stops rather than to describe the fabric colour. On equipment with several needles, also verify the assignment at the machine. The archive should explain the intended sequence without assuming that every receiving system interprets colour information identically.

If supplied measurements or sequence notes are unfamiliar, begin with reading embroidery pattern information. Use the actual design sheet as the reference when comparing the export, not a thumbnail remembered from a shop page.

6. Attach the sample to a specific file revision

After the digital checks, stitch a sample on the intended fabric with the intended support. Follow the first stitch-out workflow if you need a controlled setup. Opening successfully in desktop software establishes only that the software can interpret the file; it does not establish the final result on fabric.

Give the sample a record containing the export filename, date, machine, hoop, fabric, stabilizer, needle and thread. Note any adjustments made on the machine, including rotation or resizing. Without that note, the saved file and the stitched result may no longer describe the same setup.

Inspect the unhooped sample. Record what happened at stops, whether travel threads need attention, and whether outlines meet the intended edges. Photograph the front and back with the sample identifier. A pleasing front alone can hide problems that will matter on the next run.

Mark the export “tested” only after that process, and state the setup for which it was tested. Approval on woven cotton does not automatically approve the same file for a stretch garment. Preserve the earlier accepted version when starting another experiment.

7. Make the archive useful after the next change

Keep a second copy of the archive in a separate backup location. A USB stick used for machine transfer is a delivery tool and should not be the only home of the master. Periodically check that a backed-up project opens and that its supporting records are present.

Before a batch conversion, choose a small representative set: a simple design, one with several colour changes, and any special process you actually use. Compare their reopened exports before processing the full library. Keep companion files together where the receiving workflow requires them. A successful batch report is not permission to delete the originals.

Preserve the supplied licence and delivery terms with the design. If you plan to share a converted file or send it to a production partner, check those terms or request clarification from the supplier. File organisation should retain that information alongside the technical record. For Stitchesly download questions, use the order and download support page.

If the machine does not display an otherwise checked export, pause the archive work and investigate the transfer route and model requirements. Do not cycle through random conversions or overwrite the source in search of a visible thumbnail.

The archive is ready when you can answer four questions without guessing: where is the untouched source, which revision was exported, what changed in the export, and which exact file produced the retained sample? That is enough structure to keep a small design collection dependable as it grows.