Guides
Cards on the phone

Apple Wallet pass sizes, in one table

Apple does not publish a single table with everything, and the sizes change with the pass type. These are the ones for a loyalty card (storeCard), which is what a bar or a café uses.

Updated 10 August 2026 · we keep it up to date because we use it ourselves.

Apple spreads these sizes across several pages and changes them depending on the pass type, so almost everything you find out there mixes up the sizes for a concert ticket with those for a stamp card. This table is the one for a loyalty card (storeCard), and it comes with the small print that hardly anyone mentions: there are two strip sizes doing the rounds, and both can be defended.

The size table

ImageFileIn points2x (px)3x (px)Required?
Icon icon.png 38 × 3876 × 76114 × 114 Yes
Logo logo.png 50–160 wide × 50 highup to 320 × 100up to 480 × 150 No, but really yes
Strip strip.png 375 × 144750 × 2881125 × 432 No

The logo sizes are a maximum, not a canvas: the image is fitted inside that box keeping its proportions. A square logo will end up taking 50 × 50 of the 160 available in width, and that's fine — what you can't do is stretch it.

And a loyalty card does not use the other three images you'll see mentioned elsewhere: thumbnail.png is for event tickets and generic passes, background.png for event tickets and footer.png for boarding passes. If you come across them in a tutorial, that tutorial isn't talking about your case.

Careful with the strip: you'll find two sizes, and both are "Apple's". The archived PassKit documentation split the strip into three heights —98 pt for event tickets, 144 pt for gift cards and coupons and 123 pt "in all other cases"— and that's where the 375 × 123 found all over the internet comes from. The current design guidelines list the strip at 375 × 144 for coupons and loyalty cards. Since a storeCard is precisely the gift/loyalty card, 144 is the one that applies — and it's the one we recommend.

What to do with this in practice: design at 1125 × 432 and keep the important content in the middle band. If the system crops, it crops top and bottom, where you have nothing. The other way round —designing at the shorter size and having it stretched— always shows.

A note in the interest of transparency: this system currently generates its strips at 1125 × 369 (the shorter height), and on a real iPhone they look with no bands, no stretching and no cropping. So if you came looking for which of the two "works": both do. The practical difference lies elsewhere — with the taller height the stamps come out 17% bigger and fill the space better. It's an improvement, not a fix.

How to settle it for your own pass in two minutes. Open one of your passes and look only at the stamp band. If the circles come out oval, it's being stretched. If the ones at the ends look eaten into at the sides, it's being cropped. And if you see a band above and below, you have too much height. Careful with that last one: if the background of your strip is the same colour as the pass's, the band is there but you can't see it — the only giveaway is that the stamps look small for the space they have.

The strip, which is the one that really matters

The strip is the wide band that runs across the pass below the header. On a loyalty card it is the whole face of the product: it's where the stamp slots, the rewards and the photo of your shop are drawn. If you're only going to take care of one image, make it this one.

The aspect ratio is around 2.6 : 1 (a very wide band). Two practical consequences:

  • A portrait photo won't work. It will be cropped top and bottom. Choose landscape photos, with the subject in the centre.
  • Don't put small text inside the strip. At 144 points high, any sentence is hard to read. Text goes in the pass fields, which are real text and adapt to the language of the phone.

The strip changes depending on what happens

The strip doesn't have to be a fixed image. On a stamp card it's normal to have one image for each state: 0 stamps, 1 stamp, 2 stamps… With a 10-stamp card that's eleven images. That's where the real work of building this by hand lies, and it's exactly what a system like this one does on its own: generating all eleven, for every tier, for every business.

Logo and icon are not the same thing (and the icon is seen more)

It's the most common mistake: uploading the same image to both places.

IconLogo
Where it's seenIn notifications and in the list of passesTop left of the pass
ShapeSquare, cropped with rounded cornersLandscape, fitted to the box
What to putYour brand's symbol, no textYour full logo
If you get it wrongA long logo inside a square becomes unreadable in the notificationA square symbol looks tiny at the top
And if you're coming from an old tutorial: the icon has grown. For years the minimum was 29 pt (29/58/87 px), and half the internet still says so. Since iOS 15 notifications show the icon larger and Apple raised the minimum to 38 pt. At the old size the icon looks blurry exactly where people look most: in the notification your customer receives. We had it at 29 ourselves and raised it when we found out while writing this guide.
The icon is mandatory. Without icon.png, the pass won't be added to Wallet. And since it's the one shown in notifications, it's the image of your business your customer will see most often.

Format, and the mistakes that break the pass

  • PNG. Every scale, always PNG. Apple's current guidelines ask for 2x and 3x; 1x is no longer needed for modern screens.
  • Beware of disguised WebP. Many programs export a file named .png that is actually WebP inside. Wallet won't open it and the pass fails without saying why. If a pass "won't add" and you can't find the reason, start here.
  • Transparency in the icon and logo: yes, and it's a good idea, because you set the pass background with a colour. In the strip, no: anything left transparent will show the background colour and usually looks odd.
  • File size. There's no magic number, but the whole .pkpass travels to the phone every time it's updated. A 2 MB strip times eleven states makes a slow pass.

The text fields

The pass text doesn't go inside the images: they're fields, which is why they can be read by a screen reader, changed from the server and shown in the phone's language.

RowHow many fitWhat it's for
Header1The detail you see with the pass closed. On a stamp card: "7/10".
Primary1The most important thing. On a storeCard it usually ends up behind the strip.
Secondary and auxiliary4 between themMember name, tier, next reward. Not 4 of each: 4 in total, in a single row.
BackManyTerms, address, phone, unsubscribe. Only people looking for something go there.

Rule of thumb: three details on the front and not one more. Who they are, how far along they are and what they'll get. Everything else goes on the back.

And watch out for long text: if it doesn't fit, Wallet shows no error at all — it simply doesn't display it. A field that looks complete in your test can vanish on a customer's phone with the text in German.

Fields get translated; images don't. If you write "NEXT REWARD" inside the strip, a German customer will see it in English forever. If you set it as a field label, they see it in their own language.

Colours and contrast

The pass has three colours: background, text and labels. They're declared as a triplet rgb(23, 187, 82), CSS-style — hexadecimal isn't documented, so if your tool lets you enter #17bb52, you're outside what Apple describes. Two more warnings that save headaches:

  • Contrast matters more than it seems. Yellow on white looks gorgeous on your screen and can't be read in sunlight, which is exactly where your customer gets their phone out on a terrace.
  • The background colour and the strip have to get along. If the strip has a dark photo and the pass background is black, the pass looks like a hole. Tint them in the same colour family.

A detail almost nobody takes advantage of: the colour can change with the customer's tier. The same card in blue for someone just starting out and in black for someone who's been around for a year is the cheapest status signal there is — they carry it in their pocket and see it every day.

Frequently asked questions

What size is the strip image on an Apple Wallet pass?

You will find two answers: 375 × 123 pt and 375 × 144 pt. Apple's archived documentation gave 375 × 144 for gift cards and coupons and 375 × 123 for everything else; the current guidelines list 375 × 144 for coupons and loyalty cards. In pixels: 750 × 288 at 2x and 1125 × 432 at 3x for the taller size, and 750 × 246 / 1125 × 369 for the shorter one. If you design at the taller size and there is too much, it gets cropped top and bottom, which is the least visible failure.

Do I need to upload all three scales of the strip?

Apple's current guidelines only ask for 2x and 3x. The practical approach is to design a single image at 3x and produce the 2x one by scaling it down; 1x is no longer needed for modern screens.

What format should the pass images be?

PNG. The icon is mandatory: without icon.png the pass will not be added. And watch out for files named .png that are actually WebP inside: they have to be re-encoded as genuine PNG or the pass fails.

How many text fields fit on a loyalty pass?

On a storeCard: 1 header field, 1 primary field and up to 4 between secondary and auxiliary fields on the front. More fit on the back, but only people who go looking for them ever see them.

If you're also going to support Android —and you'll have to—, carry on with the loyalty card on Google Wallet, where the sizes and the way the card is built are different.

And if you’d rather not build any of this

etlas does everything on this page for you: it generates the images at the right size, builds the pass for Apple and Google, and updates it on your customer’s phone every time they get a stamp. You choose the colours and the rewards.