Put a USB Receipt Printer on the Network

There are four ways to put a USB-only receipt printer on your network: a generic USB print server box ($20–60), a Raspberry Pi running a small print service, the vendor route (a new interface card or a new printer), or a small bridge node that presents the printer as a normal network printer on port 9100. Which one fits depends on a question most guides skip: does your POS only need to send bytes to the printer, or does it also need to hear back — paper out, cover open, drawer status?

If it only needs to send, almost anything below works. If it needs to hear back, most of the cheap options quietly fail.

Why this problem exists

USB receipt printers are the cheapest printers you can buy — the $40–90 generics on Amazon's best-seller list are usually USB-only or USB-plus-serial. Ethernet models of the same printer typically cost $30–80 more, and name-brand network printers like the Epson TM-m30III run $275–541.

Meanwhile, most POS systems — tablets especially — expect a network printer: an IP address they can reach over the LAN, usually speaking raw ESC/POS (the command language nearly all receipt printers understand) on TCP port 9100 (see how port 9100 printing works). A tablet has nowhere to plug a USB printer in, and even a Windows POS often routes kitchen tickets by IP address, one per station (see kitchen printer setup).

So you have a cheap printer with the wrong plug. Here are your options, honestly compared.

Option 1: a generic USB print server ($20–60)

The classic answer is a small "USB print server" box: TP-Link, IOGEAR, and a rotating cast of unbranded ones. You plug the printer into the box, the box into your switch, and it forwards a TCP port to the USB port.

For one-way printing this often works. The catches:

• Most are one-way. They forward bytes to the printer but do not reliably return the printer's replies. ESC/POS status queries (DLE EOT — the command a POS sends to ask "do you have paper?") either time out or come back garbled. Your POS will show the printer as online when it's out of paper, or offline when it's fine.
• They're built for office printers. Many expect IPP or LPD, not the raw byte streams receipt printers use. Look specifically for "RAW/port 9100" support in the spec sheet before buying.
• Setup is a coin flip. Configuration utilities that only run on old Windows versions, fixed IPs on the wrong subnet, firmware from 2016. When they work, they work for years; when they don't, there's no one to call.

Option 2: a Raspberry Pi bridge

A Raspberry Pi running a small Python or Node service is the DIY answer, and it genuinely works: the Pi talks USB to the printer and exposes port 9100 (or an HTTP endpoint) to the network. If you can follow a terminal tutorial, our companion guide walks through the whole build: Raspberry Pi receipt printer server.

The honest trade-offs: a Pi is $35–80 plus an SD card and power supply, it boots in 30+ seconds after a power cut, and SD cards corrupt under the abrupt power-offs that happen constantly in restaurants. It's a great fit when you want the bridge to do more — logging, reformatting tickets, driving multiple devices — and a lot of machine when all you need is "make this USB printer look like a network printer."

Option 3: the vendor route

If your printer is a name-brand model with a modular interface (many Epson TM and Star TSP printers), the manufacturer sells Ethernet interface cards — typically $50–150, plus finding the right part number for your exact model. For a $300+ printer you already own, this is clean and supported.

For a $60 generic, the math fails: the card can cost more than the printer, if a card exists at all (most generics have soldered, non-modular interfaces). The vendor's real answer is "buy the Ethernet model," which means paying the price difference again and putting a working printer in a drawer.

Option 4: a bridge node that speaks printer, both directions

This is the gap we build for. A ProxyNode is a small device (ESP32-class, about the size of a matchbox) that plugs into the printer's USB port and joins your LAN. To your POS it looks like an ordinary network printer:

• It listens on TCP port 9100 and passes raw ESC/POS through to the USB printer — the same way a built-in Ethernet interface would.
• It answers DLE EOT status queries with the printer's real state: paper out, cover open, drawer open. This is the part generic print server boxes drop.
• It announces itself with mDNS, so software that discovers printers on the LAN can find it.
• It also serves a plain HTTP/JSON API on the side — POST /print, GET /status — for software that would rather send JSON than raw bytes.

And when a status reading genuinely can't be taken, it says so — the API reports known: false rather than guessing. A bridge that invents printer status is worse than no bridge.

Wiring and power notes

Whatever bridge you choose, two practical details:

• Power from the printer itself. Many receipt printers — including most Epson TM-m30 family units and a lot of generics — have a powered USB-A port intended to charge a tablet. That port can power a small bridge device, so the whole setup runs off the printer's own power brick: one outlet, and the bridge turns on and off with the printer. A Pi is the exception — it wants 2.5–5 A, more than most of those ports supply, so give it its own official power supply.
• Prefer wired Ethernet where you can. Receipt printing is latency-sensitive and kitchens are hostile RF environments. If the bridge supports both, cable it. If you must use Wi-Fi, give the bridge a DHCP reservation so its IP never changes — your POS is almost certainly configured to print to a fixed IP.

Which option, in one table

FAQ

Frequently asked questions

Can I just use a USB-to-Ethernet adapter cable?

No. Those adapters add an Ethernet port to a computer — they don't make a USB device reachable over the network. You need something with a processor in the middle: a print server box, a Pi, or a bridge node that speaks both USB and TCP.

What is port 9100 and why does it keep coming up?

Port 9100 is the de facto standard for raw network printing: the POS opens a TCP connection to the printer's IP on port 9100 and writes printer commands straight through. Nearly every POS that supports network receipt printers uses it, which is why any USB-to-network bridge needs to speak it.

Will my POS know the printer is out of paper through a bridge?

Only if the bridge passes status traffic both ways. POS software asks with the ESC/POS DLE EOT command and expects a one-byte reply. Most cheap print server boxes never return it; a Pi can if your software forwards replies; a ProxyNode answers it as a native feature.

Can the printer's USB tablet-charging port really power the bridge?

Usually, for small devices. Those ports typically supply 1–2 A at 5 V, which is plenty for an ESP32-class node and not enough for a Raspberry Pi 4 or 5 under load. Check your printer's manual for the port's rated output.

Is a used name-brand Ethernet printer a better buy than a bridge?

Sometimes. Used TM-T88 series printers are plentiful and nearly indestructible, and if your POS requires a certified model it may be your only option — see our guide to POS printer whitelists. If your POS just prints to an IP address, bridging the printer you already own is cheaper.

More on the network side of this: port 9100 printing explained · kitchen printer setup · the full Raspberry Pi build · everything else for operators at ProxyNodes for restaurants.