Labelixa ZPL for VS Code
See the Zebra ZPL label you are editing — rendered, without a printer —
and get the label linted in the Problems panel while you work.
What it does
Preview the label under your cursor. Put the caret anywhere inside a
^XA … ^XZ block and run Labelixa: Preview the label under the cursor.
The block is rendered by the Labelixa API and shown
beside your code.
If the cursor is between labels, nothing is rendered and the extension
says so. Showing the nearest label instead would let you edit one label
while looking at another — a quiet way to ship the wrong thing.
Lint while you work. On save, the file is checked and the findings land
in the Problems panel with their real line and column: unknown commands,
unterminated fields, out-of-range parameters, RFID notes, and more.
Quota, plainly
- Linting does not consume label quota. It only shares the rate limit.
That is why it can run on every save.
- Rendering a preview does consume quota — so it is never automatic.
It happens only when you run the preview command.
Anonymous use is free and rate limited. To use your own quota, put your key
(lbx_… from labelixa.com/panel) into
labelixa.apiKey.
Settings
| Setting |
Default |
Meaning |
labelixa.apiKey |
empty |
Your API key. Empty = anonymous free tier. |
labelixa.baseUrl |
https://api.labelixa.com |
Change only for a self-hosted Labelixa. |
labelixa.dpmm |
8 |
Printer resolution (8 dpmm = 203 dpi). |
labelixa.widthIn / labelixa.heightIn |
4 / 6 |
Label size in inches. |
labelixa.lintOnSave |
true |
Lint on save. |
What it does not do
- It does not print. It renders what a printer would produce, from
our own ZPL engine — a simulation, not a device.
- It is not a substitute for a test print. Fonts, media calibration and
darkness live in the printer; the preview cannot see them.
- The caret character is fixed to
^. ^CC (change caret) is not
handled — the Labelixa engine does not handle it either, so the preview
is exactly as capable as the renderer behind it, no more.
Privacy
Your ZPL is sent to the Labelixa API to be rendered and checked. The
diagnostics endpoint is stateless: the label is not written to disk and not
logged, and the response carries positions and codes rather than your label
text. See labelixa.com/security.
Source
Developed in the open at
github.com/iskendererdogan-stack/Labelixa
(vscode/). Bug reports: labelixa.com/contact.
MIT licensed.
