Zebra's label software is free. Here is exactly where it stops.

ZebraDesigner does not list Windows printers. It lists ZDesigner drivers. Zebra's own release notes put it plainly — “the ZebraDesigner label design application requires the ZDesigner Windows driver to communicate with your printer” — and that one sentence explains every surprise in the printer list.

“It prints upside down compared to the screen”

There is a rotate 180° tick box on the Options tab of the ZDesigner driver's properties. If your print comes out inverted relative to what you designed, that is almost always it. Untick it and the label matches the screen.

Do not go looking for a mirror setting. There is one — Mirror Image, on the Advanced Setup tab — and it is a different thing entirely. Mirrored means the text reads backwards, as if through glass. Rotated means upside down but still readable. If your label is readable, the mirror box is not your problem and should be left alone.

Where you untick it decides how far the fix reaches. Reached through the design program, it applies to that label. Set in the Windows printing preferences for that printer, it becomes the default for everything that prints to it. Set it in Windows, or you will meet the same label upside down again from a different program.

One more place it can live: the printer itself holds a print orientation in its own firmware, settable from the front panel. If the driver setting is off and the label is still inverted, that is where to look next.

“The label is the wrong size, or printing off the edge”

Three things hold an opinion about how big your label is: the document, the driver, and the stock actually in the printer. The print is only right when all three agree, and the software will not tell you when they do not.

The tell is a margin you never typed. If your label is set narrower than the driver's page, the design program pads the difference out as a margin on one side — so a label that measures 76 mm sitting in a driver page set to 100 mm quietly acquires a 24 mm margin, and everything shifts. Nothing is broken; two numbers simply disagree.

Measure the label itself — across and down, the liner does not count — and put that same number in both places. If you are not sure what you have got, we can tell you from the part number, or from the roll.

That is worth knowing if anything other than a person is ever going to print your labels. Design it visually, tick the box, print once, and you have the commands your printer actually obeys — ready to be sent by a script, a handheld application, or a system that prints without anybody opening a designer.

And the driver's settings travel with it. Darkness, print speed, thermal transfer or direct, how the printer finds the gap between labels, which way up it prints — all of it is written into the file alongside the design. That is genuinely useful, because it means the file prints the same from anywhere. It is also the first of two things to be careful about.

“Careful what you send it to”

Because those settings are in the file, sending it to a shared printer reconfigures that printer for whoever prints next. On a machine that one department uses for one label, that is exactly what you want. On the printer the whole warehouse shares, it is how somebody else's labels come out too dark on Monday morning. Know which sort you are aiming at.

“Strip the front of the file”

The file does not begin with a printer command. It begins with a byte-order mark and a control character — four bytes that are not ZPL and that your text editor will not show you. Printers often swallow them without complaint, which is worse than if they did not, because the day one does not you are looking at the design rather than at four invisible bytes.

If you are sending the file raw from your own code, start from the first printer command and throw away everything before it. That one line of defensive code is the difference between "it works on my PC but not from the system" and it just working.

“It is one label, not a template”

This is the limit, and it is the honest end of what free will do. Whatever the operator typed at print time is baked into the file as fixed text. Print a use-by label with one date and you get a file that prints that date, for ever. There is no placeholder left in it for your system to fill.

For labels stored in the printer with fields your system fills in, Zebra has a separate free tool aimed squarely at developers, and BarTender exports templates too. But for the common case — a handful of fixed label layouts that a system needs to fire off on demand — print to file out of the free edition is a perfectly respectable way to get them, and it costs nothing.

“Will it run on what we have?”

Almost certainly. It is a Windows program — 10 or 11, or Server 2019 and later — and it wants about 2 GB of memory, a gigabyte of disk, a screen of at least 1366 by 768, and the Microsoft .NET Framework version 4.7.2, which most machines already have. There is no Mac version, no Linux version and no browser version, and there is not going to be one.

Windows 7 and 8 were dropped some years ago along with the older .NET versions, so a machine still on those will not take the current release. That is usually a sign the machine has a bigger problem than label software.

“Is it still being looked after?”

Yes, and that is a fair question about free software. Version 3 arrived in 2019 and has been updated steadily ever since — the most recent build at the time of writing is from late 2025, and the changes in between have been real ones: licensing moved to a new platform, the GS1 standard was brought up to date more than once, newer Windows Server versions were added, and a security hole in the installer was closed.

It is not abandonware and it is not a stripped demo designed to annoy you into buying something. It is Zebra making sure that a printer they sold you is easy to print to, which is a motive you can rely on.