This article explains how Hatch and Wilcom embroidery software handle embroidery files during import, how automatic design adjustments and stitch-to-object conversion can alter the internal structure of a design, and why disabling these features is often recommended when importing purchased embroidery files.
This behavior is software-driven and applies to designs from all designers.
Automatic design adjustments in Hatch and Wilcom
Hatch and Wilcom share the same core embroidery engine. By default, both programs include automatic features intended to optimize or “improve” designs during import. These may include:
- Automatic stitch adjustment
- Stitch-to-object (outline/OBJ) conversion
- Internal optimization based on perceived stitch type
- EMB grading logic
- Reconstruction of stitch paths
While useful in some workflows, these features can significantly change how a design is represented internally.
Why designs change on import
When automatic adjustments are enabled, the software may attempt to reinterpret stitch data and rebuild it into embroidery objects. This process can:
- Split satin columns into multiple segments
- Expose travel stitches more aggressively
- Create the appearance of many small fragments
- Make a design look inefficient or chaotic in software
The stitch data itself may not be wrong. What changes is the software’s internal interpretation of that data.
Hatch-specific recommendation
If you are using Hatch, it is recommended to:
- Avoid resizing the design immediately after import
- Disable automatic design adjustments when importing purchased files
- Preserve the design as stitches rather than reconstructed objects
Where to change this in Hatch
- Open the upper menu
- Select Software Settings
- Select Embroidery Settings
- Choose the option:
Leave the stitches as individual stitches, EMB grade D
This setting instructs Hatch to preserve the original stitch data and avoid automatic reconstruction.
Official Hatch documentation related to settings and behavior:
https://hatch.embroideryhelp.net/v3/en/downloads/QuickStartGuide.pdf
https://hatch.embroideryhelp.net/v3/en/downloads/QuickReference.pdf
Wilcom stitch-to-object conversion behavior
Wilcom includes explicit functionality for converting stitches into embroidery objects (including outline objects). This is a documented feature and is commonly triggered when opening machine files.
When enabled, Wilcom:
- Processes stitch data
- Attempts to recreate embroidery objects
- Alters the internal structure of the design
This behavior is documented by Wilcom in its official help materials:
Wilcom – Converting stitches to objects
https://docs.wilcom.com/embroiderystudio/e4/en/MainHelp/Modifying/functions/Converting_stitches_to_objects.htm
Wilcom – Opening machine files and conversion behavior
https://docs.wilcom.com/embroiderystudio/e4/en/MainHelp/Production/convert/Open_machine_files.htm
Visual comparison and interpretation
When comparing the same design imported twice:
- Once with automatic adjustments enabled
- Once with adjustments disabled
The adjusted version may appear fragmented or overly complex in software.
The unadjusted version more accurately reflects the original stitch structure.
Both versions may stitch similarly on the machine, but only one preserves the original digitizing intent.
Why this affects all purchased designs
This behavior is not specific to:
- A particular designer
- A specific font
- A marketplace
Any purchased embroidery design can appear altered if:
- Automatic adjustments are enabled
- Stitch-to-object conversion occurs
- Machine files are reconstructed on import
Understanding and controlling these settings is essential for accurate evaluation of embroidery files.
Key takeaway
If a design looks unexpectedly fragmented or altered inside Hatch or Wilcom, the most common cause is automatic design adjustment or stitch-to-object conversion during import, not a digitizing error.
For predictable results:
- Import designs as stitches
- Disable automatic conversion features
- Avoid major resizing immediately after import
This approach preserves the original stitch data and prevents software-generated artifacts from being mistaken for design flaws.