How big is the iOS keyword field?

The App Store keyword field holds exactly 100 characters of comma-separated terms. It is hidden from users and used only for search matching, so packing it efficiently directly affects which searches your app can rank for.

Why remove words that are in my app title?

Apple already indexes every word in your app name and subtitle for search, so repeating them in the keyword field wastes precious bytes. This builder strips title words so the 100 characters go entirely to new terms.

Should I use spaces in the keyword field?

No. Apple ignores spaces after commas but they still consume characters, so the builder joins terms with commas and no spaces. It also splits phrases into single tokens because Apple matches across the comma list to form multi-word searches automatically.

Can I use competitor names as keywords?

You can include generic competitor app names, and many developers do, but avoid trademarked terms you have no right to and Apple may reject. The builder includes them as candidates so you can decide which to keep.

What happens to terms that don't fit?

Terms that overflow the 100-character limit are listed separately as lower-priority so you can swap them in for weaker keywords. Nothing is silently lost — you see exactly what fit and what didn't.

App Store Keyword Field Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Make every one of your 100 characters earn its place

The iOS keyword field is one of the highest-leverage ASO inputs and one of the most commonly wasted, because developers fill it with words Apple already indexes from the app name. This builder strips those out, removes duplicates and stop words, splits phrases into the single tokens Apple actually matches on, and greedily packs the highest-value terms into exactly 100 characters.

How it works

You enter your app title and subtitle, plus features, competitor names, and extra related terms. Apple already indexes title and subtitle words for search, so the builder excludes any single-word term that appears there. It also drops common stop words like the, app, and free, which Apple auto-indexes, and removes duplicates. Multi-word phrases are split into unique single tokens because the App Store recombines comma-separated keywords into multi-word searches on its own — so storing photo and editor separately also covers “photo editor”. Finally it fills the field greedily with commas and no spaces, since spaces consume bytes without helping matching, and shows you both what fit and what overflowed.

Tips and example

Don’t repeat your app name — if your title is PhotoFlow: Photo Editor, the builder will skip photo and editor automatically.
Prefer single specific tokens over long phrases; Apple builds the phrases for you across the comma list.
Put your most important terms first in the inputs — they get packed before lower-priority ones if space runs out.
Review the “did not fit” list each release and rotate terms based on which searches actually convert.