About this tool
A .mobileprovision file looks opaque, but inside the binary wrapper sits a plain XML plist describing exactly what the profile allows: which app ID it covers, which team issued it, which certificates and devices it includes, and when it expires. Provisioning Profile Parser digs that plist out for you. Drop a .mobileprovision file onto the page — or paste its base64 — and the tool scans the bytes for the embedded XML document, extracts it and parses it locally in your browser. You get a readable summary: the profile Name, AppIDName and TeamName, the creation and expiration dates with a live countdown telling you how many days remain before your builds stop installing, the full entitlements dictionary (push environment, app groups, associated domains and friends), the number of embedded developer certificates, the count of provisioned devices and whether it is an enterprise ProvisionsAllDevices profile. The extracted XML is shown pretty-printed so you can copy individual values straight into a bug report or CI check. Everything runs client-side, which matters here: profiles contain team identifiers and device UDIDs you may not want to upload to a stranger's server — and with this tool you never do.
How to use Provisioning Profile Parser
- Drop a .mobileprovision file onto the upload zone or click to browse — or paste the file's base64 into the text box.
- The tool scans the binary for the embedded XML plist and parses it locally.
- Read the summary: name, team, app ID, expiry countdown, entitlements, certificate and device counts.
- Expand the raw plist section to copy individual keys or the whole XML for bug reports and CI checks.
Frequently asked questions
Is my provisioning profile uploaded anywhere?
No. The file is read with the File API and parsed in your browser's memory. Profiles contain team IDs and device UDIDs, which is exactly why this tool never sends them anywhere.
What does the expiration countdown mean?
A profile past its ExpirationDate stops working: new installs fail and, for development profiles, apps may refuse to launch. Renew the profile in the Apple Developer portal before the countdown reaches zero.
Why are certificates and devices shown as counts?
DeveloperCertificates are embedded binary blobs and ProvisionedDevices are UDID strings. The counts — plus the ProvisionsAllDevices flag for enterprise profiles — tell you the profile's scope without dumping hundreds of lines.
The tool says it cannot find a plist — why?
Some files are wrapped differently or double-encoded. Make sure you uploaded the .mobileprovision itself, not a zipped or renamed file, and try the base64 paste as a fallback.