The app store subtitle character limit is 30 characters. That is not a lot.
But most indie iOS developers are not hitting 30. They write subtitles like “The Smartest Finance App” (25 characters, zero target keywords) or “Minimalist Habits” (17 characters, lots of unused capacity) or leave the field blank entirely.
The 30-character constraint is actually the point. It forces every character to earn its place.
Why the subtitle matters for ASO
Apple indexes your app’s subtitle for keyword search. It carries more indexing weight than the standalone keyword field, and it appears directly under your app name in search results. Users read it before they tap your listing.
That means the subtitle does two jobs at once: it tells Apple what keywords to rank you for, and it tells users at a glance whether this result matches their intent.
A subtitle that handles both jobs earns impressions and clicks. A subtitle that ignores search intent only handles one.
The 30-character limit, explained
The field in App Store Connect accepts up to 30 characters including spaces. Punctuation counts. Capital letters count. Nothing in the field is free.
A few practical rules that follow from the limit:
Commas waste two characters. Most developers write subtitles like “Budget Tracker, Expense Log.” The comma plus space between phrases uses two characters out of 30. Two words joined by a space, like “Budget Tracker Expense Log,” delivers the same keyword value at lower character cost.
The subtitle does not need to be a sentence. “Track spending without the spreadsheet” reads naturally but spends seven characters on “without the” that contribute nothing to indexing. “Expense tracker no spreadsheet” is tighter, and the savings can be reinvested in an additional keyword.
Do not repeat keywords from your title. Apple deduplicates across your metadata fields. If your app is called “Notion Daily: Task Manager,” putting “task” or “manager” in the subtitle does not add indexing value. It wastes characters. Use the subtitle to introduce keywords that are not already in your title or keyword field.
Avoid branding in the subtitle. “By Acme Studios” uses 14 characters that Apple treats as noise for indexing. Users find that information on the product page. The subtitle is not the place for it.
What good looks like: examples
Subtitle quality is easier to evaluate against alternatives. Here are before-and-after comparisons across different app categories with character counts shown:
| App type | Weak subtitle | Strong subtitle |
|---|---|---|
| Habit tracker | Habit Tracker App (18) | Daily habits streak tracker (27) |
| Budget app | Manage Your Money (18) | Spend tracker no subscriptions (30) |
| Focus timer | Stay Focused (13) | Focus timer Pomodoro sessions (29) |
| Recipe app | Your Recipe Box (16) | Recipe saver meal planner (26) |
The strong examples are not keyword-stuffed. They read naturally enough that a user scanning search results understands what the app does. And they use enough characters to get close to the limit with terms that users actually type.
Notice that “Spend tracker no subscriptions” works on two levels: it includes a keyword phrase (“spend tracker”) and it answers a specific objection (“no subscriptions”) that users in the budget app category often have. That conversion signal costs no extra characters compared to a generic tagline.
How characters map to indexing value
Not all 30 characters are equal. Apple’s indexing treats your title and subtitle as higher-priority fields than the keyword field, which is why every unused subtitle character represents more lost indexing value than an unused character in the keyword field.
A useful mental model: the subtitle is roughly two to three search keyword phrases. At 30 characters with spaces, you can typically fit a primary two-word phrase plus a secondary phrase before hitting the limit. The goal is to make both phrases specific enough to rank for realistic terms while maintaining enough coherence that users understand the listing.
One structural decision worth making intentionally: lead with the higher-priority keyword phrase. Apple appears to give slightly more weight to terms that appear earlier in the field. If you are trying to rank for both “habit tracker” and “daily streak,” put the higher-priority term first.
App Store subtitle examples: good vs bad, by category
Concrete examples to make the abstract rules tangible. Each pair shows what not to do alongside what would actually earn rankings — for the same hypothetical app.
Fitness tracker app. Title: FitTracker — Workout & Gym Log (30/30)
- ❌ Bad subtitle:
Track your workouts at the gym(29/30) — every meaningful word (workouts, gym) duplicates the title. Zero net-new keyword indexed. - ✅ Good subtitle:
Cardio, HIIT & Strength Plans(29/30) — four net-new high-volume keyword tokens.
To-do list app. Title: Plana — Daily Task Planner (25/30)
- ❌ Bad subtitle:
The best task planner app(24/30) — task and planner are duplicates. Best and app are wasted. - ✅ Good subtitle:
To-Do Lists, Reminders & Habits(30/30) — five net-new keywords mapped to real search demand.
Calorie tracking app. Title: KalBuddy — Calorie Counter (25/30)
- ❌ Bad subtitle:
Track your calories with KalBuddy(32/30 — over limit) — over budget, brand name duplicated. - ✅ Good subtitle:
Macro & Nutrition Diary(23/30) — three net-new high-intent keywords, room to spare.
Meditation app. Title: ZenMin — Meditation Timer (24/30)
- ❌ Bad subtitle:
A meditation app for everyone(28/30) — meditation duplicates the title; app and everyone are wasted. - ✅ Good subtitle:
Sleep, Breathwork & Mindfulness(30/30) — four net-new high-search-volume terms in the same wellness category.
Photo editor app. Title: Lumen — Photo Editor (20/30)
- ❌ Bad subtitle:
Edit photos easily on iPhone(29/30) — edit, photos, and iPhone either duplicate or waste. - ✅ Good subtitle:
Filters, Presets & RAW Tools(28/30) — four high-intent search terms.
The pattern is consistent across categories: the bad subtitles describe the app to the developer (literally what it does, restated). The good subtitles cover terms the title cannot reach.
Auditing your current subtitle
Open App Store Connect metadata for your most recent version. Count the characters in your subtitle. Then ask three questions:
- Is this close to 30 characters? Below 22 means you have unused indexing capacity that a competitor might be filling.
- Do any of these words also appear in your app title? Remove them and replace with new terms.
- Would a user searching for this app type these specific words? If not, find the words they would use.
The answers tell you where the characters went and what to do with them.
One thing to verify after any subtitle change: wait 21 days for Apple’s indexing cycle to complete before evaluating ranking movement. The subtitle takes the same time to take effect as any other metadata field. Changes that appear immediately in App Store Connect do not mean rankings have updated yet.
Where to go from here
The subtitle is the easiest high-leverage metadata change an indie developer can make. It does not require design work or engineering. It requires 20 minutes of deliberate thought about what users search for and how to apply 30 characters against that intent.
A subtitle audit can move keyword rankings within the next index cycle. That is a fast return for a narrow time investment.
Marteso surfaces keyword rankings for every term in your title, subtitle, and keyword field so you can see which characters are earning impressions versus which are dead weight. Start at app.marteso.com.