Why do my keywords say 45 of 100 when I typed 45 characters?

Apple documentation disagrees with itself here. The App Store search guidance says 100 characters, while the App Store Connect field reference says up to 100 bytes. A byte limit is the stricter of the two, and an accented character such as e with an acute mark costs two bytes, so this tool counts bytes and shows the character count beside it.

Can I add spaces in the keyword field?

Yes, inside phrases. What Apple asks you to avoid is a space right after each comma, because it wastes the byte budget on a separator nobody searches for.

Which fields need no approval?

All of them, but the App Store rejects anything over the limit on upload. Promotional text is the one you can edit later without submitting a new version.

Does this check keyword quality?

No, only length. Deciding whether a keyword is worth its bytes is a judgement call, not something a counter can make.

App Store Metadata Limits

Check app name, subtitle, and keyword fields against App Store limits.

Loading tool…

App Store Metadata Limits on Loonix helps you check your app name, subtitle, and keywords against App Store limits, counting keywords in bytes not characters.

How to use

Type the metadata exactly as you plan to submit it.
Watch the keywords field, which is counted in bytes.
Fix any field shown in red before uploading.

Features and limitations

Checks all six metadata fields at once with a usage bar for each.
Counts the keyword field in UTF-8 bytes, which is how the App Store counts it, so accents do not surprise you.
Explains the byte difference only when there is one, instead of on every keystroke.
Counts the keywords budget left as bytes, which is what you actually have to fit.

Limitation: Limits are the documented maximums, and the keyword field is measured in UTF-8 bytes to match how the App Store counts. There is no check that your keywords are good, only that they fit.

Use cases

Fit an app name and subtitle into the character limits before writing them into a build.
Work out how many keyword bytes remain when a name contains accents.
Catch a promotional text edit that pushes the field over its limit.

Frequently asked questions

Usage, result, and limitation information for this tool.

Why do my keywords say 45 of 100 when I typed 45 characters?: Apple documentation disagrees with itself here. The App Store search guidance says 100 characters, while the App Store Connect field reference says up to 100 bytes. A byte limit is the stricter of the two, and an accented character such as e with an acute mark costs two bytes, so this tool counts bytes and shows the character count beside it.
Can I add spaces in the keyword field?: Yes, inside phrases. What Apple asks you to avoid is a space right after each comma, because it wastes the byte budget on a separator nobody searches for.
Which fields need no approval?: All of them, but the App Store rejects anything over the limit on upload. Promotional text is the one you can edit later without submitting a new version.
Does this check keyword quality?: No, only length. Deciding whether a keyword is worth its bytes is a judgement call, not something a counter can make.