Barcode Reader

Scan and decode barcodes from uploaded images or live camera.

Tested tool guide Tested browser tools Checked August 16, 2026

What Barcode Reader does, with a checked example

This tool reads a barcode from an image you upload or from your device's camera and extracts the raw string encoded in it, along with the symbology it detected (EAN-13, UPC-A, Code 128, QR, and similar formats). It locates the bar pattern or module grid in the frame, decodes it, and where the format includes a check digit, validates that digit. The thing people expect and don't get: it returns the encoded data, not the product name, price, or manufacturer - a UPC number still has to be looked up elsewhere to mean anything.

Worked example

A concrete input and expected output from the current implementation.

Input

A clear photo of a product's EAN-13 barcode where the printed digits under the bars read 5901234123457

Expected output

Format: EAN-13
Data: 5901234123457
Check digit: valid

Summing the first 12 digits with alternating weights of 1 and 3 gives 83; the EAN-13 check formula (10 - (83 mod 10)) mod 10 = 7, which matches the printed final digit, so the read is reported as valid.

How the result is produced

Capture and localization

The tool takes a single video frame or an uploaded image and searches it for a barcode-shaped region: a run of parallel bars of varying width for 1D symbologies, or a square module grid with finder patterns for 2D symbologies like QR. It crops and normalizes that region before attempting to decode it, so framing, focus, and lighting in the source image directly affect whether anything is found.

Decode and checksum validation

Once a candidate region is found, the tool reads the bar/space or module pattern into raw data and identifies which symbology produced it. For formats that define a check digit or checksum (EAN-13, UPC-A, Code 39, and others), it recomputes that digit from the decoded data and flags a mismatch rather than silently returning a corrupted read.

Good uses

Pulling the GTIN/UPC number off a product photo when you don't have a dedicated handheld scanner
Checking that a barcode rendered on packaging artwork or a label proof actually decodes to the intended number before it goes to print
Reading a Code 128 or QR payload off a screenshot or scanned document during development or testing

Limits and checks

It reports the encoded string and format only - it does not query GS1, a UPC database, or any catalog to tell you what product a number belongs to
Blur, glare, low contrast, a cropped or angled barcode, or a busy background can cause no detection at all rather than a wrong-but-plausible read
A valid checksum only proves the digits are internally consistent for that symbology; it does not prove the barcode matches the product it's printed on, and forged or mislabeled barcodes can still pass

Common questions

Can it tell me what product a scanned UPC or EAN belongs to?

No. It only returns the raw number and the symbology it detected. Matching that number to a product name, brand, or price requires looking it up in a separate product database, which this tool does not do.

Does it handle QR codes as well as traditional 1D barcodes?

Barcode readers built for the browser typically decode both linear formats (EAN-13, UPC-A, Code 128, Code 39) and 2D formats like QR and Data Matrix. If a scan of a QR code returns nothing, try a sharper, better-lit image before assuming the format isn't supported.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.