TSPL to ZPL

Switching a line from TSC to Zebra usually stalls on the templates. Paste the TSPL here and LabelZoom interprets it — TEXT, BARCODE, QRCODE, BAR, BOX, BITMAP — into its label model, then writes native, editable ZPL II that any current Zebra accepts. The barcodes stay barcodes and the text stays text, so the converted label can still be edited, filled with data, and maintained.

Need to see the TSPL first? TSPL viewer. Archiving it? TSPL to PDF. Other migrations: EPL to ZPL, DPL to ZPL.

Preview: LabelZoom’s TSPL reader is newer than our ZPL engine and still improving. Compare the converted ZPL against a known-good print before rolling a template out. If something doesn’t match, let us know — reports go straight into what we fix next.

Paste your TSPL code

Note on Watermarks: Free online conversions include a LabelZoom watermark. Need to remove watermarks for production, or process thousands of labels per minute? Check out our REST API subscriptions

Native ZPL fields, not a bitmap of the TSC label — edit the result like any ZPL.

Barcodes and QR codes stay symbols: BARCODE and QRCODE become ^BC, ^B3, ^BQ.

One template for a mixed TSC / Zebra fleet during the changeover.

How to convert TSPL to ZPL

  1. 1

    Paste the TSPL job above, or upload the file — safer when it carries BITMAP graphics, whose binary bytes a clipboard can mangle. A ZIP of templates converts each one.

  2. 2

    Pick the density the TSPL was written for (203 dpi on most TSC desktop models, 300 on the high-resolution variants) and the label size that SIZE declares.

  3. 3

    Click Quick Convert, then copy the ZPL, download it, or send it straight to a connected Zebra. Open it in the ZPL editor to fine-tune fonts.

How TSPL commands map to ZPL

The converter works at the object level, so each TSPL element becomes the ZPL command that means the same thing.

TSPLBecomes ZPLNotes
SIZE^PW, ^LLInches or millimetres converted to dots at the chosen density
GAP, DENSITY, SPEEDdroppedPrinter configuration, not label content — set once on the Zebra
TEXT^FO ^A ^FD ^FSClosest ZPL font at the same physical height; rotation preserved
BARCODE^BC, ^B3, ^BE …Narrow/wide widths become ^BY module and ratio
QRCODE^BQError-correction level and cell size mapped
BAR, BOX^GBRules and frames
BITMAP^GFThe one element that stays a bitmap, in compressed hex

Other Supported Formats

TSPL ViewerTSPL to PDFEPL to ZPLDPL to ZPLZPL EditorZPL Viewer
Start converting now

Frequently Asked Questions

Everything you need to know about migrating TSPL templates to ZPL.

Is the output real ZPL or a bitmap of the TSC label?
Real ZPL. The TSPL is read into LabelZoom's label model as objects — TEXT fields, BARCODE and QRCODE symbols, BAR and BOX rules — and each is written out as the ZPL command that means the same thing: ^A fonts with ^FD data, ^BC / ^B3 / ^BQ barcodes, ^GB boxes. Only BITMAP graphics become ^GF, because they were bitmaps to begin with. You can open the result in the ZPL editor and change it.
What happens to TSPL's SIZE and GAP?
SIZE becomes the ZPL label width and length (^PW and ^LL, in dots at the density you choose). GAP describes the media to the printer rather than the label content, so it is dropped; set the gap on the Zebra with ^MN or its calibration routine once, not per label.
Will the fonts match?
TSPL's numbered bitmap fonts and the TTF fonts loaded on a TSC printer have no exact ZPL twins, so each is mapped to the closest ZPL font and scaled to the same physical height. Positions and sizes carry over; letterforms differ a little. Fields that must look identical are the ones to hand-tune afterward.
Why do barcode widths sometimes change?
TSPL specifies bars in narrow and wide element widths and ZPL in a module width and ratio (^BY), so the converter picks the ^BY that reproduces the same narrow bar. Where the ratio is not expressible exactly the barcode remains scannable but may be a dot or two wider. Check the preview against a printed original.
How accurate is the conversion, and can I run it in bulk?
The TSPL reader is newer than our ZPL engine: everyday templates convert cleanly and are tested against real production formats; unusual options may need a look, so compare before rolling out. For hundreds of templates, the REST API does the same conversion from a script, without a watermark.