/etc/cups/ppd/ (for older PPD-based drivers)
Here’s an interesting, slightly offbeat write-up on the topic: You click “Print.” The printer hums. Magic? No — it’s a tiny piece of software called a printer driver , working behind the scenes like a silent translator. But if you’ve ever needed to find, fix, or move that driver, you’ve probably asked: Where does it actually live?
/Library/Printers/
Here, each manufacturer gets a folder (HP, Canon, Brother, etc.), containing .plugin or .bundle files — self-contained driver packages. macOS also uses (Common Unix Printing System), whose config file lives at:
So next time you hunt for a printer driver, remember: It might be in System32. It might be in a PPD file. Or it might be nowhere at all — because the driver became the handshake between two machines that no longer need a translator.
Modern macOS versions shift driver logic into and IPP Everywhere — essentially, drivers becoming so universal they vanish entirely. The Philosophical Twist: Is a driver even a file anymore? In the cloud-printing era, many “drivers” are just XML descriptions delivered on the fly via IPP (Internet Printing Protocol). Your computer asks the printer: What can you do? The printer replies: Here’s my driverless profile. Suddenly, the driver isn’t a file you find — it’s a conversation.
