LeCoqRoti
Minimum system: macOS 14
PlistEdit Pro 1.10.0 requires macOS 14 (Sonoma) or later. Earlier versions worked on older systems, but this release draws a line at Sonoma. It runs natively on both Intel and Apple Silicon Macs.
Initial view: keys and values expand in an outline
The file appears in an outline view where keys and values expand into familiar types: strings, booleans, dates, data or nested dictionaries. You can switch to a plain-text representation at any time. Editing is direct: click a value, type the change, and a multi-level undo chain records every step.
Can it search more than one file
Yes. A folder search lets you target an entire directory of plist files and returns every occurrence of a given key or value. For single files, find and replace works in both the outline and plain-text views, with copy and paste preserving property list structure rather than flattening it into text.
What else comes with the app
The installation includes a command-line tool called pledit for scripted edits, plus AppleScript support for automation. JSON files open in the same outline view, so you can browse and modify them with the same drag-and-drop interface used for standard property lists.
A session: editing a preferences file from start to finish
Suppose a colleague sends over a .plist from a test build where a default value is wrong. You drop the file onto the PlistEdit Pro icon in the Dock. It opens to an outline with the root dictionary expanded. The key you need is three levels deep inside a nested dictionary: you tap the right arrow key twice and press Tab to move into the value column. You type the correct string. A small grey marker appears in the undo stack at the bottom left, confirming the change is recorded.
Next you need to check whether the same key appears anywhere else in the project. You open the folder search panel, drag in the project directory, and type the key name. PlistEdit Pro returns four matches across two files. One is a release-config file you had not thought to check. You double-click the result; the file opens in a new window scrolled to the exact row. You edit it, save both files, and switch to the plain-text view for a final visual diff against the original. The session takes less than four minutes.
Gatekeeper block: clear it with one Terminal command
Gatekeeper blocks the app on first launch. After mounting the disk image and dragging the app to Applications, macOS may refuse to open it. The solution is a single Terminal command: press Enter when prompted, and the quarantine flag is removed. The app launches normally from that point on.
A file opens in plain text when you expected the outline. This usually means the file extension is not recognised or the file contains a syntax error. Rename it with a .plist or .json extension and reopen. If the content is malformed, PlistEdit Pro shows the raw text so you can locate the stray character, fix it, and switch back to the outline view.
Drag-and-drop reordering feels imprecise. The trick is to watch the blue insertion line that appears between rows, not the cursor itself. Dragging a key into a dictionary requires dropping it on the dictionary row, not between its children. After a few attempts the behaviour becomes automatic.
Find and replace skips entries you can see. Check whether the search scope is set to the current selection rather than the whole file. The scope toggle sits in the find bar; switching it to “All” immediately catches the missing hits.
Apple Silicon launch: under a second and ready to edit
On an Apple Silicon Mac, cold-launching PlistEdit Pro takes under a second. Opening a typical preferences plist of a few hundred keys happens instantly. Even a large file with several thousand entries—common when editing an application’s full default-settings manifest—loads without a beach ball. The outline view scrolls smoothly during rapid key-arrow navigation, and switching between outline and plain-text modes is immediate because both representations are kept in memory.
Memory use stays modest. After editing a dozen files across multiple windows, the app typically occupies less than 120 MB of RAM. CPU usage is flat during idle and spikes only briefly during folder searches across large directories. The app has not crashed once across several days of continuous use, and autosave writes are quick enough to go unnoticed. The only modest delay occurs when opening a file stored inside a mounted sparse bundle, where the system’s I/O overhead is the bottleneck, not the editor itself.
Binary format: your plist stays as-is when saved
Does it alter the binary format of saved plist files? No. PlistEdit Pro preserves the original format. If you open a binary plist, it stays binary when saved. The app does not convert formats unless you explicitly export to a different type. This matters for iOS developers whose build tools expect a specific format.
Can two people use it on the same Mac without clashing preferences? Yes. The app stores its settings per user in the standard ~/Library/Preferences sandbox. A designer and a developer sharing a machine will each see their own font choices, window layouts and recent-file lists.
Is the command-line tool practical for CI workflows? The included pledit tool accepts AppleScript-style commands and can read, modify and write plist values non-interactively. It works in shell scripts and Makefiles, though it does require a logged-in graphical session because it communicates with the main app via Apple Events. For headless build servers, a pure command-line alternative may be necessary, but on a developer’s laptop or a test Mac it slots into automation cleanly.
Does the preferences browser let you break system settings? The browser shows macOS preference domains in a read-only outline until you explicitly open a file for editing. It is a viewer first. You have to choose to make a change, and the undo stack is always available if a tweak produces an unwanted result.
Correspondence 0
Take a chair or join the table to send a letter.
No correspondence on this note yet. Letters are read before they appear.