Launch

30% off your first month of Pro30% off month one$9.90 → $6.93

See plans
ZPL em PDF

Guide · Zebra printers

Your Zebra printed the ZPL code instead of the label

On a printer that does not speak ZPL, printed code is expected. On a Zebra it is not, and it always means the ZPL never reached the printer's interpreter as ZPL. Something in between wrapped it, the printer was told to speak another language, or the file was never raw ZPL to begin with. Four causes cover nearly every case. Before touching the printer, drop the file into the converter on this page: if a label appears, the file is fine and the problem is the path to the printer.

Checked on November 16, 2026

1. A driver rendered the code as a document

The most common cause, and the easiest to confirm. Opening the .zpl or .txt in Notepad and pressing Print, or printing it from any application, sends it through the Windows driver. A driver's job is to turn a document into a picture of that document, so the printer receives an image of your ZPL as text, and prints exactly that.

Zebra's own application note on this symptom says the same about its ZDesigner driver: ZPL embedded in a job sent through it comes out as printed commands. The file has to reach the printer raw, without a driver reformatting it.

  • Install a second queue for the same printer using the Generic / Text Only driver, and send ZPL to that one. It passes bytes through untouched.
  • Or share the printer and copy the file straight to it: copy /b label.zpl \\localhost\ZebraShare
  • Or, for a networked Zebra, send the file to TCP port 9100, which takes raw ZPL with no driver at all.

2. The printer is set to another language

Many Zebras speak more than one language, ZPL, EPL and, on mobile models, CPCL or line print, and only interpret the ones their device.languages setting allows. A printer left in line_print mode prints whatever it receives as plain text, so ZPL comes out as characters.

Ask it: send ! U1 getvar "device.languages" through a raw connection (Zebra Setup Utilities has a send-command box). If the answer is line_print or epl, set it with ! U1 setvar "device.languages" "zpl", followed by a line break. Zebra's support article on enabling ZPL also tells you to recalibrate the media afterwards (~JC).

3. The printer is in diagnostic mode

Communications diagnostics, sometimes called dump mode, makes a Zebra print every byte it receives, as text and hex, instead of acting on it. It exists for exactly this kind of troubleshooting, so the output looks like your ZPL with extra characters around it.

The ZPL command ~JD switches it on and ~JE switches it off, and the setting survives a power cycle. If somebody ran a diagnostic and never sent ~JE, every later job prints this way. Send ~JE through a raw connection.

4. The file is not raw ZPL

Carrier APIs rarely hand you the bytes directly. UPS, for one, returns the label inside a JSON response as base64, and a string of base64 sent to a printer is just text. Decode it first. If the file starts with ^XA once decoded, that decoded output is what the printer wants.

The other version of this is a file in Zebra's older language, EPL, which starts with a line like N or q812 rather than ^XA. A ZPL-only printer prints that as text too. The ZPL vs EPL page shows how to tell them apart from the first lines.

When the printer is not the point

If you only need the label on paper and the Zebra is in another building, or the printer is not a Zebra at all, convert the file to a PDF here and print that at 100% scale on anything. The conversion runs in this tab, and the file is not uploaded.

Check the file itself: if it renders here, the ZPL is fine

Drag the file in, paste the code, or pick it from your device

.txt · .zpl · .prn · .zip · .pdf · .png · .jpg — 5 labels a day

The conversion happens in your browser: your file never leaves your device.How that works
Free, no signupNo uploadNo watermarkBatches of many filesPDF · PNG · ZIP

Questions

Frequently asked questions

Why does my Zebra printer print ZPL commands as text?

The ZPL did not reach its interpreter as ZPL. Usually it went through a driver that printed it as a document (send it raw instead, with Generic / Text Only or port 9100). Otherwise the printer's device.languages is set to line_print or EPL, it is stuck in diagnostic mode (send ~JE), or the file is base64 or EPL rather than raw ZPL.

Should I use the ZDesigner driver to print a ZPL file?

Not for a file that is already ZPL. ZDesigner is for printing documents from applications. Zebra's application note says ZPL sent through it comes out as text. For a ready-made .zpl file, use a raw path: a Generic / Text Only queue, copy /b to a shared printer, or TCP port 9100.

How do I check which language my Zebra is set to?

Send ! U1 getvar "device.languages" over a raw connection, for example from Zebra Setup Utilities. If it answers line_print or epl, set it with ! U1 setvar "device.languages" "zpl" and recalibrate the media.

How do I know whether the problem is the file or the printer?

Drop the file into the converter on this page. If a label appears, the ZPL is valid and the problem is how it reaches the printer. If nothing renders, look at the file itself: it may be base64, EPL, or not a label at all.

Other guides