plist XML ↔ JSON

Client

Convert between Apple property list XML and JSON—paste XML plist text or JSON objects typical of Info.plist and app metadata. This page targets plist semantics, not arbitrary XML; use JSON ↔ XML for generic documents.

Learn more: plist XML vs generic XML

Convert between Apple plist XML and JSON for Info.plist–style bundles, mobile provisioning metadata, and other tools that emit plist XML—not for arbitrary XML documents.

What plist XML is

A plist file is a small XML vocabulary: a root plist element containing one value—usually a dict with alternating key and typed value tags (string, integer, true, array, data, and so on). It is narrower than general XML, which makes round-trips more predictable than ad-hoc element trees.

Not a substitute for JSON ↔ XML

If you need to map custom tags or mixed content, use the JSON ↔ XML tool. This page uses a plist parser and builder so behavior matches Apple-style plists; binary .plist files must be converted to XML elsewhere before pasting.

JSON & plist XML

?

JSON → plist uses JSON.parse then a plist XML builder. plist → JSON uses an Apple plist XML parser on the XML text, then JSON.stringify for display.

This is not a general-purpose XML ↔ JSON tool—use the JSON ↔ XML page for arbitrary documents. Binary .plist files are not supported here; paste XML plist only.

Sample JSON is pre-filled—click JSON → plist, or load the plist example and try plist → JSON. Parsing runs in your browser.

Common use cases

  • Inspect or edit Info.plist–style data as JSON, then copy plist XML back into an Xcode or CI template.
  • Compare two plist sources by round-tripping through JSON for a familiar structure.
  • Share a minimal plist snippet with someone who prefers editing JSON.
  • Skim entitlements or sandbox keys in JSON before merging plist fragments from different branches.

Common mistakes to avoid

  • Pasting binary plist files

    Binary .plist blobs are not accepted here—export XML from PlistBuddy, Xcode, or plutil -convert xml1 first.

  • Expecting the same behavior as generic JSON ↔ XML

    Plist has a fixed tag vocabulary (dict, key, string, array, …). Arbitrary XML should use the JSON ↔ XML tool instead.

  • Assuming every Apple tool writes identical whitespace

    Pretty-printed plist XML can differ slightly between exporters. Rely on parsing equality, not line-for-line text matches.

FAQ

Is data uploaded?

No. Parsing and building run in your browser tab.

Does this validate against App Store or notarization rules?

No—this only converts formats. Entitlements and signing still need your build pipeline and Apple’s tooling.

Can I convert generic RSS or SOAP XML here?

Use JSON ↔ XML for arbitrary documents. This page is optimized for plist semantics (dict, array, key/value pairs).

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • plist to json online
  • info plist to json converter
  • json to plist xml online
  • apple plist xml converter browser

More tools

Related utilities you can open in another tab—mostly client-side.