AutoDigitizing is a paid feature not included in standard API plans. It converts an image → EMB → TrueView PNG / machine file. It uses specific API calls. It is charged per call because these requests are resource-intensive. Usage can be tracked in your API Dashboard → Stats → Hits.
What is AutoDigitizing?
In the EWA API, AutoDigitizing means converting an image into an embroidery design:
- You upload an image (bitmap or vector).
- The Wilcom Embroidery Engine processes it and generates an EMB file, Wilcom’s native design format.
- From this EMB file, the system can produce:
- A TrueView PNG image, and/or
- A machine file – e.g. DST
So AutoDigitizing is a two-step process: image → EMB → output files.
Types of AutoDigitizing calls
There are two main categories:
Why not in standard plans?
AutoDigitizing is resource-intensive.
- Processing images into embroidery designs places a heavy load on the API server.
- Workload increases with the size and complexity of the image.
- Because of this, AutoDigitizing is charged per call, not bundled into standard subscription plans.
How to check AutoDigitizing usage
- Log into your API account and go to the Dashboard.

- Select Stats → see total number of API calls.
- Choose a time period – e.g. 'last 30 days'.
- Click Hits to view all API call types.
- If your account includes AutoDigitizing, you’ll see them listed at the bottom.

- Select a call type to see detailed usage – frequency, peaks, quiet periods, etc.
