PRO — $24.90/MO / 14-DAY PRO TRIAL ON SIGNUP
Print labels from a browser
Print to a thermal printer from your web app. A local LabelInn API on port 6631 takes the job, so you never ship printer-specific code.
HOW IT WORKS
Three screens from data to printed label.
No copy-paste, no hunting for templates. The same flow repeats for every record.
Printer status, quick actions and recent work in one place.
Text, barcodes, QR and images placed on the real media size.
See the label, the printer state and the copy count before it prints.
01
Who this is for
Developers whose web application has to reach a thermal printer sitting on a customer desk, without writing and shipping a print bridge of their own.
02
Step by step
- Install LabelInn on the machine the printer is connected to and enable the local API.
- From your web app, discover the local endpoint on port 6631 and check /local/v1/health.
- Post the print job with the design reference and the field values for this label.
- Read the job result back, and use the audit endpoint if you need a record of what printed.
Try it with your own data — signing up starts a 14-day Pro trial, no credit card. After that this feature needs Pro at $24.90/mo. Download now → | See pricing →
03
What you can do
- One request shape whether the target speaks ZPL, TSPL, TPCL or Epson — LabelInn generates the command stream.
- Works on the local network without internet: the edge queue holds jobs and syncs back when the connection returns.
- Fleet endpoints let the page list and health-check the printers actually present before it prints.
- The same job can be sent from the cloud API instead when the browser and printer are not on one network.
04
Technical details
| Local API port | 6631 (HTTP) |
|---|---|
| Health check | GET /local/v1/health |
| Printer discovery | GET /local/v1/fleet/printers |
| Offline | Queue holds jobs and syncs back |
| Plan | Pro; 14-day Pro trial on signup |
05
Limits and honest caveats
- LabelInn has to be installed on a machine that can reach the printer. The API routes the job; it does not create a network path to hardware that has none.
- A browser page can only call the local API when it is allowed to reach that host — plan for HTTPS and origin rules in your deployment.
- API access needs the Pro plan. Signing up starts a 14-day Pro trial so you can build against the real endpoints first.
06
Frequently asked questions
07
What we verified
The capability is implemented in the LabelInn codebase and the referenced source file names the exact format, engine, port or endpoint described on this page.
lib/services/edge/edge_http_server.dart + edge_server_config.dart — local LAN HTTP API on default port 6631 with /local/v1/* routes
ANY PRINTER
Design it, bind your data, print on the printer you already own.
Zebra, TSC, Toshiba, Epson and more — over USB, network or Bluetooth, with no driver to install.
PRICING
Start free. Pay when it earns its keep.
QUESTIONS / FAQ
Frequently asked questions
Can I print ZPL from a browser without building my own print bridge?
Yes — that is exactly the gap this fills. Your page posts a job to the LabelInn instance beside the printer, and LabelInn produces the command stream the printer actually speaks.
Does this need internet?
Not for the local path. The edge API runs on your own network on port 6631, holds a queue offline, and syncs back when the connection returns.
What if the printer is in another building?
Then use the cloud API instead: your app calls LabelInn, and the LabelInn runtime next to that printer performs the output.
KEEP GOING
Related pages
NEXT STEP / LABELINN
Print your Browser / web app data on the printer you already own
This feature runs on Pro — $24.90/mo, or $249/year (pay for 10 months, use 12). Signing up starts a 14-day Pro trial, so you can bind your own Browser / web app data and print a real label before you pay anything. · 14-day Pro trial on signup · No credit card required · Windows, macOS, Android, Web