OpenCore config.plist Editor

Drop your EFI/OC/config.plist to view and edit it in a tree, catch the mistakes that stop a Hackintosh from booting, and download it with key order and data types untouched.

Drag & drop
Validates OpenCore schema
Base64 ⇄ Hex
Never uploaded

Ready to open a file processed locally — nothing is uploaded

Base64 ⇄ Hex converter

Guides such as Dortania list values like AAPL,ig-platform-id in hex, while the XML file stores them as Base64. Convert here, or type a hex value straight into a data field in the tree as 0x07009B3E or <07009B3E>.

Hex: 07009B3E
Base64 (as in XML <data>): BwCbPg==
Little-endian integer: 0x3E9B0007 (1050345479)
ASCII: ···>
Length: 4 byte(s)

What gets checked

All eight top-level sections exist and are dictionaries: ACPI, Booter, DeviceProperties, Kernel, Misc, NVRAM, PlatformInfo, UEFI
Entries in ACPI, Booter and Kernel lists, and in Misc › Tools and UEFI › Drivers, have the required fields with the right types; MinKernel/MaxKernel are Darwin versions
Lilu.kext is loaded before its plugins (WhateverGreen, VirtualSMC, AppleALC…); duplicate kexts, SSDTs and drivers
Patch Find/Replace lengths match; Mask/ReplaceMask lengths are valid
UEFI › Drivers use the dictionary format and include OpenRuntime.efi
SMBIOS: sample serial, MLB, UUID or ROM left in place; ROM is 6 bytes
Security: Vault, DmgLoading and SecureBootModel values; SIP (csr-active-config) and boot-args that weaken security
Leftover #WARNING keys from Sample.plist; DeviceProperties keys that aren't PCI paths

Frequently asked questions

Does this replace ocvalidate?: No. It catches common mistakes instantly in the browser, but ocvalidate from your exact OpenCore release is still the reference check.
Is my serial number uploaded?: No. The file is read and edited locally in your browser, so SMBIOS values never leave your computer.
Does it work on Windows?: Yes — any modern browser on Windows, Linux or macOS, with no ProperTree or Python install.