EMB
Status
| Field | Value |
|---|---|
| Extension(s) | .emb |
| Common ecosystem | Wilcom |
| Format family | Native working file |
| Satin Studio status | Researching |
| Open / import | No |
| Export | No |
| Confidence | High for ecosystem role. |
What it is
EMB is Wilcom’s native working format. It can preserve editable outlines, stitch settings, lettering, colors, icons, generated stitches, and software-specific properties.
Satin Studio direction
High-value import research, but much harder than stitch-stream support because editable object semantics matter.
Versions and variants
EMB is a native working format and is versioned by software generation. Support would need a version-specific object-model mapping, not just stitch parsing.
File identification notes
Reported EMB-family files contain vectors, icon data, color data, and stitch data. Some internal data is compressed and may use additional byte transformation before or around compressed streams.
Observed structure notes
- EMB-family files are native working documents. They may contain object vectors, icons/previews, colors, generated stitches, settings, and compressed internal streams.
- Any useful parser needs a version marker and an object stream map before stitch data can be interpreted safely.
Structure sketch
EMB is a native working file. A parser must find objects and metadata before extracting stitches.
struct EmbContainer<'a> {
version_or_header: &'a [u8], // version-specific
object_streams: &'a [EmbStream<'a>],
compressed_streams: &'a [EmbStream<'a>],
}
struct EmbStream<'a> {
kind: &'a str, // vectors, icons, colors, stitches, settings, unknown
payload: &'a [u8],
}
What we still need
Legally usable files, version identification, compression/container notes, and an object-model mapping strategy.