# Hardware barcode scanners and QR codes

> Dedicated 2D imagers decode a QR in tens of milliseconds, tolerate motion and poor light far better than phones, and type the result straight into any software as keyboard input. Rule of thumb: above roughly 200 scans per day per station, a purpose-built imager pays for itself in speed and error rate.

Source: https://useqr.app/docs/scanning/hardware-barcode-scanners-and-qr · Last reviewed 2026-08-21 · UseQR is free forever, no signup.

---

## What a 2D imager is

A hardware "QR scanner" (the class of device made by Zebra, Honeywell, Datalogic and
similar) is a small camera, its own illumination, and a decoder chip in one housing.
Pull the trigger and it captures a frame under its own light, decodes on-board, and
emits the payload text. No app, no autofocus hunt, no tapping a banner.

One critical check before buying: it must be a **2D imager**, not a laser scanner. A
laser physically cannot read QR codes, for reasons explained in
[2D imager vs laser scanner](/docs/scanning/2d-imager-vs-laser-scanner).

## Why it beats a phone at volume

| Property | Phone camera | 2D imager |
|---|---|---|
| Trigger to decode | ~1–2 s (wake, aim, focus, tap) | **tens of milliseconds** |
| Ambient light | Needs decent light | Irrelevant, brings its own |
| Motion tolerance | Poor in dim light | High, fast shutter plus pulsed illumination |
| Ruggedness | A dropped phone is a bad day | Rugged models rated for repeated 1.5–1.8 m drops to concrete |
| Output | Opens a link or shows text | Types the payload into whatever has focus |
| All-day ergonomics | Thumb on glass | Trigger grip designed for thousands of cycles |

The latency gap is the one that compounds. At two seconds per phone scan versus a
tenth of a second on an imager, a 500-scan day differs by a quarter of an hour of pure
scanning time, before counting mis-scans and re-tries, where the imager's advantage in
[low light](/docs/scanning/qr-scanning-in-low-light) and
[motion](/docs/scanning/motion-blur-and-qr-scanning) widens further.

## Interface modes: how the data gets out

- **Keyboard wedge (USB-HID).** The scanner enumerates as a keyboard and *types* the
  decoded text, usually with a configurable Enter suffix. This is the magic for
  non-developers: put the cursor in a spreadsheet cell and scan: payload, new line,
  next cell. No integration work at all.
- **USB-COM / serial.** The payload arrives on a virtual serial port for software to
  read: cleaner for real applications, since nothing depends on which window has
  focus.
- **Bluetooth HID** for cordless use, pairing like a wireless keyboard.

Configuration is famously self-referential: you set suffixes, modes and symbologies by
scanning **configuration barcodes** printed in the manual.

Two wedge-mode gotchas worth knowing before they cost you an afternoon. First, HID
wedges emulate keystrokes, so a **keyboard-layout mismatch** (a US-layout scanner
typing into a UK or German layout) silently swaps characters like `@`, `#` and `z`/`y`,
garbling URLs and serials. Second, the wedge types whatever the code contains, so a
malicious payload lands straight in your active window; scan untrusted codes with a
[browser decoder](/scan) that shows text instead.

## When to buy one

The working rule: **above ~200 scans per day per station, buy the imager.** Below
that, a phone plus a batch-scanning workflow is usually fine: the options are laid
out in [batch scanning many QR codes](/docs/scanning/batch-scanning-many-qr-codes).
Entry-level corded imagers are cheap relative to the labour they save; the expensive
part of scanning is always the human holding the device.

Typical tipping points: goods-in at a warehouse, ticket gates at an event, asset
audits, production-line tracking, all covered from the label side in
[QR code inventory management](/docs/ecommerce/qr-code-inventory-management). If you
are also *printing* the codes at volume, generate them consistently with the
[bulk generator](/bulk) and test a sample with the [validator](/validate) before
committing to a label run.

## FAQ

### Can a normal barcode scanner read QR codes?
Only if it is a 2D imager. Camera-based imagers read both 1D barcodes and QR codes; laser scanners sweep a single line and can never read a QR code regardless of settings. The spec sheet will say "2D" or "imager" explicitly.

### How does a hardware scanner get data into my software?
Most commonly as a keyboard wedge: the scanner enumerates as a USB keyboard and types the decoded text into whatever has focus, usually followed by Enter. Serial and Bluetooth modes exist for tighter integrations.

### When is a hardware scanner worth buying instead of using phones?
At roughly 200 or more scans per day per station. Below that, phones with a batch workflow cope; above it, the imager's sub-100 ms decode, motion tolerance and trigger ergonomics repay the hardware cost quickly.

### Why does my scanner type wrong characters?
A keyboard-layout mismatch. Wedge scanners emulate keystrokes, so a scanner configured for a US layout typing into a system set to another layout swaps symbols and letters. Set the scanner's layout via its configuration barcodes to match the host system.

## Try it

- https://useqr.app/scan
- https://useqr.app/bulk
- https://useqr.app/validate