Home › Code 128 vs Code 39

Code 128 vs Code 39 — Technical Comparison & Decision Guide

Last updated: April 2026

Code 128 and Code 39 are both alphanumeric barcode formats used for internal applications — inventory labels, asset tags, shipping labels, and industrial identification — where no GS1 registration is required. The fundamental difference is density: Code 128 encodes the same data in roughly 30–40% less space than Code 39. For the majority of new implementations, Code 128 is the clear choice. Code 39 remains relevant only in specific industries and legacy environments that explicitly require it. This guide explains why, when each is appropriate, and how to decide for your specific application.

Direct Comparison Table

The Density Difference — Why It Matters

The gap between Code 128 and Code 39 barcode widths is significant enough to affect what labels you can use. To encode the string ITEM-BLK-LG-001 (15 characters):

• Code 128 — approximately 45–50mm wide at standard narrow bar width (0.25mm) with a minimum recommended bar height of 25mm. Fits comfortably on a standard 1" × 3" label with room for human-readable text and a logo.
• Code 39 — approximately 85–95mm wide at the same narrow bar width. Requires a wide-format label (roughly 4–5 inches) or the bar height must be significantly reduced, which can cause scanning failures.

This is not a marginal difference. On small labels — shelf bin tags, pharmaceutical packaging, jewellery price tags, electronics component bags — Code 39 often cannot encode the data that Code 128 handles easily. This density gap is the primary reason Code 128 replaced Code 39 as the default choice in logistics, retail warehouse operations, and new system implementations starting in the late 1990s.

Code 128 Sub-Types: A, B, and C

Code 128 has three sub-types that are often selected automatically by the generator:

Code 128A encodes uppercase letters, digits, and ASCII control characters (such as carriage return and tab). It is used in applications that require control character encoding, which is rare in most commercial contexts.

Code 128B encodes the full ASCII character set including lowercase letters. It is the most commonly used sub-type and the default in most implementations. When you generate a Code 128 barcode with mixed-case or lowercase characters, Code 128B is used.

Code 128C encodes digit pairs with exceptional density — each pair of two digits (00–99) is encoded in a single barcode symbol. This halves the barcode width for purely numeric data compared to Code 128B. It is used for FNSKU codes, numeric serial numbers, and other all-numeric data where space is at a premium. BatchPrintGTIN automatically selects Code 128C for numeric-only input where appropriate.

When Code 39 Is Still Required

Despite Code 128's advantages, Code 39 remains a mandatory requirement in several specific industries and standards:

Automotive Industry — AIAG Standards

The US automotive industry standardised on Code 39 through the Automotive Industry Action Group (AIAG) in the 1980s. Vehicle identification number (VIN) labels, supplier delivery tags, and many parts identification labels in the automotive supply chain specify Code 39 explicitly. Major automakers and Tier 1 suppliers often have decades-old receiving equipment that only reads Code 39. If you are a supplier to Ford, GM, Stellantis, Toyota, or any of their tier suppliers in North America, check the relevant AIAG standard (particularly B-10 for shipping labels) before choosing a format. Many automotive applications are now migrating to QR and Data Matrix codes for parts tracking, but Code 39 remains the fallback requirement in many facilities.

US Department of Defense

Various US DoD standards — including MIL-STD-1189 and many individual programme specifications — require Code 39 for asset labels. Although the DoD has updated many specifications to allow Code 128 and 2D codes (particularly for UID — Unique Identification — applications which use Data Matrix), legacy facilities and older receiving systems throughout the defence supply chain still require Code 39. If you are supplying to a US government contract, check the specific contract and programme requirements.

Legacy Healthcare Systems

Some hospital systems, blood banks, and laboratory information systems installed before the mid-2000s support Code 39 only. Clinical environments have long hardware replacement cycles, and a scanner installed in a surgical supply room in 2003 may still be in active service. If you are integrating barcodes with an existing clinical system, scan test labels on the actual equipment before committing to Code 128.

Government and Identity Applications

Some state and federal government applications — including certain driving licence and identification document formats and correctional facilities — use Code 39 in legacy systems. Newer government ID applications generally use PDF417 or Data Matrix.

GS1-128 — When You Need Structured Supply Chain Data

GS1-128 (formerly called EAN-128 or UCC-128) is a specific application of Code 128 that uses GS1 Application Identifiers (AIs) to encode multiple structured data elements in a single barcode. Application Identifiers are two-to-four-digit prefixes that tell the scanner what type of data follows — for example, AI (01) indicates a GTIN, AI (17) indicates an expiry date, AI (10) indicates a batch or lot number, and AI (21) indicates a serial number.

A single GS1-128 barcode on a pharmaceutical package might encode all of the following: the product GTIN, the lot number, the expiry date, and the serial number. A retail distribution centre label might encode a GTIN, a serial shipping container code, and a delivery date. This structured encoding is impossible in plain Code 128 or Code 39 — those formats simply encode a string of characters with no standardised meaning assigned to specific positions.

GS1-128 is required in some healthcare supply chains (particularly in hospital and pharmacy systems implementing GS1 Healthcare standards), some food and fresh produce supply chains (for lot and expiry tracking), and on retailer-specific distribution centre labels for chains such as Walmart, Costco, and many European grocery retailers. If a retailer's supplier requirements document specifies "GS1-128 with Application Identifiers," this is the format they mean.

Real-World Use Case Summary

Migrating from Code 39 to Code 128

If you are running a legacy internal system that uses Code 39 and want to switch to Code 128, the transition is straightforward as long as your scanners support Code 128 — which almost all scanners manufactured after 1995 do. The data encoded in the barcode does not change; you simply regenerate your labels with Code 128 instead of Code 39. The barcodes will be narrower (which may allow you to reduce label size or add more information), and scanning will be more reliable at longer read distances.

Before migrating, test a Code 128 barcode on every scanner in your operation, including mobile devices, fixed-mount scanners at receiving docks, and any integrated scanner in desktop software. If all scanners confirm successful reads, you can switch format on next print run without any data changes.

Frequently Asked Questions

Related Topics

• Code 128 Barcode Generator — All Character Sets and Options
• All Barcode Formats Compared — UPC, EAN, Code 128, QR & More
• Amazon FBA Barcode Guide — FNSKU Label Requirements
• Barcode Label Generator — Label Dimensions for Code 128
• Bulk Barcode Generator — Generate Code 128 from CSV
• Barcode Examples — Scannable Samples of All Formats