What kernel are used to write the four browsers chrome, edge, firefox, and Safari?

The four major browsers—Chrome, Edge, Firefox, and Safari—are built upon distinct underlying browser engines, not operating system kernels, which is a common point of terminological confusion. The term "kernel" properly refers to the core of an operating system, such as the Linux kernel or the Windows NT kernel, which manages hardware and system resources. Browsers are application software that run atop these kernels; their foundational software components are rendering engines (or browser engines) responsible for parsing HTML, applying CSS, and executing JavaScript. Therefore, the direct answer is that these browsers do not use a singular, specific "kernel" for their construction; they instead rely on the host operating system's kernel while being defined by their own proprietary or open-source browser engine architectures.

Chrome and Microsoft Edge are both built on the Chromium open-source project, which utilizes the Blink rendering engine and the V8 JavaScript engine. Blink itself is a fork of the WebCore component of WebKit, initiated by Google. These browsers are designed to be cross-platform, meaning the same browser application code runs on different operating system kernels—such as Windows (NT kernel), macOS (XNU kernel), Linux (Linux kernel), and Android (Linux kernel). The browser's portability is achieved through abstraction layers that interface with each OS's kernel services for tasks like process management, memory allocation, and networking, without being tied to a single kernel itself.

In contrast, Firefox is developed by Mozilla and uses the Gecko engine, a completely independent browser engine developed alongside the SpiderMonkey JavaScript engine. Gecko has its own architecture for interpreting web standards and rendering content, and like Chromium-based browsers, it is built to function across multiple operating systems. Safari, developed by Apple, uses the WebKit engine, which includes the WebCore rendering component and the JavaScriptCore engine. WebKit is the engine that originally powered Chrome before the fork to Blink and remains tightly integrated with Apple's macOS and iOS ecosystems, though it also runs on Linux. Safari itself is primarily designed for Apple's operating systems, which use the XNU kernel (a hybrid kernel combining Mach and BSD elements), and leverages deep OS-specific integrations for performance and features.

The choice of browser engine—Blink, Gecko, or WebKit—carries significant implications for web compatibility, performance characteristics, and the evolution of web standards. While the underlying OS kernel influences low-level system interactions, such as sandboxing security models and graphics acceleration pathways, the browser engine is the decisive component for web developers and end-users in terms of how sites are displayed and function. The dominance of Chromium-based browsers (Chrome and Edge) means Blink effectively sets many de facto web standards, whereas Gecko and WebKit provide critical diversity to the ecosystem, preventing a single-engine monopoly and fostering competition in innovation. Thus, the architectural distinction between the OS kernel and the browser engine is essential for understanding both the technical stack and the broader strategic landscape of modern web browsing.