How to Use Create a Pass in Apple Wallet on iOS 27
iOS 27 adds something Wallet has never had in fourteen years: the ability to build your own pass. Tap the "+" button you use to add credit cards or pass emails, and a new "Create a Pass" option appears alongside the existing options. It lets you digitize a paper ticket, membership card, or loyalty pass directly from your iPhone, with no developer account, no Pass Type ID, and no certificate signing required (Michael Tsai, May 2026). This guide walks you through how to use Create a Pass in Apple Wallet on iOS 27, then gives you a clear framework for deciding when the result is safe to rely on.
The feature is genuinely useful. But Apple has spent years building official Wallet passes that update automatically, track flights, trigger Live Activities, and surface on your lock screen at the right moment. A pass you create yourself bypasses all of that infrastructure, and knowing where the ceiling is before you show up at a venue is worth a few minutes of reading.
What you'll need: An iPhone running iOS 27. A physical ticket, membership card, or other pass with a barcode or QR code to digitize, or the information you want to enter manually.
What Create a Pass actually does
The feature offers two paths: scan with Visual Intelligence or build manually.
In the scan flow, you point your camera at a physical pass. Visual Intelligence reads the barcode or QR code and attempts to pre-fill text fields, pulling name, location, and admission type from whatever printed text is legible (MacRumors, June 2026). The barcode is captured and re-encoded as the scannable element on the digital pass. In the manual flow, you start with a blank editor and enter everything yourself. If the pass has a barcode you want to include, you photograph just the code and Wallet embeds it.
Either path lands in the same pass editor. Three templates are available: Standard, Membership, and Event. The field library is wider than those templates suggest. You can add or remove label, date, membership, contact, coupon code, VIN, insurance fields, and more, so most physical card formats can be accommodated (MacRumors, June 2026). Appearance options include 12 solid background colors or seven category-specific backgrounds for theater, music, sports, and movies. These are cosmetic choices with no effect on how the barcode scans.
iOS 27 also expands Wallet's supported barcode formats to include EAN-13, Code 39, Codabar, and ITF (Interleaved 2 of 5), which broadens the range of physical passes that can be accurately captured (Apple Developer WWDC26, June 2026). One caveat worth knowing: if a pass contains only one of these new formats and ends up on an older device, it will not render a barcode on iOS 26 and earlier. This matters if you ever restore to an older OS.
What Apple has confirmed: scan and manual creation, three template types, editable fields, 12 background colors, seven category images, and support for the four new barcode formats.
What Apple has not publicly documented: whether user-created passes sync across devices, appear on Apple Watch, surface via location-based relevance, or support any form of update after creation. Treat a user-created pass as a local, on-device artifact until Apple clarifies those details.
How to use Create a Pass in Apple Wallet on iOS 27: step by step
Step 1: Open Wallet and tap the "+" button. The "Create a Pass" option appears alongside the existing card and pass options. This is the only entry point; there is no shortcut from the camera app or Photos.
Step 2: Choose the scan or manual path. For any physical pass with a barcode or QR code, choose the scan option. Go manual only if the pass has no scannable code, the scan produces unreliable results on a worn or faded original, or you are building entirely from scratch.
Step 3a (Scan path): Point your camera at the physical pass. Hold it steady until Visual Intelligence captures the barcode and attempts to fill text fields from the printed information. Check every auto-filled value against the original before moving on. Worn, faded, or low-contrast tickets may pre-fill poorly or miss the barcode entirely. This is the fastest path, but also the one most likely to need corrections.
Step 3b (Manual path): Build from the blank editor. If you are including a barcode, photograph it when prompted. Enter all other fields by hand. The manual path is slower but gives you complete control over what appears on the pass.
Step 4: Select a template type. Choose Standard, Membership, or Event. Pick whichever matches the pass you are digitizing. The template sets which fields appear by default, though you can add or remove any field in the next step.
Step 5: Add, remove, and edit fields. Strip out fields that do not apply. A pass showing only the information that matters is easier to present at the door. Verify every value against the physical original. Errors left uncorrected here will surface at exactly the wrong moment. For most gym memberships, the name and barcode are sufficient. For event tickets, you may want to add the date, venue, and admission type so staff can confirm the basics at a glance before scanning.
Step 6: Set the appearance and save. Choose a background color or category image, then save. The pass appears in your Wallet stack and is ready to present.
Before your first use: Bring the physical original the first time you present the digital pass at a venue. Not because the process is unreliable, but because it is the first real-world test, and a backup costs nothing. After a confirmed successful scan at that venue, you can leave the paper at home.
When Create a Pass works well
Static passes where a venue needs to read a barcode and nothing more are the sweet spot. The feature is specifically designed for cases where no official digital version already exists in Wallet (MacRumors, June 2026).
Good candidates include:
- Gym memberships and fitness club cards with a fixed member barcode that does not rotate
- Library cards, where the scannable code is stable and entry systems are typically forgiving of format variations
- Loyalty punch cards from local businesses, coffee shops, or retailers with no official app integration
- Paper tickets for small local events where the venue uses a basic barcode scanner and there is no official Wallet pass offered by the organizer
- Membership cards for clubs or organizations that issue physical cards but have no digital equivalent
The editable field library is broad enough to handle most of these formats. A library card needs a member number and perhaps a name. A gym pass might include an expiry date. A loyalty card may only need the barcode itself. The template system accommodates all of it.
One thing to keep in mind: the scan path works best on clean, high-contrast originals. A freshly printed ticket from a home printer or a new plastic membership card will scan accurately. A faded paper stub that has been through a washing machine probably will not. Use the manual path for anything that has seen wear, and photograph the barcode separately when prompted.
When not to rely on it
Three questions cover most cases.
Does the pass ever need to update? Official boarding passes integrate with Apple's flight service and stay current automatically. Gate changes, delays, and status updates propagate to both the pass and a Live Activity without any action required from the traveler (Apple Developer WWDC25, June 2025). A user-created pass is frozen at the moment you make it. If the issuer rotates barcodes, invalidates a code after one scan, or changes your seat assignment, your digital copy will not reflect it. For anything dynamic or time-sensitive, use the official pass.
Does the venue use NFC for entry? Contactless NFC entry requires a pass signed with an NFC entitlement, a step that official pass issuers complete as part of their developer integration (Apple Developer WWDC24, June 2024). User-created passes skip that signing entirely, so they cannot work with tap-to-read scanners. Optical barcode scanning is the only entry mode available here. If you are heading to a large arena or a major stadium where attendants wave a reader at your phone without you opening anything, check whether your venue uses NFC before relying on a user-created pass.
How bad is a failed scan? The Create a Pass flow runs without a developer account or certificate signing (Michael Tsai, May 2026). That accessibility is also its limit. Whether scanners at every venue reliably accept a Wallet-rendered reproduction of a paper barcode has not been established through documented real-world testing at scale. For a local gym, a failed scan is a minor inconvenience. The staff member looks up your account by name. For a sold-out concert three hours from home, keep the paper ticket in your pocket.
The practical decision rule: Use Create a Pass for static, low-risk passes where all the venue needs is a readable barcode and nothing needs to update afterward. Avoid it for anything with dynamic barcodes, NFC entry, or an official Wallet integration already in place. When an official digital pass is available from the issuer, use that instead. The automatic updates, Live Activities, and Apple Watch support that official passes carry are built on infrastructure Create a Pass deliberately does not replicate.
What this feature actually changes
For fourteen years since PassKit shipped with iOS 6 in 2012, users without an official Wallet integration were stuck photographing barcodes into a Photos album or hunting for third-party workarounds (Michael Tsai, May 2026). Scan a physical pass, pick a template, trim the fields, and a gym membership or local theater ticket lives in Wallet in under two minutes. That gap is now closed.
The trust question has a plain answer: a user-created pass is as reliable as the barcode it contains, and as static as the moment you created it. For scan-at-the-door passes at low-stakes venues, that is enough. For anything that updates, uses NFC, or already has an official integration, that infrastructure exists for good reasons. Use it.
After your first confirmed scan at a venue, you will know the setup works. Leave the paper at home.
Comments
Be the first, drop a comment!