Convert PNG to PKPASS

A PNG must become part of an Apple Wallet pass when a ticket, boarding pass, loyalty card, or coupon needs to be installed in Wallet instead of shared as an image. The PNG supplies artwork; the resulting PKPASS package supplies structured fields, barcode data, and a cryptographic signature.

What the PNG format is

PNG is a lossless raster-image format that supports transparency, indexed color, grayscale, and full-color RGB or RGBA images. Web designers, software developers, photographers, graphic editors, and users creating screenshots, logos, QR codes, and scanned artwork commonly use it. Applications including Adobe Photoshop, Affinity Photo, GIMP, and Preview can create or export PNG files.

A PNG contains pixels, not Wallet instructions. It does not normally contain the pass fields, barcode payload, update URL, Apple Wallet layout, or signing data required by PKPASS. A pass generator can use it as an icon, logo, strip, thumbnail, background, or other supported image asset.

What the PKPASS format is

PKPASS is Apple Wallet’s pass-package format. A file with the .pkpass extension is a ZIP archive containing files such as pass.json, image assets, manifest.json, and a cryptographic signature.

The pass.json file identifies the pass type, issuer, team, serial number, colors, fields, barcode, dates, and other Wallet behavior. manifest.json lists package files and their SHA-1 hashes; signature signs that manifest with an Apple Pass Type ID certificate. Wallet checks the signature before accepting the pass. This structure supports boarding passes, event tickets, coupons, store cards, and membership cards with machine-readable and updateable data.

How to create a PKPASS from a PNG

There is no valid one-click conversion of a standalone PNG. Create a Wallet pass and place the PNG inside it.

1. Prepare the artwork in an image editor. Export an RGB or RGBA PNG, remove unnecessary metadata, and follow the pass generator’s required dimensions and @2x or @3x asset naming rules. Keep important text and barcodes as pass fields or barcode data instead of drawing them into the image; embedded content cannot be updated, localized, or reliably scanned.
2. Collect the pass data: issuer name, pass type, serial number, display fields, barcode format and payload, relevant dates, colors, and any update information. A screenshot of a ticket does not automatically supply these values. If the PNG contains a barcode, decode it separately and verify the result.
3. For programmatic generation, create an Apple Developer Pass Type ID and obtain its certificate and private key. The identifier in pass.json must match the certificate. The signing process also requires the current Apple Worldwide Developer Relations intermediate certificate.
4. Use passkit-generator for a repeatable Node.js workflow on macOS, Windows, or Linux. Install it with npm install passkit-generator, provide pass.json, the PNG assets, the Pass Type ID certificate, private key, and Apple intermediate certificate, then export the generated .pkpass file. The library creates the manifest and signature, avoiding common manual ZIP and signing errors.
5. For a no-code or hosted workflow, a pass platform such as PassKit can accept artwork, collect pass fields and barcode data, sign passes with the configured Apple credentials, and distribute them through a download link or email. It is a pass-authoring service, not a PNG converter: the issuer still has to supply valid pass data and credentials. Review its data handling before uploading tickets, identity documents, or unreleased designs.
6. Open the finished file on an iPhone or iPad with Apple Wallet and test installation, barcode scanning, text contrast, image scaling, dates, and the oldest supported iOS version. Do not edit, recompress, or add files after signing; any package change invalidates the manifest signature.

Quality and compatibility limits

Apple Wallet does not accept a PNG renamed to .pkpass, a ZIP containing only an image, or an unsigned archive. A usable package needs a valid pass.json, correctly hashed files in manifest.json, a matching cryptographic signature, and a supported pass structure.

Image quality depends on the source resolution and the asset slot. Enlarging a small screenshot produces blur, while text rendered inside artwork may become unreadable on different displays. Use the image roles and dimensions documented by the chosen pass tool, and keep scannable barcode data in a native Wallet barcode when possible.

PKPASS is designed for Apple Wallet and is not the native pass format for Google Wallet or other Android wallets. For Android distribution, use the target platform’s pass format or a service that generates platform-specific versions. Wallet support, certificate requirements, pass fields, and barcode behavior can also change with Apple’s current PassKit specifications, so verify the generated file against the supported iOS versions before distribution.