PlistEdit Pro 1.10.0 Mac

PlistEdit Pro is a dedicated editor for property list and JSON files that slots in alongside Xcode and other development tools on a Mac. Rather than replacing a full IDE, it focuses on the tasks that come up when you are debugging a preference file, auditing a folder of plists, or tweaking a JSON configuration outside of a project build. The interface is built for keyboard navigation, so repetitive edits stay fast without reaching for a mouse.

A feature developers lean on is the ability to search an entire directory of plist files for a specific key or value. Instead of opening each file individually, you point the app at a folder and get results in one pass. Drag-and-drop support also means you can restructure data by moving entries within the outline view, which is quicker than cutting and pasting raw XML.

For automation, PlistEdit Pro includes AppleScript support. This lets you script batch changes or integrate the editor into a build pipeline. The app also ships with structure definitions for standard property list files, so common keys are displayed with their expected types and value ranges. A built-in preferences browser gives you direct access to macOS’s own preference plists, and you can customize the display font to match what you use in your code editor.

Fat Cat Software positions the tool as a companion for Mac and iOS developers, and its role becomes clearer when you think about the gaps it fills: fast folder searches, scripted edits, and a lightweight way to inspect system preferences without digging through ~/Library.

Editing installer packages, launch daemons, and profiles without Xcode

Mac and iOS developers working outside of Xcode’s managed build environment see the biggest payoff. If you maintain installer packages, launch daemons, or configuration profiles, you are likely editing plists by hand. The outline view in PlistEdit Pro respects the data types that matter — booleans actually appear as checkboxes, dates get a calendar picker, and arrays can be reordered with a drag. That removes a whole layer of syntax errors that creep in when you type XML or JSON by hand.

IT admins who manage fleets of Macs also find it useful. When a configuration profile misbehaves, the folder search can sweep through a directory of deployed plists and pinpoint which machine has a stray key. The AppleScript support means those same admins can script a weekend audit without writing a custom parser. Even technical support staff who do not write code day-to-day can use the preferences browser to check whether a user’s settings file is corrupted, without teaching them how to read raw plist syntax in TextEdit.

No warning when a file sits inside a sandboxed or protected folder

One early frustration is that the app does not warn you when a file is locked by the system. If you open a plist inside a protected folder — say, a sandboxed container — the editor appears to let you make changes, but saving throws a permissions error. The simplest fix is to duplicate the file to your desktop, edit it there, and then replace the original in Finder after authenticating. Another approach is to launch the app itself as root for quick system-level edits, though that is a deliberate choice, not a default.

JSON editing introduces a different set of snags. PlistEdit Pro auto-detects the format, but if a JSON file has a syntax error — a trailing comma in an object, for example — the app refuses to open it in outline view and falls back to the plain text pane. Fix the error in a lightweight text editor first, then reopen it. Users also occasionally trip over the find-and-replace panel: it searches the visible outline structure, not the raw text, so a key named name nested inside two dictionaries will match only if you expand those nodes first. Expanding all nodes with a single keyboard shortcut before running a search avoids that confusion.

Font customization is another area where new users sometimes go in circles. Changing the display font in the preferences window applies to the outline view, but the plain text pane uses its own setting. If you want both to match, you have to set each one separately. It is a small thing, but it catches people who switch between views and wonder why the font looks inconsistent.

Native Apple Silicon support and faster folder searches after macOS 14 cutoff

Version 1.10.0 raised the minimum requirement to macOS 14, which cuts off older hardware but also means the app runs natively on both Intel and Apple Silicon without Rosetta translation on M-series machines. In practical terms, folder searches over large directories feel snappier on recent hardware, and the memory footprint stays low even when you have dozens of files open.

The version 1.1 update rehoused several interface controls that used to clutter the preferences window. The checkboxes for the preferences browser options moved into a toolbar menu, so the window itself is shorter and you are not scrolling past options you rarely change. The "Ask to revert when file changes on disk" setting changed from a checkbox to a small popover that appears only when the situation actually occurs. That cuts down on dialogue fatigue — you no longer get prompted when nothing has changed on disk, and the popover is dismissible with a single keystroke.

For anyone who uses the pledit command-line tool as part of a scripted workflow, the move to macOS 14 means the tool now respects the tighter security model without needing additional entitlements. The net result for daily use is fewer permissions prompts and a quieter background experience when the tool is invoked from a cron job or a CI pipeline.

Version 1.10.0 raises the minimum system requirement to macOS 14. The update also refreshed interface elements for macOS Tahoe and moved the preferences browser’s option checkboxes into a toolbar menu. The ‘Ask to revert when file changes on disk’ setting now appears in a small popover instead of a standalone dialog.

• macOS 14 or later
• Apple Silicon and Intel Macs