Profile Inspector

Profile Inspector

Open a .mobileconfig file and see every payload and setting in it, laid out clearly. 💻 Local only: doesn't connect to Jamf Pro.

Use it to check a profile before you deploy it, or to work out what a profile you've inherited actually does.

How to use it

1. Drag one or more .mobileconfig files onto the window, or click Open File….
2. Each file is added to the Profiles list on the left. Click one to inspect it. Remove from list takes it out (the file itself isn't touched).

What you see

• The profile: display name, identifier, scope (for example System or User), payload type, the number of payloads and the file name.
• Each payload: its display name, payload type, identifier and every key it sets, with the value. Payloads with nothing beyond the standard fields show No additional keys.

Signed profiles

Profile Inspector reads unsigned profiles. A signed profile shows "… is not a valid .mobileconfig file". Remove the signature with Profile Unsigner first, then open the unsigned copy.

Tips

• To check whether two profiles fight over the same settings on your devices, use Profile Conflicts.
• Profile Inspector only reads the file. To change a profile, edit it in a text editor or rebuild it with one of the profile builders.

Permissions: none. Profile Inspector doesn't connect to Jamf Pro.