What Is a .pkpass File? Apple Wallet Passes Explained

Every card, ticket, and coupon in Apple Wallet is a .pkpass file. If you're planning a wallet program, understanding the format explains both what's possible and what your platform should be doing for you.

Inside a .pkpass

A .pkpass is a ZIP archive with a strict structure: a pass.json describing the layout, fields, colors, and barcode; image assets (logo, icon, strip); localizations; a manifest listing a checksum for every file; and a cryptographic signature created with a certificate issued by Apple to the pass creator. If any byte changes without re-signing, the pass is invalid — that signature is why wallet passes are trustworthy at the door.

Pass types and layouts

Apple defines five styles — generic, store card, coupon, event ticket, and boarding pass — each with fixed field positions: header, primary, secondary, auxiliary, and back fields. Design within the system and passes feel native; fight it and they look broken. (Google Wallet uses a different but analogous model — see our Apple vs Google comparison.)

How updates reach the phone

A pass carries a web service URL and an authentication token. When the source data changes, the issuing server tells Apple's push service, the device fetches the updated .pkpass, and the card refreshes silently — that's how a membership tier or event gate changes on thousands of phones in seconds.

Do you need a .pkpass generator?

Only if you enjoy managing certificates, signing pipelines, and push registrations. Kemicard generates, signs, and updates .pkpass files (and their Google Wallet equivalents) automatically from Salesforce records: you design the template with clicks, map fields, and the platform handles the format. Read how in the technical architecture, or try it on the AppExchange Test Drive.