Aztec Code

Aztec Code is a two-dimensional matrix symbology standardized as ISO/IEC 24778:2008.¹ Unlike linear barcodes, it stores information in a square field of dark and light modules, so a small symbol can carry substantially more data than a one-dimensional product code. The design was created in 1995 by Andrew Longacre Jr. and Robert Hussey at Welch Allyn; their patent describes the central locator, layered data regions, and error-correction approach.² The name refers to the central bullseye's visual resemblance to imagery associated with Aztec architecture, not to the historical Aztec civilization or its writing systems. The standard is a symbology specification: software and equipment may implement it independently while preserving the same encoded structure.

The central bullseye is the key structural feature because it lets a scanner find the symbol, determine its orientation, and estimate module size. Around it are orientation marks, a mode message describing the symbol's layout, and one or more square layers containing data and error-correction codewords.¹ A compact symbol has one to four layers and omits some outer reference features; a full symbol has one to 32 layers and can grow from 19 by 19 to 151 by 151 modules. Data is divided into character tables so a symbol can switch efficiently among uppercase, lowercase, mixed punctuation, digits, and binary bytes. Reed–Solomon coding adds recoverable redundancy, with the encoder able to trade payload capacity for greater resistance to damage.³

Aztec Code is particularly useful for tickets and documents whose printed area is limited, including transport tickets, boarding credentials, postage, and electronic vouchers. It can encode a relatively large payload in a compact square and does not require a blank margin around the symbol, although a clear surrounding area can still improve practical scanning. Its finder pattern supports reading from varied orientations, while error correction helps with creases, stains, low-contrast printing, and partial obstruction. These properties make it attractive for paper-based and screen-based credentials, where the symbol may be printed on a receipt or displayed on a mobile phone. Implementations such as the open-source ZXing library demonstrate that decoding can be performed by general-purpose camera software as well as dedicated barcode scanners.⁴

Aztec Code's compact form is not merely a smaller version of a full symbol: it uses a different finder arrangement to reduce overhead at very small sizes.¹ The symbol can carry raw binary data as well as human-readable character strings, which makes its practical content broader than names or numbers. Its error correction is configurable rather than fixed; increasing redundancy improves recovery from damage but leaves fewer modules for the message. This trade-off means that the same payload may legitimately be represented by symbols of different sizes. Aztec Code is also distinct from Data Matrix, QR Code, and PDF417: all are standardized two-dimensional formats, but their finder patterns, data layouts, capacity rules, and application ecosystems differ. Reliable decoding still depends on print quality, contrast, focus, and an implementation that follows the standard.

module

A single square element of a matrix barcode, rendered as dark or light.

bullseye

The concentric central finder pattern used to locate and orient an Aztec Code symbol.

layer

A square ring of modules surrounding the bullseye and carrying encoded information or control data.

Reed–Solomon error correction

An algebraic method that adds redundancy so missing or altered codewords can be reconstructed.

quiet zone

A blank margin around a barcode; Aztec Code is designed not to require one for symbol definition.