What Compact Aztec Code is
Compact Aztec Code is a smaller-footprint variant of Aztec Code, limited to 1-4 data layers instead of the full format's up to 32. bwip-js delegates its own symbol drawing entirely to its Aztec Code encoder -- confirmed directly: bwipp_azteccodecompact forces the "format" option to "compact" (silently discarding any other value a caller supplies) and calls bwipp_azteccode().
Generate it now
Enter any text or data to see a live preview -- there is no fixed structure beyond Aztec Code's own general capacity rules.
Valid input
Any text or byte data is accepted, up to whatever a 4-layer compact symbol can hold at the chosen error-correction level (higher error correction reserves more of the symbol for redundancy, leaving less for data) -- confirmed empirically that raising error correction can exceed capacity for a payload that fits at a lower level ("Maximum length exceeded").
Key options
Supported options include eclevel and layers. Real, literal defaults (inherited directly from the azteccode delegate): eclevel 23 (percent of the symbol reserved for error correction, 5-95), layers -1 (auto-select the smallest layer count that fits). Because this capability always forces the format to "compact," an explicit layers value is constrained to 1-4 -- a value outside that range is rejected, even though the same value is valid for the separate, full-range Aztec Code generator.
Output and printing
Export SVG for vector-precise ticket/pass artwork or PNG for a quick proof.
Common uses
Aztec Code (both the full-range and this compact variant) is a real, ISO/IEC 24778-standardized 2D symbology widely used for airline boarding passes and event tickets, where a smaller physical footprint on a printed or mobile ticket matters.
Example
See the live preview above, seeded with a bwip-js-verified valid value.
Size guidance
Compact Aztec Code always uses a square, bullseye-centered finder pattern (unlike full-range Aztec Code's larger symbols, which use a different finder ring count) and supports only 1 to 4 data layers, capping its maximum data capacity well below the full-range format's own maximum.
Troubleshooting
A rejected value usually means the payload does not fit in a 4-layer compact symbol at the chosen error-correction level -- lower eclevel, shorten the payload, or use the separate full-range Aztec Code generator instead.
Related formats
Related formats: the separately-covered Aztec Code generator (full range, up to 32 layers) and Aztec Runes (a fixed 0-255 numeric-only micro-symbol) -- each a distinct real capability in this catalog, not a preset of this one.
FAQ
How is this different from the regular Aztec Code generator?
Both use the identical underlying Aztec Code encoder; this generator always forces the "compact" layout (1-4 layers, a fixed square finder pattern), while the separate Aztec Code generator lets bwip-js choose between full-range (up to 32 layers) and compact automatically, or fixes full range explicitly.
Why did my value get rejected even though it looks short?
Raising error correction (eclevel) reserves more of the fixed 4-layer capacity for redundancy, leaving less room for data -- a payload that fits at the default level can exceed capacity at a much higher one.