Frequently asked questions about Labelixa: rendering issues, character support, error messages, the free tier and the on-premise option.
Why does my label render not at all or incorrectly?
The most common causes: an unsupported command (listed in the X-Warnings header), a wrong dpmm/size, or a CORS block from the browser. Check the X-Warnings response header first.
Are special characters (accents, ß, ı, ş, ğ) supported?
Yes. The engine uses a font that supports Latin Extended characters and assumes UTF-8. Send your ZPL as UTF-8; ^CI28 is recommended.
What does a rate-limit / quota error (429) mean?
You exceeded the per-second request or daily quota limit. Wait the time given in the Retry-After header, or move to a higher-limit plan with an API key.
Is there a guarantee for the free tier?
No. No plan comes with a service-level agreement (SLA); a dedicated SLA is provided only under a separate contract. For production use a paid plan is recommended.
What is the difference between the Label API and the Barcode API?
The Label API (/v1/printers) renders full ZPL labels. The Barcode API (/v1/barcodes) produces a single barcode without knowing ZPL; its audience and usage are different.
Can I run it on my own server (on-prem)?
Yes, the engine is stateless and can be packaged as a single Docker image. A custom font can be defined with LABELIXA_FONT. Contact us for enterprise requirements.
