Field Limits by Platform
Updated January 26, 2026
TL;DR: Reference for character limits, field counts, and typography across Apple and Google Wallet passes.
- Apple: SF Pro font, fixed field counts per pass type, text auto-truncates
- Google: Roboto font, flexible modules with recommended character limits
- Typography: Font family, size, and weight are system-controlled (not customizable)
- Primary fields: ~20-25 characters before truncation
- Back/detail fields: No practical limit (scrollable)
- Always test on actual devices — limits vary by screen size
Overview
This reference provides field limits and character constraints for Apple Wallet and Google Wallet passes. These limits are approximate — actual truncation depends on font size, device screen, and number of fields displayed.
Design principle: If text might truncate, the most important information must come first.
Apple Wallet Field Limits
Field Counts by Pass Type
| Pass Type | Header | Primary | Secondary | Auxiliary | Back |
|---|---|---|---|---|---|
| Coupon | 3 | 1 | 4* | 4* | Unlimited |
| Event Ticket | 3 | 1 | 4 | 4 | Unlimited |
| Access Control (Generic) | 3 | 1 | 4* | 4* | Unlimited |
| Loyalty | 3 | 1 | 4* | 4* | Unlimited |
*Coupon, Access Control (Generic), and Loyalty with square barcode: Combined maximum of 4 secondary + auxiliary fields.
Character Limits (Approximate)
| Field Type | Recommended Max | Notes |
|---|---|---|
| Header fields | 15-20 chars | Depends on number of fields |
| Primary field | 20-25 chars | Single line, auto-truncates |
| Secondary fields | 15-20 chars | Per field, depends on count |
| Auxiliary fields | 15-20 chars | Per field, depends on count |
| Field labels | 10-15 chars | Displayed above values |
| Back fields | No limit | Scrollable detail view |
Truncation Behavior
Apple Wallet automatically truncates text that exceeds available space: - No text wrapping on front of pass - Truncation indicated by ellipsis (...) - Number of visible characters varies by device width - More fields = less space per field
Best Practices
- Put critical information at the beginning of field values
- Use abbreviations where meaning remains clear
- Test with longest expected values
- Consider field count trade-offs (fewer fields = more space each)
Google Wallet Field Limits
Module Character Limits
| Module Type | Field | Character Limit | Truncation |
|---|---|---|---|
| Header | Title | ~25-30 chars | Auto-truncates |
| TextModuleData | header | 35 chars (recommended) | Soft limit |
| TextModuleData | body | 500 chars (recommended) | Soft limit |
| ValueAddedModuleData | header | 60 chars | Hard limit |
| ValueAddedModuleData | body | 50 chars | Hard limit |
| LinksModuleData | description | ~40 chars | Auto-truncates |
| InfoModuleData | label | ~15 chars | Auto-truncates |
| InfoModuleData | value | ~25 chars | Auto-truncates |
Module Counts
| Module Type | Class Limit | Object Limit |
|---|---|---|
| TextModuleData | 10 | 10 |
| LinksModuleData | 10 | 10 |
| ImageModuleData | 1 | 1 |
| InfoModuleData | Varies by pass type | Varies |
| ValueAddedModuleData | 10 | 10 |
Pass Type Specific Limits
| Field | Character Recommendation |
|---|---|
| Program name | 20-25 chars |
| Account name | 25-30 chars |
| Account ID | 20 chars |
| Rewards tier | 15-20 chars |
| Points balance | 10-15 chars |
| Field | Character Recommendation |
|---|---|
| Event name | 30-35 chars |
| Venue name | 25-30 chars |
| Date/time | 20 chars |
| Seat info | 15-20 chars per field |
| Field | Character Recommendation |
|---|---|
| Card title | 25-30 chars |
| Header | 20-25 chars |
| Subheader | 30-35 chars |
Truncation Behavior
Google Wallet handles text overflow differently: - Varies by device and Android version - OEM implementations may differ - Some fields support multi-line display - Critical content should fit without relying on expansion
Typography
Font style, size, and placement are controlled by Apple and Google — not by pass creators. This ensures a consistent, accessible experience across all wallet passes.
Apple Wallet Typography
| Aspect | Specification |
|---|---|
| Font family | SF Pro (San Francisco) |
| Display text (≥20pt) | SF Pro Display — tighter spacing, thinner strokes |
| Body text (<20pt) | SF Pro Text — looser spacing, heavier strokes |
| Weights available | 9 weights (Thin to Black) plus italics |
| Customizable | No — system-controlled |
| Language support | 150+ languages (Latin, Greek, Cyrillic) |
SF Pro automatically switches between Display and Text optical sizes based on the rendered point size. The operating system adjusts font rendering based on the user's accessibility settings.
Google Wallet Typography
| Aspect | Specification |
|---|---|
| Font family | Roboto |
| Weights available | Thin (100), Light (300), Regular (400), Medium (500), Bold (700), Black (900) |
| Customizable | No — system-controlled |
| Rendering | Varies by Android version and OEM implementation |
Google Wallet follows Material Design typography principles. Text rendering may differ across devices due to manufacturer customizations.
What You Can Control
| Element | Apple | |
|---|---|---|
| Text content | Yes | Yes |
| Text color | Yes | Yes |
| Font family | No | No |
| Font size | No | No |
| Font weight | No | No |
| Line height | No | No |
| Letter spacing | No | No |
Dynamic Text Behavior
Both platforms dynamically adjust text display based on:
- Device screen size — Larger screens show more characters before truncation
- User accessibility settings — System font size preferences affect rendering
- Field count — More fields means less space per field
- Content length — Back fields may reduce font size to fit content
There is no precise character count you can rely on. Design for the shortest common denominator and test on multiple devices.
Cross-Platform Comparison
| Aspect | Apple Wallet | Google Wallet |
|---|---|---|
| Font family | SF Pro | Roboto |
| Field structure | Fixed regions | Flexible modules |
| Primary content | ~20-25 chars | ~25-30 chars |
| Truncation | Consistent across iOS | Varies by device/OEM |
| Back/details | Scrollable, no limit | Expandable sections |
| Label display | Above value | Configurable |
| Multi-line support | No (front) | Yes (some fields) |
Field Content Guidelines
What Works
| Content Type | Good Example | Avoid |
|---|---|---|
| Names | "J. Smith" | "Jonathan Alexander Smith III" |
| Dates | "Mar 26, 2026" | "March 26th, 2026" |
| Times | "7:30 PM" | "7:30 PM EST (Doors 6:30)" |
| Points | "2,500 pts" | "2,500 loyalty points balance" |
| Status | "ACTIVE" | "Currently Active Status" |
| Locations | "Gate B12" | "Terminal B, Gate 12, Level 2" |
Abbreviation Patterns
| Full Text | Abbreviation |
|---|---|
| Membership | Mbr or Member |
| Points | pts |
| Balance | Bal |
| Available | Avail |
| Expires | Exp |
| Section | Sec |
| Row | Row |
| Seat | Seat |
Testing Recommendations
Test Cases
- Minimum content — Single character values
- Maximum content — Longest expected values
- Edge cases — Special characters, emojis, numbers
- Multiple devices — Different screen sizes
- Both platforms — Same content, different rendering
Device Testing Matrix
| Device Type | Screen Width | Character Impact |
|---|---|---|
| iPhone SE | 320pt | Most constrained |
| iPhone 14 | 390pt | Standard |
| iPhone 14 Pro Max | 430pt | Most space |
| Android (small) | ~360dp | Constrained |
| Android (standard) | ~400dp | Standard |
| Android (large) | ~440dp | Most space |
Common Mistakes
Designing for ideal content length — Real user data will exceed your mockup values.
Ignoring field count trade-offs — More fields means less space for each.
Testing only on one device — Truncation varies significantly by screen size.
Putting key info at end of text — Truncated text hides the most important part.
Assuming Google renders like Apple — Layout behavior differs substantially.
Sources
More articles in Technical Reference
This reference provides exact image specifications for Apple Wallet and Google Wallet passes. Use...
Color SpecificationsThis reference covers color configuration for Apple Wallet and Google Wallet passes. The platform...
Barcode And Nfc ReferenceThis reference covers barcode formats and NFC specifications for wallet passes. Both platforms su...