広告が嫌いですか? 行く広告なし今日 

Barcode Check Digit Validator

データ開発者数学

広告削除する？

入力

自動処理

出力

クライアント側

Enter a barcode to validate

検出されたフォーマット

チェックデジット

Expected Digit

Calculation Breakdown

バッチ結果

Barcode	形式	状態	期待値
結果はここに表示されます

広告削除する？

ガイド

Barcode Check Digit Validator

Validate the check digit of any retail or shipping barcode in one paste. The validator auto-detects the format from the digit count, recomputes the expected check digit using the right algorithm — GS1 modulo-10 for EAN/UPC/GTIN, modulo-11 for ISBN-10 — and shows a position-by-position breakdown so you can see exactly where a transcription error crept in.

使用方法

Paste a barcode into the Barcode field. Spaces, dashes, and dots are stripped automatically.
Leave 形式お 自動検出, or pick a specific standard if your input is ambiguous (an 8-digit number could be EAN-8 or UPC-E).
Read the verdict — valid means the trailing check digit matches what the algorithm expects, invalid means it does not.
Inspect the Calculation Breakdown to see the per-digit weights, the running sum, and the modulo result.
To validate many barcodes at once, paste them into 一括検証 — one per line — and the table populates per row.

サポートされている形式

EAN-13 – 13-digit retail barcode used worldwide on consumer products.
EAN-8 – 8-digit short form for small packages.
UPC-A – 12-digit code used across North America.
UPC-E – 8-digit compressed UPC; the validator expands it to UPC-A internally.
ISBN-10 – Legacy 10-character book identifier, may end in X.
ISBN-13 – Modern 13-digit book identifier, prefixed with 978 or 979.
GTIN-14 – 14-digit logistics-unit identifier used in shipping containers.

機能

Auto-detect format – Recognises seven barcode standards by length and prefix; override manually when needed.
ステップ・バイ・ステップの解説 – Position, digit, weight, and product for every contributing digit.
Expected vs provided – Surfaces the digit the algorithm expected so you can fix the wrong character at a glance.
バッチモード – Validate hundreds of barcodes in a single paste, with a per-row format and verdict.
Forgiving input – Spaces, dashes, dots, and lowercase X are normalised before validation.
100%クライアントサイド – Numbers never leave the browser; nothing is logged or sent to a server.

 よくある質問

Why does the same digit string need a different check digit for ISBN-10 vs ISBN-13?

ISBN-10 uses a modulo-11 algorithm with descending weights from 10 down to 2, while ISBN-13 uses the GS1 modulo-10 algorithm shared by EAN-13. The arithmetic, the weight pattern, and even the alphabet differ — ISBN-10 may end in X (representing 10), but ISBN-13 must end in a digit 0–9.
What does the alternating 3,1 weight pattern in EAN/UPC actually catch?

It detects all single-digit substitution errors, and most adjacent transposition errors. The asymmetry between 3 and 1 means swapping two neighbouring digits usually produces a different sum, which trips the check. Doubling-only schemes (like Luhn) catch transpositions only when neighbours differ by exactly 5.
Why is GTIN-14 the same algorithm as EAN-13 but a different length?

GTIN is the unifying 14-digit container in the GS1 framework. Shorter codes (EAN-13, UPC-A, EAN-8) are conceptually right-aligned inside a GTIN-14 with leading zeros. The algorithm has to be consistent so a system can store every variant in the same field and reuse the same validator.
Can a barcode pass the check digit and still be wrong?

Yes. The check digit only protects against transcription errors — typos, OCR misreads, smudged scans. It does not prove the code was issued or that the underlying GTIN belongs to a real product. For that you need GS1 lookup or a product database.