Which is denser—Code 128 or Code 39?

Code 128 is significantly denser for the same alphanumeric string because it encodes three characters per module group. Code 39 uses wider bars and inter-character gaps.

Does Code 39 support lowercase letters?

Standard Code 39 is uppercase alphanumeric plus a handful of symbols. Code 128 supports full ASCII in subset B, making it better for mixed-case IDs.

Which symbology do shipping labels use?

Carrier labels often use Code 128 or specialized 2D formats—not Code 39. Follow the carrier’s ZPL or PDF spec rather than assuming either symbology.

Can one scanner read both Code 128 and Code 39?

Most modern imager guns do. Verify symbology enablement in the scanner configuration; some ship with Code 39 disabled by default.

Do these symbologies include check digits?

Code 128 has an internal checksum. Code 39 optionally appends a modulo-43 check character—enable it only if your spec requires verification.

When should I switch from Code 39 to Code 128?

When label space is tight, data length grows, or you need lowercase characters. Plan a parallel scan test before bulk reprinting rack labels.

Code 128 vs Code 39 Compared

Code 128 and Code 39 are workhorse 1D symbologies for warehouse, manufacturing, and asset labels. Code 128 packs more characters into less width; Code 39 remains on legacy systems that expect its simpler alphabet and wider bars. Create samples in the Code 128 generator and Code 39 generator, then decode with Barcode Scan.

Why it matters

Logistics teams live or die by label density. A Code 128 shipment ID fits beside a carrier logo where Code 39 would overflow; yet hospitals and defense contractors sometimes mandate Code 39 because their decades-old SOPs and scanners were certified on that symbology. Picking the wrong one means either reconfiguring every handheld or reprinting thousands of rack labels.

Code 128 and Code 39 width comparison for the same data

How to apply it

Audit your WMS, MES, or ERP export templates for the symbology name—they often hard-code one format. For new deployments without legacy constraints, default to Code 128 for alphanumeric order numbers, lot codes, and SSCC-style IDs. Stay on Code 39 only when a trading partner or internal standard explicitly requires it. Pair this decision with barcode size guidelines so narrow bars remain scannable.

List maximum label width and required data length before choosing a symbology.
Enable checksum characters only if your spec demands them—Code 39 checksum is optional; Code 128 includes checksum modules internally.
Use subset B in Code 128 for typical ASCII payloads unless you are optimizing numeric-only strings.
Scan at the farthest expected distance on your warehouse aisles, not just at arm’s length.

Common mistakes

Migrating to Code 128 without updating scanner firmware leaves devices reading partial strings. Conversely, choosing Code 39 for 20-character IDs forces tiny X-dimensions that fail on thermal printers. Do not mix symbologies on the same label without confirming the reader supports multi-symbol scanning. Review barcode types if your payload outgrows either format.

Warehouse label showing logistics barcode placement

Recommended tools

Generate side-by-side proofs in Code 128 and Code 39, explore other logistics formats from the Barcode Generator, and validate with Barcode Scan.

Why it matters

How to apply it

Common mistakes

Recommended tools

Related

Frequently asked questions