Plist Editor

Edit property lists in an Xcode-style key / value tree — add, rename, retype and delete entries, then save as XML or binary.

Inline tree editing
Change a value's type safely
Diff-friendly output
No Xcode, no install

Ready to open a file processed locally — nothing is uploaded

Diff-friendly by design

Keys stay in the order they were written, and types are never guessed on save: an integer stays an integer, a real stays a real, and dates and data blobs keep their own tags. Export regenerates the file, so formatting and whitespace may change, and source comments are not preserved. Review the diff before replacing the original.

Typical edits

Bump CFBundleShortVersionString in an Info.plist
Add a usage-description key required by App Review
Toggle a boolean in a preferences or LaunchAgent plist
Fix a value inside an OpenCore config.plist

A safe editing workflow

Keep a copy of the original. Edit a key or value in the tree and explicitly select its type.
Use Undo / Redo for mistakes. An invalid source edit keeps the last valid tree and blocks export until it is fixed or undone.
Download XML for readable diffs, or binary if the receiving tool requires it. Check the result in the target application; syntax checks do not validate every application's settings.

Exporting JSON? Read the type-mapping limitations first.

Frequently asked questions

Can I create a plist from scratch?: Yes — click New for an empty dictionary, then add keys with the plus button on any container row.
Can I edit the raw XML?: Yes. The source pane is editable and the tree updates as you type; invalid XML is reported instead of silently discarded.