DriverKit and System Extensions: Drivers for Modern macOS

Hardware vendors once shipped kernel extensions that loaded into the macOS kernel. With macOS 10.15 Catalina, Apple introduced system extensions and DriverKit as their replacement and began deprecating kernel extensions where an alternative exists. A DriverKit driver, known as a dext, runs in its own user-space process with restricted privileges. New macOS driver work should start there.

At a glance

10.15
macOS Catalina, the release that introduced DriverKit and system extensions.
dext
A DriverKit extension: a driver bundle that runs as an isolated user-space process.
Entitlement
Apple must grant DriverKit entitlements to your developer account before a dext can ship.
Notarised
Outside the App Store, the host app must be signed with a Developer ID and notarised.

The problem

Kernel extensions still exist, but on Apple silicon Macs loading a third-party one requires the user to lower the system security policy in recovery mode and then approve the extension. For most products that support burden is unacceptable.

Porting a kernel extension directly is rarely straightforward. DriverKit exposes a narrower set of families and APIs, its interface definitions use their own format, and the driver runs in a process that must be installed and approved, not simply copied into a folder.

On current macOS a driver is as much an app feature as a kernel feature, so plan the entitlements, installer and approval flow alongside the code.

How a dext ships

A dext is embedded in a host application, which asks the system to activate it through the System Extensions framework. The user approves it once in System Settings, after which the system loads it whenever matching hardware appears. The host app generally needs to be in the Applications folder for activation to succeed, and it must be signed and, outside the App Store, notarised.

DriverKit provides families for USB, HID, PCIe, serial, networking, audio and some storage devices. Before starting, check that a family exists for your device type on the oldest macOS version you must support, and request the matching entitlements from Apple early, since approval is not instant. DriverKit is also available on iPadOS for iPads with M-series chips.

What good looks like

Confirm that DriverKit supports your device class on the macOS versions you target.

Request DriverKit entitlements from Apple for your device as soon as development begins.

Build the host app and installer flow early, and test activation, upgrade and removal on a clean Mac.

Kernel extension and DriverKit extension
Kernel extensionDriverKit extension
Runs inKernelUser-space process
Effect of a crashKernel panicDriver process ends
Installation on Apple siliconReduced security mode neededApproved in System Settings
API breadthBroad kernel APIsDefined DriverKit families
StatusDeprecated where alternatives existRecommended
Why new macOS drivers should be written for DriverKit.
Main DriverKit families
FamilyDevice types
USBDriverKitUSB devices and interfaces
HIDDriverKitKeyboards, pointing devices and other HID hardware
PCIDriverKitPCIe devices, including those attached over Thunderbolt
SerialDriverKitSerial port devices
NetworkingDriverKitNetwork interfaces
AudioDriverKitAudio devices
Availability varies by macOS version; check the minimum version for each family you need.

What it changes

System Stability

A faulty driver ends its own process instead of panicking the kernel.

Supported Path

The driver uses the model Apple is investing in, not one being phased out.

Smooth Install

Users approve the extension once, without changing security settings.

Apple Silicon Ready

The same approach works on current Macs without reduced security modes.

Where to go next

If the hardware is also supported on Linux or Windows, keep device logic in a portable library and make the dext a thin layer over it.

Many USB and HID devices need no driver on macOS at all, so check that first.

Problems this prevents

  • Customers asked to lower Mac security settings
  • A release blocked waiting for entitlements
  • Kernel extension code that will not port directly
  • Install flows never tested on a clean machine

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.