How good is your Apple Wallet pass?
Drop in a .pkpass and get a score against wallet pass best practice in seconds: signature, live updates, scanning and tap, layout and images. It runs in your browser, so the pass never leaves your device.
Drop a .pkpass file here
Export it from your pass platform, save it from an email or link, or share it from Wallet on your iPhone. Apple Wallet passes only.
Analyzed in your browser. The pass never leaves your device.
More than fifty checks, from signature to lock screen.
Many pass platforms use only a fraction of what Apple Wallet can do. These checks come from issuing and running pass programs in production, and each finding says what we found in your pass and how Stell handles it.
Signing and setup
Whether Wallet will accept the pass at all: its basic details, a single layout, an icon, the kind of transport on a boarding pass, contents that match what was signed, and a valid signature from Apple's current certificate chain.
Live updates
Whether the pass can change after it is issued: a secure connection to an update service, a strong access key per pass, lock-screen messages that name the new value when the values customers watch change, and whether the pass has expired or been voided.
Scanning and tap
Whether staff and readers can identify the customer: a QR code or barcode in a format Wallet draws and an encoding scanners read, a backup for barcode types older iPhones cannot show, the number printed under the code, and NFC tap.
Design and layout
Whether the pass looks right on every iPhone: fields that fit the layout and all have values, dates that read naturally, a logo, sharp images at the right sizes, readable text contrast, the poster layouts of iOS 18 and iOS 27, event guide buttons and quick actions under the pass.
Content and relevance
A description VoiceOver can read, structured details that tell iPhone what the pass is about, sharing turned off, an end date for offers and tickets, terms and readable links on the back, complete translations, sign-up in Wallet, app links, and store locations or a relevant time so the pass reaches the lock screen when it is needed.
A barcode and NFC are both first-class ways to identify a pass holder, so a pass without NFC is never marked as broken; the analyzer suggests adding tap alongside the barcode where it fits the pass style. For what a pass that keeps itself current looks like, see updates and push, and for which terminals can read a tap, the reader directory.
About the pass analyzer.
- Is my pass uploaded anywhere?
- No. The analyzer reads the .pkpass in your browser, unzips it and runs every check on your device. The full report is free and needs no email. If you ask us about moving to Stell from the report, we receive your email, company and a one-line score summary, never the pass or its contents.
- Where do I get a .pkpass file?
- Most pass platforms can export one, and on a Mac you can save the pass from the email or link it was sent with. On iPhone, open the pass in Wallet and share it to your Mac or to Files, unless the issuer has turned sharing off for that pass.
- Does it verify the signature?
- It checks that every file matches what was signed, reads the certificates in the signature and confirms they belong to this pass, use Apple's current certificate chain and were valid when the pass was signed. Wallet performs the final verification when the pass is added.
- How is the score calculated?
- Each check is weighted by severity: critical problems that stop a pass from adding, verifying or ever being updated count most, then warnings, then suggestions. A pass with any critical problem scores 49 or lower, however much else it gets right.
Passes that score well and stay that way.
Stell signs, hosts and updates passes on Apple Wallet and Google Wallet, so signing, hosting and live updates are handled for every pass you issue.