Skip to main content

Text, monograms, and batch personalization

Text must stay editable until you intentionally convert it. Rebuilding names from outlines or stitches is avoidable damage.

Text objects​

A text object should keep:

  • content;
  • font asset;
  • size;
  • baseline or path layout;
  • alignment;
  • thread;
  • stitch style;
  • warnings;
  • personalization field name when used in a template.

Changing MASON to MAYA should not erase the stitch settings around the word.

Fonts​

Use TTF or OTF import when exact lettering matters. A project font travels with the project. A system font on one device is not a production guarantee on another.

The app should measure text before trusting it. Watch for:

  • tiny letters;
  • closed counters;
  • narrow strokes;
  • fragile serifs;
  • fabric pile;
  • satin width;
  • line spacing;
  • arc distortion.

If a warning says the text is too small for the chosen stitch style, believe the warning before the screen preview.

Stitch styles​

Lettering may use run, outline, satin-style, fill-style, or template-defined embroidery lettering. The safe choice depends on size, font, fabric, and thread.

Do not expect arbitrary fonts to become good satin lettering at arbitrary sizes.

Monograms​

A monogram is more than initials. It often includes frame, layout, thread order, fabric placement, and size constraints. Keep those parts together in the project so changing an initial does not break the design.

Batch personalization​

Batch personalization means one source project creates many checked outputs.

Each row should get its own:

  • text value;
  • preview;
  • warning result;
  • machine file when exported;
  • worksheet row when worksheets are used.

One bad name should not hide inside a clean batch.