A device driver is a specialized program that enables an operating system to control and exchange data with a particular piece of hardware. Hardware units do not all respond to the same commands or protocols, so a driver acts as an interpreter between the OS and the device's unique interface. For general reference to how drivers relate to hardware, see hardware documentation.
How device drivers operate
Drivers translate high-level operating system requests (for example, "print this page" or "draw this image") into low-level commands the device understands. They typically run in one of two contexts: kernel mode, where they have direct access to system resources and perform time-critical operations, or user mode, where they run with fewer privileges and can be isolated from core system code. Drivers handle I/O requests, manage device registers or memory buffers, respond to interrupts, and often coordinate with firmware on the device itself.
Common types and examples
Many parts of a computer require drivers because each manufacturer implements hardware differently. Typical examples include:
- Printers — drivers provide page layout, resolution options, and spooler integration.
- Graphics adapters (GPU) — vendors such as AMD and Nvidia supply drivers that enable rendering, acceleration, and power management.
- Modems — handle connection protocols and data modulation.
- Network interface cards — drivers implement packet handling, offload features, and link management.
- Sound cards — provide audio buffering, mixing, and sample-rate handling.
Development, distribution, and operating system dependence
Drivers are platform-specific. A driver compiled for one operating system cannot normally be used on another; for example, drivers distributed for macOS will not work on Microsoft Windows without a compatible port. Vendors often provide signed, signed-and-certified, or open-source drivers. Signed drivers use cryptographic signatures to verify publisher identity and integrity, which modern OSes often require for kernel-level components. Operating systems also supply generic or class drivers that cover many devices that conform to common standards, reducing the need for vendor-supplied code.
Design approaches and practical considerations
Driver design choices affect performance, reliability, and security. Key distinctions include:
- Monolithic vs. modular: modular drivers can be loaded or unloaded without rebooting, aiding updates and debugging.
- User-mode vs. kernel-mode: user-mode drivers reduce crash risk to the system but might have higher context-switch overhead.
- Proprietary vs. open-source: open drivers allow community inspection and ports between systems, while proprietary drivers often include vendor-optimized features.
Best practices for administrators and developers include keeping drivers up to date, using signed drivers from trusted sources, and testing drivers in controlled environments before deployment. Driver faults are a common cause of system instability and security vulnerabilities because they operate close to hardware and frequently require high privileges.
History, significance, and future trends
Device drivers grew in importance as personal computers diversified and operating systems evolved to support plug-and-play enumeration and hot-swapping of devices. Today drivers remain central to performance-sensitive areas such as graphics, networking, and storage. Trends include more robust driver frameworks that isolate faults, improved APIs for power and resource management, and increasing use of virtualization to encapsulate device access. For vendor resources and guidance on writing or obtaining drivers, consult manufacturer documentation and platform-specific developer resources such as hardware and OS guides.