ZPL-Befehlsübersicht

Suchen Sie häufige Zebra-ZPL-Befehle, Beispiele und Hinweise für Layout, Text, Barcodes, Grafiken und Geräteeinstellungen.

ZPLZebraEtiketten-Workflow

^XA

Start label format

^XA

Wrap every label format with ^XA and ^XZ.

^XZ

End label format

^XZ

Missing ^XZ is one of the easiest ways to break a job.

^PW

Print width

^PW812

Set the label width in dots.

^LL

Label length

^LL1218

Set label length in dots.

^FO

Field origin

^FO50,80

Place the next field at x,y coordinates.

^FT

Field typeset

^FT50,120

Alternative field positioning, often baseline-oriented.

Font selection

^A0N,40,40

Choose font, rotation, height, and width.

^FD

Field data

^FDHello^FS

Text or encoded data for a field.

^FS

Field separator

^FS

Ends a field. Missing separators cause confusing output.

^GB

Graphic box

^GB400,2,2^FS

Draw lines, boxes, and separators.

^BY

Barcode defaults

^BY3,2,120

Set barcode module width, ratio, and height defaults.

^BC

Code 128 barcode

^BCN,120,Y,N,N

Common for shipping and inventory labels.

^BQN

QR Code

^BQN,2,6^FDQA,https://example.com^FS

Use model 2 QR with module size.

^BX

DataMatrix

^BXN,5,200

Common for compact 2D labels.

^CI28

UTF-8 encoding

^CI28

Use before UTF-8 text fields.

^LH

Label home

^LH0,0

Offset the whole label coordinate system.

~SD

Print darkness

~SD15

Printer setting. Test carefully on real media.

^PR

Print speed

^PR4

Printer speed can affect barcode quality.

How to use this tool

Start with sample data

Use the default values to understand the expected ZPL shape.

Adjust for your printer

Check label size, DPI, barcode data, and printer-specific settings before production.

Preview or copy the result

Use the main ZPL Viewer for final visual checks whenever the tool generates ZPL.

Frequently Asked Questions

No. It helps catch obvious layout and data mistakes before final hardware validation.

Treat them as a starting point. Review printer model, DPI, media, and business data before production printing.

Some printer-language conversions are not one-to-one. A clear migration map is safer than pretending every ZPL command has a perfect EPL or CPCL equivalent.