Supported file formats

Supported file formats

Embroidery designs are saved in one of two formats – ‘design’ (outline) or ‘machine’ (stitch) file format. WilcomWorkspace reads and writes a wide variety of file formats of both types.
 

File type

Description

Design

Design files usually contain digitized shapes and lines, selected stitch types and stitch values and effects.

Machine

Machine files generally contain stitches and machine functions and are only suited to specific embroidery machines.

Supported design file formats

WilcomWorkspace supports the following design file (condensed) formats:

Extension

Format

Read

Write

EMB

EmbroideryStudio design file (up to & including the latest release)

ART

artista V4.0 design files

 

ART42

Explorations project file

 

ART?0

BERNINA Embroidery Software file

 

JAN

Janome Embroidery Software file

 

Supported machine file formats

WilcomWorkspace supports the following machine file (expanded) formats:

Extension

 

Format

Read

Write

10O

 

Toyota

ARX

 

Bernina cross stitch file format

 

BRO

 

Bits & Volts

CSD

 

Singer / Poem / Huskygram

DAT

 

Hiraoka DAT

DSB

Tajima (Barudan)

DSN

 

Nova

 

DST

 

Tajima

DSZ

¥

Tajima ZSK machine format

EMX

 

Wilcom cross stitch file format

 

 

EMD

 

Elna

EXP

 

Melco

HUS

 

Husqvarna / Viking / Pfaff

INB

 

Inbro

JEF

 

Janome / Elna / Kenmore format (V1.0)

KSM

 

Pfaff

MJD

 

Time & Space MJD

PCD

 

Pfaff

PCH

 

Pfaff

 

PCM

 

Pfaff

PCQ

 

Pfaff

PCS

 

Pfaff

PEC

 

Deco / Brother / Babylock

 

PES

 

Deco / Brother / Babylock

PMU

 

Proel Win

UM

 

Proel DOS

SEW

 

Janome / Elna / Kenmore

SHV

 

Husqvarna / Viking / Pfaff

STC

 

Gunold APS stitch format

 

STX

 

Datastitch

TAP / MON

§

Happy

TBF

 

Tajima

 

U01

Barudan (TBD)

U03

 

Barudan FDR-3

 

VEP

 

Hiraoka VEP

 

VIP

 

Husqvarna / Viking / Pfaff

VP3

 

Husqvarna / Viking / Pfaff

XXX

Singer

Z01

£

ZSK TC machine format

† includes needle addressing data ¥ Two options – ZSK1 and ZSK2 (see note) § TAP and MON files are written together – TAP is the machine file, MON the header file.£ Used with Transport Code Disks (see note)


Note: ZSK1 format is used with older ZSK machines, generally those older than 1991 which have no more than 7 needles. ZSK2 is for newer ZSK machines, those characterized by a single top thread trimmer. The trim is the most significant differentiating factor between the two types. If the ZSK machine accepts Transport Code Disks, then ZSK TC Machine Format must be used.
    • Related Articles

    • Supported file formats

      The Wilcom Embroidery Web API supports a wide range of embroidery-specific and artwork input/output formats to ensure compatibility with professional embroidery workflows and machine types. This format support enables seamless integration across ...
    • How to convert designs to EMB file format

      Wilcom Workspace has the capability to convert designs to EMB file format. Follow the steps below on how to convert your design to EMB file format. Open the design you wish to convert. You may drag and drop the design or click Upload from a folder. ...
    • About Embroidery Formats

      In the Wilcom Web API service most API calls return an “embroidery” file. This Article provides background information on this topic. NATIVE AND MACHINE FORMATS Wilcom developed a “native” internal embroidery design format in EmbroideryStudio, called ...
    • When exporting to Machine File format (Z00 / ZSK), colors are not correct.

      Symptom / Scenario: Colors are not correct with the exported Z00/ZSK machine file formats. Affected ES version: ES e4.5 SOLUTION: By default, ZSK TC machine format is limited to 15 colors, but actually the *.Z00 file format itself actually supports ...
    • A file exported from Digital Edition File > Export Machine File does not appear on a ZSK machine.

      Problem: Files exported with File > Export Machine File method cannot be seen on a ZSK machine Cause: The issue is caused by the permissions assigned to a file which prevent the ZSK machine reading the file. Workaround: Setup and use Connection ...