Tick the permissions your app uses and get the Info.plist keys with their usage descriptions, plus the InfoPlist.strings files to localise them in English and Spanish.
Result
Tick at least one permission to generate the code.
Info.plist (source code)
es.lproj/InfoPlist.strings
en.lproj/InfoPlist.strings
🔒 Everything is generated in your browser. No data is sent to any server.
How to use it
- Type your app’s name and choose the base language of your Info.plist.
- Tick each permission and describe what you actually use it for. The examples are only a starting point.
- Copy the XML into your Info.plist (right-click it in Xcode → Open As → Source Code).
- If your app is localised, add the generated text to each
InfoPlist.stringsfile.
Writing descriptions Apple accepts
- Say what the user gets: «uses the camera to scan QR codes», not «needs camera access».
- One permission, one concrete reason. Vague texts are a common cause of App Review rejections under guideline 5.1.1.
- If you access a protected resource without its key, the app crashes the moment it asks for permission.
Frequently asked questions
Which calendar key do I need on iOS 17?
Use NSCalendarsFullAccessUsageDescription to read events, or NSCalendarsWriteOnlyAccessUsageDescription if you only add them.
Do I need NSUserTrackingUsageDescription?
Only if you show the App Tracking Transparency prompt, for example to use the advertising identifier.
Is anything sent to a server?
No. The code is generated in your browser.
¿Prefieres español? Esta herramienta en español.