ZPL Label Viewer

Preview Zebra ZPL labels in your browser with no upload: many labels at once, PNG and PDF export, and a check of every command

🔒 Your data stays in your browser: nothing you type or upload is sent to a server.

How it works

Paste ZPL, the language Zebra printers read, and the label is drawn as you type. Every ^XA ... ^XZ block becomes its own label, so a file with many labels shows all of them. The drawing is done by a WebAssembly engine that runs inside your browser: your ZPL is never uploaded, and once the engine has loaded, nothing needs a connection. Pick the print density (dpmm) and the label size, or leave Auto on to take them from ^PW and ^LL. The check panel lists, with line numbers, every command the engine draws, skips or does not know, plus missing ^FS and unbalanced ^XA / ^XZ.

Formula

dots = mm x dpmm (6 dpmm = 152 dpi, 8 = 203, 12 = 300, 24 = 600) 4 x 6 in at 8 dpmm = 812 x 1218 dots

Common questions

How do I preview a ZPL label without a printer?

Paste the code between ^XA and ^XZ (or open the .zpl, .txt or .prn file, or drop it on the page) and choose the print density of your printer: 6, 8, 12 or 24 dpmm, which is 152, 203, 300 or 600 dpi. Most desktop and industrial Zebra printers are 203 dpi (8 dpmm) or 300 dpi (12 dpmm). The label size comes from ^PW and ^LL if you leave Auto on; otherwise pick a preset such as 4 x 6 in or 100 x 150 mm. You can download each label as PNG, or all of them as a PDF at real size.

What is the difference between dpmm and dpi?

Both measure print density. dpmm is dots per millimeter, which is what ZPL tools and Zebra documents use; dpi is dots per inch, so dpi = dpmm x 25.4. ZPL positions and sizes are in dots, so the same code is physically smaller on a 300 dpi printer than on a 203 dpi one. A 4 x 6 in label is 812 x 1218 dots at 8 dpmm and 1218 x 1827 at 12 dpmm.

Is my ZPL sent anywhere? Why not use an online renderer?

No. The drawing engine is a WebAssembly file of about 7 MB (about 1.7 MB compressed) that this site serves and your browser downloads once, only when you open this tool. Rendering happens in a Web Worker on your device, so the ZPL, which often contains customer names, addresses and order numbers, never leaves it. Online renderers send the code to a server to get the image back. The last ZPL and settings are kept only in this browser (local storage).

Why does my label look different on the printer, or on Labelary?

The engine is Zebrash, an open source renderer that implements a subset of ZPL, and it is no longer actively developed. We tested it command by command: it draws Code 128, Code 39, Interleaved 2 of 5, EAN-13, PDF417, Aztec, QR Code and Data Matrix, boxes, circles, diagonal lines, ^GF images, ~DG / ^XG, ^DF / ^XF / ^FN templates, ^FB text blocks, ^FR and ^LR reverse printing, rotation and UTF-8 with ^CI28. Other barcode types (Code 93, Codabar, UPC-A, UPC-E, EAN-8, MSI, GS1 DataBar and more) are printed as small plain text, ^GE ellipses are not drawn, and ^BD MaxiCode makes the label fail. ^FB ignores the maximum lines and the hanging indent, ^LL / ^LS / ^LT / ^FP / ^CW / ^SN are ignored, and stored fonts and images are not available. Text uses the engine's own fonts, not the ones in the printer, so widths and line breaks can differ by a few dots. We did not compare pixel by pixel with Labelary or with a printer: print a test label before a production run.

Related tools