renderer process
The sandboxed process that turns one tab's HTML, CSS and JavaScript into pixels and runs the page's scripts.
In more detail
Each tab, and often each site, gets its own renderer process so pages are isolated from one another. Inside it the main thread parses HTML, runs JavaScript and computes styles and layout, while helper threads handle compositing. Because it is sandboxed, a renderer cannot touch your disk or other sites directly.
Related terms
- browser process — The main browser process that owns the address bar, tabs, disk storage and network access, and coordinates all the other processes.
- sandbox — A locked-down environment in which a program runs with very few permissions, so that damage from a bug or attack stays contained.
- main thread — The first thread a program starts with; in a browser page it also runs JavaScript and handles input, layout and painting.
- multi-process browser architecture — The design in which a browser runs its tabs, extensions and networking in separate operating system processes instead of one big program.
Taught in
- How Browsers Work: Navigation, DNS, TCP, TLS And Request Timing — Frontend Architecture & Web Platform
- HTML Parsing, Tokenization And The Document Object Model (DOM) — Frontend Architecture & Web Platform
- CSS Parsing, The CSSOM And The Render Tree — Frontend Architecture & Web Platform