Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/lzhoang2801/OpCore-Simplify/llms.txt

Use this file to discover all available pages before exploring further.

Once the Compatibility Checker has annotated your hardware report with per-device support ranges, OpCore Simplify calculates a suggested macOS version and presents the full list of versions your hardware can run. You can accept the suggestion or pick any other version in the supported range — including versions that require OpenCore Legacy Patcher.

​
How the Suggested Version Is Calculated

OpCore Simplify starts from the latest available macOS version and walks backwards through your hardware, narrowing the suggestion whenever a device’s compatibility ceiling is lower than the current candidate. The devices consulted are: CPU, GPU, Network (Wi-Fi only), Bluetooth, and SD Controller. Two special GPU cases apply additional caps before the general walk-back:
GPU ConditionSuggested Version Cap
AMD integrated GPU, or AMD APU Device IDs 59xx / 87C0Ventura (Darwin 22)
Intel Ice Lake iGPU (09xx) or Kaby Lake iGPU (19xx)Monterey (Darwin 21)
After the walk-back is complete, OpCore Simplify checks whether the suggested version is a Beta release. If it is, the major version is decremented by one and the check repeats until a stable release is reached.
If the suggested version equals the latest available release, no suggestion banner is shown — the tool simply presents the version list without a recommendation.

​
Accepted Input Formats

At the version prompt you can type any of the following:
InputInterpretationExample
Press Enter (blank)Accept the suggested versionVentura if that is the suggestion
Single integerSelect by Darwin major version22 → Ventura
major.minor.patchSelect an exact Darwin point release22.4.6 → a specific Ventura build
major.minorInterpreted as major.minor.9923.4 → Sonoma 14.4.x builds
QQuit the program—
When only the major version is entered, OpCore Simplify internally treats the minor and patch components as 99, which means “the latest point release of that major version.”

​
Example Session

Available macOS versions:

   17. macOS High Sierra 10.13
   18. macOS Mojave 10.14
   19. macOS Catalina 10.15
   20. macOS Big Sur 11
   21. macOS Monterey 12
   22. macOS Ventura 13
   23. macOS Sonoma 14
   24. macOS Sequoia 15
   25. macOS Tahoe 26 (Requires OpenCore Legacy Patcher)

Note:
- To select a major version, enter the number (e.g., 19).
- To specify a full version, use the Darwin version format (e.g., 22.4.6).

Please enter the macOS version you want to use (default: macOS Ventura 13):
Pressing Enter here selects macOS Ventura 13. Typing 23 would select Sonoma instead.

​
macOS Version Reference

macOS NamemacOS VersionDarwin MajorExample Darwin Version
High Sierra10.131717.7.0
Mojave10.141818.7.0
Catalina10.151919.6.0
Big Sur112020.6.0
Monterey122121.6.0
Ventura132222.6.0
Sonoma142323.6.0
Sequoia152424.5.0
Tahoe262525.0.0

​
OCLP Versions

If one or more of your devices have an OCLP Compatibility range, those macOS versions also appear in the list, labelled “Requires OpenCore Legacy Patcher” in amber text. Selecting a version that falls inside the OCLP range is permitted. However, OpCore Simplify will present an OpenCore Legacy Patcher Warning before the build step begins, giving you the opportunity to choose a different version. See Building EFI for details on the OCLP warning dialog.
Selecting an OCLP-required macOS version means macOS security features (SIP and AMFI) must be disabled on the final system. Consider whether this trade-off is acceptable for your use case before proceeding.

​
Changing the Version Later

You can return to the version selector at any time from the main menu using Option 2 — Select macOS Version. Changing the version re-runs hardware customization, SMBIOS selection, and kext selection automatically to match the new target.
If you are unsure which version to target, accept the suggestion. It represents the highest stable macOS release that all of your hardware can support natively, without requiring OCLP.

Build docs developers (and LLMs) love

Get started for freeTalk to us