ProperTree: A Python and Tkinter plist editor for OpenCore configs
Cross platform GUI plist editor written in python.
At a glance
- What is it?
- ProperTree is a cross-platform GUI plist editor written in Python and Tkinter, built mainly for people hand-editing OpenCore config.plist files. It installs by cloning the repo and running a script, and its OC Snapshot feature walks your ACPI, Kexts, Tools and Drivers folders to keep the config in sync.
- Who is it for?
- Adopt ProperTree if you edit OpenCore config.plist files by hand and want a tree view, undo, and a snapshot routine that reads your Kexts and ACPI folders instead of trusting your memory. Skip it if you want a packaged installer, a signed macOS app, or a general-purpose plist tool with no OpenCore opinions; the project ships as a repo you clone, and the macOS bundle is something you build yourself with Scripts/buildapp-select.command.
- Can I use it commercially?
- Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 148 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- corpnewt/ProperTree3,205 ★ · +55
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| corpnewt/ProperTree | 3.2k | 3.2k |
55 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What ProperTree is for, and who actually needs it
A plist is an XML or binary property list, and most of the time you never open one by hand. ProperTree exists for the cases where you do. The README describes it as a cross-platform GUI plist editor written using Python and Tkinter, and the feature list makes the intended audience obvious: a context-aware right-click menu that includes template info for OpenCore or Clover config.plist files, plus an OC (Clean) Snapshot that walks the contents of ACPI, Drivers, Kexts and Tools for OpenCore config.plist files. That is not a general-purpose editor with an OpenCore plugin bolted on. The OpenCore workflow is the reason the tool exists.
The people who get value from it are the ones editing an OpenCore config by hand: adding a kext, reordering the Kernel -> Add array, checking that a driver entry matches what is actually in the Drivers folder. Doing that in a text editor means counting array indices and hoping you did not break the XML. ProperTree gives you a tree, a full undo-redo stack, find and replace across keys or values, and drag and drop to reorder nodes. If you never touch an OpenCore config, almost nothing here applies to you.
How the editor and the OC Snapshot mechanism work
The interface is Tkinter, and the README says the tool is compatible with both Python 2.x and 3.x, which explains some of the backported features listed: binary property lists and unicode support on Python 2, and expanded integer casting so that hex values such as 0xFFFF inside xml <integer> tags are accepted. Documents are handled per window, so you can have several plists open at once.
The interesting part is the snapshot. According to the README, OC Snapshot prompts you to select an OC folder, then walks the ACPI, Kexts, Tools and Drivers directories inside it and compares every entry against the current document's ACPI -> Add, Kernel -> Add, Misc -> Tools and UEFI -> Drivers sections. It adds or removes entries to match. It also orders kexts by reading each kext's CFBundleIdentifier and comparing it against every other kext's OSBundleLibraries in their Info.plist, so a kext that others depend on is loaded before them. It warns on duplicate CFBundleIdentifiers, with MinKernel, MaxKernel and MatchKernel overlap checks, and offers to disable all but the first. It also checks for disabled parent kexts that have enabled children.
The schema choice is the detail worth understanding. By default, ProperTree determines the schema by comparing the MD5 hash of OpenCore.efi against a known list of Acidanthera debug and release versions. If the hash matches nothing, it falls back to the newest schema in the script's snapshot.plist. The README notes this can be changed in Settings under OC Snapshot Target Version. So the snapshot is only as accurate as that hash match, and a custom or rebuilt OpenCore.efi will push you onto the fallback path.
Installing ProperTree and running a first snapshot
There is no installer and no package on a registry. The README gives two routes: download the repo as a ZIP from the green Code button, which means updates require downloading again, or clone it with git so you can pull later. On *nix systems the documented commands are a clone followed by running the script with python or python3.
git clone https://github.com/corpnewt/ProperTree
python3 ./ProperTree/ProperTree.pyOn macOS the README says you can double-click ProperTree.command after cloning to launch. On Windows, the documented route is the batch file:
git clone https://github.com/corpnewt/ProperTree
./ProperTree/ProperTree.batIf the launch fails with ModuleNotFoundError: No module named 'tkinter', the GUI library is missing. The README gives the Ubuntu command for that case:
sudo apt-get install python3-tk -yOnce the window is open, open your config.plist and use the context-aware right-click menu. For the snapshot itself, the README's advice on ordering is explicit: use OC Clean Snapshot the first time, so any sample entries in the config.plist are cleared and added anew, and use a regular OC Snapshot for every snapshot after that, because a regular snapshot starts from what is already in the document and only pulls changes, which preserves customisations you have made. Expect the snapshot to prompt you for the OC folder before it does anything.
Where ProperTree breaks or becomes the wrong tool
The README's FAQ is largely a list of platform failures, and they are worth reading before you commit. On Sonoma (14.x) and newer, clicks may not register; the README attributes this to python 3.11.x and older interacting badly with tk on macOS, and says updating to at least python 3.12.0 appears to fix it. The stated workaround if you cannot update is to move the window around before clicking elements in the treeview, which is a workaround, not a fix. On Monterey (12.x) and newer, the README describes two separate problems: a black window caused by the default tk shipped with macOS, and an inability to open or save plist files, which it ties to the built-in tk and the earlier universal installers from python.org. The recommended path in both cases is installing a python.org build with a compatible tk and then using Scripts/buildapp-select.command to build an application bundle.
There is also an open crash on international keyboard layouts on macOS, reported as an NSRangeException with characterAtIndex out of bounds, which the README describes as a bug in the Cocoa implementation.
As a tool choice, ProperTree is the wrong answer if you want a signed, notarised application you can install without thinking about Python versions, or if you want to edit plists that have nothing to do with OpenCore. The version sensitivity is the real cost here: your editor's behaviour depends on which Python and which tk you happen to have.
ProperTree compared with OCAT
The natural comparison is OCAT, and the difference is in what each one treats as the source of truth. ProperTree is an editor first: you open a plist, you edit the tree, and the snapshot feature reconciles four specific sections of an OpenCore config against folders on disk. The document is the thing you are working on, and the snapshot is an operation you invoke against it.
OCAT takes the opposite approach. It is organised around OpenCore versions and their schemas, so the config is validated and updated against a chosen OpenCore release rather than against the contents of your EFI folder. That makes OCAT the better fit when your question is whether a key exists in a given OpenCore version or what changed between releases. ProperTree's schema awareness comes from hashing OpenCore.efi and falling back to the newest schema in snapshot.plist when the hash is unknown, which is a narrower form of the same idea. If you want the config checked against a version you pick explicitly, OCAT's model is the more direct one. If you want to drag nodes around, undo a mistake, and have your kext load order derived from the kexts themselves, ProperTree is doing work OCAT is not.
Maintenance, upgrade cost and the licence
The repository is not archived, and the last push was on 2026-06-20. That is the whole of what can be said about activity from the available facts; there are no releases listed. Upgrades follow whichever install route you chose. A git clone can be updated with git pull. The ZIP route cannot, and the README states plainly that updates then require downloading the repo again the same way. For the macOS application bundle, the bundle is built from your installed Python path via Scripts/buildapp-select.command, so a Python upgrade can mean rebuilding the bundle rather than just pulling the repo. On Windows, the README notes that AssociatePlistFiles.bat is location-dependent, so moving your copy of ProperTree means re-running it.
The licence is BSD-3-Clause, which is permissive and, unlike a copyleft licence, does not require you to publish modifications you distribute. That said, this is a description of the licence identifier in the repository, not legal advice; if you plan to redistribute ProperTree inside a product, read the LICENSE file at the repository root and get your own advice.
Editorial conclusion
Adopt ProperTree if you edit OpenCore config.plist files by hand and want a tree view, undo, and a snapshot routine that reads your Kexts and ACPI folders instead of trusting your memory. Skip it if you want a packaged installer, a signed macOS app, or a general-purpose plist tool with no OpenCore opinions; the project ships as a repo you clone, and the macOS bundle is something you build yourself with Scripts/buildapp-select.command. Before relying on it, check your Python version against the Sonoma and Monterey notes in the README, and confirm on a copy of your config whether a regular OC Snapshot preserves the customisations you care about.
Frequently asked questions
How do I install ProperTree on Windows?
Clone the repository and run the batch file, which the README documents as git clone https://github.com/corpnewt/ProperTree followed by ./ProperTree/ProperTree.bat. Alternatively you can download the repo as a ZIP, though the README notes that route does not let you update with git pull.
How do I install ProperTree on macOS?
Clone the repository and run python3 ./ProperTree/ProperTree.py, or simply double-click ProperTree.command after cloning, which the README lists as the macOS route. If you want a bundle you can associate with .plist files, the README points to Scripts/buildapp-select.command.
What is the difference between OC Snapshot and OC Clean Snapshot in ProperTree?
Both do the same work but start from different places. A clean snapshot first clears ACPI -> Add, Kernel -> Add, Misc -> Tools and UEFI -> Drivers and adds everything from the corresponding folders anew, while a regular snapshot starts from what is already in the document and only adds or removes entries as needed.
How do I use ProperTree to edit an OpenCore config?
Open the config.plist in the tree view and use the context-aware right-click menu, which the README says includes template info for OpenCore or Clover config.plist files. For the kexts, ACPI, Tools and Drivers sections, run OC Snapshot and select your OC folder when prompted; use OC Clean Snapshot the first time and a regular snapshot afterwards.
Is OCAT an alternative to ProperTree?
They solve overlapping problems differently. ProperTree is a document-based plist editor whose snapshot reconciles four config sections against folders on disk, while OCAT is not discussed in the ProperTree README at all, so its behaviour has to be checked against its own documentation.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/corpnewt-propertree)Star history chart for your README
[](https://hysenlabs.com/projects/corpnewt-propertree)Was this useful?