Where Is the Clover config.plist File?
Where Clover keeps its boot config.plist file on the ESP disk, and how its layout differs from OpenCore.
Last updated
Clover keeps its config in a vendor folder on the EFI system partition with drivers and tables beside it. The main plist names every patch the boot needs. Newer builds nest drivers in a versioned child folder.
The layout mirrors OpenCore at a glance but the folders and formats never mix. Mount the ESP with the OS appropriate command before browsing. Keep a known good plist copy since one typo stops the boot. SMBIOS choices share the plist file, so one backup covers every boot entry. Keep a known good copy offline.
Where Clover stores this, by platform
/boot/efi/EFI/CLOVER/config.plist
ESP vendor folder with the main plist plus drivers and tables. Never interchangeable with the OpenCore tree. Mount the ESP first.
Frequently asked questions
Can I rename a Clover config for OpenCore use?
Clover reads the vendor folder with its own name while OpenCore reads a different vendor folder, and the formats never interchange. Mount the ESP and check which vendor tree actually exists. Convert with a proper tool rather than renaming files.
Clover boots but shows no macOS entry. How do I fix it?
Mount the ESP, then confirm the plist plus the versioned drivers tree sit in the vendor folder. Newer builds moved drivers into a versioned child that older guides omit. Missing drivers stop macOS from appearing in the menu.
Notice an outdated path? Let us know.