Info.plist purpose string checker
Paste your Info.plist, the output of plutil -p, or your INFOPLIST_KEY build settings. Every NS...UsageDescription key is checked against Apple's list, and every message against Apple's rules for purpose strings. What you paste stays in your browser.
Try an example:
What it does
It finds every permission key in what you paste, the ones whose names end in UsageDescription, and checks three things: that the key is one Apple lists for iPhone and iPad, that it isn't an old key Apple has replaced, and that its message follows Apple's rules. Each message is also shown the way it reads in the permission alert, after your app's name.
Apple's rules for a purpose string
Apple's page on requesting access lists what makes a purpose string valid:
- It isn't blank, and isn't only spaces.
- It is shorter than 4,000 bytes.
- It has the type the key needs, usually a string.
- It is accurate, meaningful and specific about why the app needs the access.
The Human Interface Guidelines add the style: a brief, complete sentence, in sentence case, with a period at the end, and no passive voice. App Review guideline 5.1.1 asks that purpose strings "clearly and completely" describe how you use the data.
Keys Apple has replaced
- NSCalendarsUsageDescription: use NSCalendarsFullAccessUsageDescription, or NSCalendarsWriteOnlyAccessUsageDescription to only add events.
- NSRemindersUsageDescription: use NSRemindersFullAccessUsageDescription.
- NSLocationAlwaysUsageDescription: use NSLocationAlwaysAndWhenInUseUsageDescription (iOS 11 and later).
- NSBluetoothPeripheralUsageDescription: use NSBluetoothAlwaysUsageDescription (iOS 13 and later).
- NSNearbyInteractionAllowOnceUsageDescription: use NSNearbyInteractionUsageDescription.
What it can't tell you
It reads the text, not your code. It can't see which protected APIs your app or its SDKs really call, so it can't tell you a key is missing. Apple notes that a library you include can need a purpose string even when your own code never uses that API. Whether a reason is true is also up to you.
Questions
What happens if my iPhone app has no purpose string for a permission it uses?
Apple says access to the resource fails and the app might crash. App Review also rejects apps that contain code using a protected resource without a purpose string.
How long can a purpose string be?
Apple says shorter than 4,000 bytes. A typical one is a single complete sentence, and the alert shows it right after your app's name.
Do I need NSLocationWhenInUseUsageDescription if I ask for location always?
Yes. Apple's documentation for asking for location at all times says the Info.plist must have both NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription.
How do I translate purpose strings?
Apple suggests a string catalog named InfoPlist.xcstrings. Build the app once and Xcode fills it with your usage description keys, ready to translate.
Is what I paste sent anywhere?
No. The checker runs in your browser and never sends your Info.plist to iPip or anyone else.
Sources
- Apple: Protected resources
- Apple: Requesting access to protected resources
- Apple: Human Interface Guidelines, Privacy
- Apple: App Review Guidelines 5.1.1
- Apple: requestAlwaysAuthorization()
Updated November 20, 2026.