PlistEdit Pro 1.10.0 — macOS

If you have ever edited a .plist file in Xcode and wished for something more direct, PlistEdit Pro is that tool. It handles property list files and JSON files with equal ease, showing them in an outline view or as plain text depending on what you need. The current version, 1.10.0, runs on macOS 14 or later and includes structure definitions for standard plist files, so you are not guessing at keys.

What it does for you

Beyond basic editing, PlistEdit Pro includes a preferences browser for macOS preference plists, a find and replace function that can search entire folders of plist files for a specific key or value, and a drag-and-drop interface for moving data around. If you automate tasks, AppleScript support is built in. It is not a flashy tool—it is a practical one for anyone who needs to work with plists or JSON regularly.

Who should use it

This is for developers, sysadmins, and anyone who finds themselves opening plist files more than once a week. It is also useful for power users who want to dig into app preferences or system configuration files. The outline view makes it easy to navigate nested data, and the text view gives you full control when you need it.

Where beginners tend to slip up

The most common mistake I see is treating a plist file like a plain text document and trying to edit it in a basic text editor. PlistEdit Pro opens them correctly, preserving structure and types, but if you force-save from another app you can corrupt the file. Always open plists inside PlistEdit Pro, not in TextEdit or VS Code.

Another frequent slip is forgetting that plist keys are case-sensitive. name and Name are not the same key. PlistEdit Pro's outline view shows the tree exactly as the system expects it, so it is worth checking the case before you paste in a value from documentation.

Beginners also sometimes drag items into the wrong parent node in the outline view. The drag-and-drop is precise, but if you drop a key into a sibling instead of a child, the hierarchy shifts. Use the undo command straight away if something looks off—multi-level undo is there for exactly this reason.

Finally, people often miss the folder search feature. Instead of opening one file at a time, you can point PlistEdit Pro at a whole folder and search for a key or value. It saves a lot of manual opening and closing.

A typical session: cleaning up a preference file

Let me walk through a real-world session. Suppose a colleague passes me a corrupted preferences file from an internal tool. I open PlistEdit Pro, drag the .plist onto the window, and the outline view shows me the structure immediately. The first thing I notice is a duplicate key sitting under UserSettings. I select the duplicate, delete it, and the tree collapses cleanly.

I then use the find function to locate a particular value—windowPosition—that should be a set of four integers. It is a string instead. I click the field in the outline, change the type from string to array, and paste in the correct numbers. The file still looks tidy because PlistEdit Pro updates the view as I go.

Before saving, I check the preferences browser to confirm the file is a standard macOS preference plist. That step is not mandatory, but it catches files that have drifted from the expected schema. I save, close PlistEdit Pro, and hand the file back. The whole job takes a few minutes because I did not have to switch between tools or guess at the structure.

Switch to outline view for binary plists

If you open a plist and see garbled text in the plain text view, you are likely looking at a binary plist. Switch to the outline view—PlistEdit Pro decodes binary plists there. The plain text view works best with XML plists and JSON files.

Another snag: the file does not save because you do not have write permissions. This happens often with system plists in /Library/Preferences. PlistEdit Pro will warn you, but you need to copy the file to a writable location, edit it there, then copy it back with appropriate permissions. The app cannot override system file protections on its own.

Sometimes users report that find and replace returns no results even though they know the key exists. Check that you are searching in the right scope—the feature can look in a single file or across a folder. Also verify the exact spelling and case of the key. Using partial matching instead of exact match often helps.

If PlistEdit Pro does not open a JSON file at all, confirm the file is valid JSON first. A missing comma or an extra bracket will stop it from parsing. Validate the file with a linter before you bring it into PlistEdit Pro.

One last thing: the pledit command-line tool is handy for batch operations, but remember that it works on the file in place. Keep a backup copy before you run any scripted changes. That applies to any tool, but it is worth repeating here.

• Requires macOS 14 or later.
• Updated user interface elements for macOS Tahoe.
• Moved the prefs browser options checkboxes into a toolbar menu.
• Changed the 'Ask to revert when file changes on disk' option to a small popover.

• macOS 14 or later
• Intel or Apple Silicon