Plist Workbench
Open any Apple plist — binary or XML — read it as a tree, edit it safely, and export it back. No install, no upload.
A plist is the settings file Apple puts everywhere — and the one format you cannot fix in a text editor. Every app carries an Info.plist, every launchd job is a plist, and provisioning profiles and .mobileconfig files are plists in disguise. Half of them are binary, so opening one in a text editor shows garbage — and hand-editing the bytes corrupts it. This workbench parses binary and XML plists locally, shows the structure as an editable tree, checks launchd jobs against the documented rules, and exports your edited copy as XML, binary, JSON or CSV. Android manifests live in the APK analyser; .env files are a different format with their own parser; launchd’s Linux cousin is the systemd unit auditor. The companion article how to read and edit plist files walks through the same keys by hand.
Last updated:
Your plist input
Results
Edited
launchd validation
Plist tree
🔒 Your file never leaves your device. Parsing and editing run entirely in your browser — no upload, no server call, no account.
Binary vs XML plist — and the bplist00 anatomy
A plist is the same data in two costumes. The XML form is text you can read:
A binary plist is three parts. First the object table: every value — strings, numbers, dates, data blobs, arrays, dicts — encoded as a marker byte (type in the high nibble, size or count in the low nibble) followed by its bytes. Then the offset table: one entry per object, saying where each object starts. Then a 32-byte trailer: the offset-int size, the object-ref size, the object count, the top object, and where the offset table begins. That trailer is how a parser finds anything — and why a truncated file, or a bad offset table, is rejected outright instead of guessed at.
Plists hide in four places. Info.plist sits inside every macOS and iOS app bundle and names the bundle ID, version and permissions. launchd jobs live in ~/Library/LaunchAgents and /Library/LaunchDaemons and say what to run and when. A .mobileprovision file is a signed plist (wrapped in CMS) naming the app, devices and entitlements. A .mobileconfig file is a plist describing device settings a profile installs. If the file starts with bplist00 it is binary; if it starts with
The JSON export documents its mapping, because JSON has no date, data or UID type. Dates become ISO-8601 strings ("2026-11-19T09:19:00.000Z"), data becomes {"$data": "
What this workbench does — and what it does not
It parses, shows and edits. It reads a binary or XML plist into a value model, shows it as an expandable tree with a path, type and value preview for every node, and lets you edit scalars, rename keys, add or delete keys and array items, and change a value’s type where the conversion is unambiguous. Every export — XML, binary, JSON, CSV — is generated from the current edited model, so what you see is what you download.
It does not install anything. It does not install a .mobileconfig profile, does not load a launchd job, and does not run anything named in the plist — it only reads and rewrites the file. It does not validate code signatures or provisioning entitlements against Apple: a plist that parses cleanly can still be expired, revoked, or signed by someone you should not trust.
It never touches your original file. Editing happens in the browser’s memory; the file on your disk is unchanged until you download an export and choose to replace it yourself. Keep a backup of the original before you overwrite anything — a converted binary plist that launchd rejects is your problem to roll back, and this page will not do it for you.
Be honest with yourself before you edit a plist
Hand-editing a binary plist in a text editor corrupts it — that is the whole reason this tool exists. The safe path is convert binary to XML, edit the XML, convert back, and re-parse to verify. Even then, keep the original: a one-character mistake in a bundle ID or a launchd path fails silently at runtime.
The launchd checks are semantic, not a launchd run. They test your job against the documented rules — Label present, exactly one of Program and ProgramArguments, StartCalendarInterval fields in range, booleans really boolean — but launchd itself is the final judge. A job that passes here can still fail to load for a reason this page cannot see, like a missing executable or a permissions problem.
A plist that parses is not a plist that works. The structure can be perfect while the meaning is wrong: a mistyped bundle ID, an entitlement your provisioning profile does not grant, a profile payload for a device that is not yours. Parsing tells you what the file says; only Apple’s checks — and running the thing — tell you whether it is true.
What happens to your file
Nothing leaves your browser. The file or pasted text is parsed by JavaScript on this page: no upload, no server call, no storage, no account. Closing the page discards everything, including your edits.
Frequently asked questions
How do I tell a binary plist from an XML one?
Look at the first bytes. A binary plist starts with the eight characters bplist00 — open it in a text editor and you see that, then garbage. An XML plist starts with
Is it safe to edit a launchd plist here?
Safer than editing the bytes by hand, but not risk-free. Your edits live in the browser’s memory and the original file on disk is never touched; you download a new file and decide yourself whether to replace the old one. Keep a backup of the original, and test the new job with launchctl on a copy before it matters. This tool never loads the job for you — installing it is your step, on purpose.
Why does the JSON export write dates as strings and data as {"$data": ...}?
JSON has no date, binary-data or UID type, so the export has to encode them somehow — and the mapping is written on this page so nothing is lost silently. Dates become ISO-8601 strings, data becomes {"$data": "