Which barcode formats does Apple Wallet support for passes?

Apple Wallet pass barcodes commonly use QR, Aztec, PDF417, and Code 128, depending on the issuer and use case. The exact pass file determines what is displayed, so the format should match the intended scanner workflow.

Why do tickets sometimes show multiple barcode formats?

Issuers may include different barcodes for compatibility, internal tracking, or links. Some encode the same data in multiple formats, while others are completely different and only one is meant for entry.

Is QR always better than Code 128 in Apple Wallet?

Not always. QR codes are common and robust, but the right choice depends on what the venue or store scanner expects. Matching the original issuer barcode data and purpose matters more than picking a format you prefer.

Can barcode format affect scan reliability?

Yes. Display size, contrast, source quality, and scanner hardware all matter, and some formats are less forgiving when rendered too small. A correctly chosen and correctly encoded barcode usually scans more reliably than a guessed conversion.

How do I choose the right barcode when I am unsure?

Look at the ticket context, check which code is intended for entry, and compare barcode types before converting. If a pass app shows multiple detections, review each option instead of selecting the first one automatically.

Apple Wallet Barcode Formats: QR, Aztec, PDF417, Code 128

Barcode format is one of the biggest reasons Apple Wallet passes scan reliably or fail at the gate. Two tickets can look similar on screen while using completely different barcode types with different scanner expectations.

This guide explains the four formats people most often see when importing passes to Apple Wallet: QR, Aztec, PDF417, and Code 128. It focuses on what they look like, where they are commonly used, and how to choose the correct barcode when a ticket contains more than one.

The Four Barcode Formats You Will See Most Often

Apple Wallet pass imports regularly involve these formats. Each has a different visual structure and is common in different industries.

QR Code

Square matrix code with corner markers. Common for event tickets, coupons, sign-in flows, and many modern digital passes.

Aztec

Square code with a bullseye-style center. Frequently seen in transit and some travel systems because it packs a lot of data into a compact symbol.

PDF417

Stacked linear code with multiple rows. Widely used on boarding passes and other high-data ticket formats.

Code 128

Linear barcode with varying bar widths. Common for membership cards, logistics labels, retail IDs, and many barcode-based check-in systems.

NeatPass supports many formats beyond these four, but this set covers most real-world pass imports. See the full list in supported barcodes.

Why Format Choice Matters in Apple Wallet

The barcode is not just a picture. It is encoded data plus a specific symbology, and scanners are often configured for the format the issuer expects. If a ticket originally relies on PDF417 and you accidentally use a different code from the same page, the gate scanner may reject it even though a barcode is visible.

The safest way in NeatPass is to preserve the intended barcode from the original source, then export a proper Wallet pass. Use adding to Wallet guidance as your final step and import methods when you start from PDFs, photos, or screenshots.

Detection helps, but review still matters

NeatPass can show multiple detected barcodes and overlays. Use live barcode detection to see what was found, then quickly confirm if a code looks different than what you expected before exporting the pass.

How to Think About Barcode Selection

Format choice becomes easier when you think about the scanner and the context, not just which barcode looks easiest to recognize.

Event tickets

Prioritize the barcode that is clearly labeled or positioned for entry. Tickets often include extra barcodes for order tracking or internal venue use.

Travel passes

Boarding and rail documents often use dense formats because they carry more encoded data. Use the travel barcode, not a separate app or web link QR if both are present.

Membership and loyalty cards

Linear formats like Code 128 are common for check-in and checkout. If the original card uses Code 128, preserve that barcode rather than replacing it with a different format.

Multiple barcodes on one page

Do not assume the largest code is always the right one. Compare labels, context, and duplicate-grouping tools when available.

Display constraints

Small or dense codes can become hard to scan when captured from a low-quality image. Source quality matters before format even enters the conversation.

Common mistakes

Choosing a marketing QR code, cropped barcode, or low-resolution screenshot is a more common failure than choosing the wrong app theme or pass color.

If NeatPass cannot detect the barcode cleanly, fix the source image first. Start with barcode detection troubleshooting before trying repeated conversions.

Convert the right barcode to Apple Wallet

NeatPass makes it easy to convert any ticket, pass, or loyalty card to Apple Wallet.

Try NeatPass Free

Step-by-Step: Let NeatPass Help You Pick the Right Barcode

Import the original ticket or card source

Start with the original PDF, screenshot, photo, or app capture in NeatPass. You do not need to identify the barcode format manually before importing.

Let NeatPass detect the visible barcodes

NeatPass scans the source and shows the barcode candidates it finds. This removes most of the guesswork, especially on tickets with multiple codes.

Pick the barcode used for entry or check-in

If multiple barcodes appear, choose the one that matches the real scanning use case. Ignore marketing or tracking codes, even if they look cleaner in the image.

Export a real Wallet pass

Confirm the selection and let NeatPass create a proper Wallet pass that preserves the barcode data, instead of relying on a screenshot or photo at the scanner.

Keep the original as backup until first successful scan

For your first use, keep the original ticket or card source available. Once you confirm the Wallet pass scans correctly, NeatPass becomes the faster everyday option.

Frequently Asked Questions

Import a barcode and export a real Wallet pass

Download

NeatPass Handles the Hard Part

NeatPass handles barcode detection and Wallet pass creation for most imports. Knowing what QR, Aztec, PDF417, and Code 128 look like simply helps you confirm the right code faster in edge cases with multiple barcodes.

Most scan failures happen before the Wallet step when the wrong barcode is used or the source image is poor. NeatPass makes that review easier, then exports a proper Wallet pass with the preserved barcode data.

Need the next step? Read which barcode to choose when your ticket has multiple, see the broader guide in convert any barcode type to Apple Wallet, and troubleshoot failures in Apple Wallet barcode won't scan.