What Does Multi-Process Mean in a Web Browser?

Multi-process means the browser runs different parts of itself — the interface, individual tabs, and sometimes plugins — in separate operating-system processes instead of one. The practical payoff is isolation: if one tab crashes or hangs, the rest of the browser usually keeps running. The trade-off is higher memory use, because each process carries its own overhead. You can see this directly in Task Manager or Activity Monitor, where a multi-process browser appears as many entries rather than one.

How the architecture is split

In a multi-process browser, the work is divided into roles:

• Browser (parent) process — draws the window, menus, and address bar, and coordinates everything else.
• Renderer processes — one or more per tab or site, handling page layout, JavaScript, and rendering.
• Plugin/GPU processes — separate processes for plugin content and for graphics compositing.

Each renderer is sandboxed from the others and from the parent process, so a fault in one is contained rather than spreading.

Why browsers moved to multi-process

The single-process model put every tab, plugin, and the UI into one address space. One bad page could freeze or crash the entire browser, and a malicious page had a wider reach.

Multi-process addresses that with three mechanisms:

• Stability — a crashed renderer takes down only its own tab. The browser can show a "page crashed" state and let you reload it.
• Security — sandboxing limits what a compromised renderer can touch on your system.
• Responsiveness — a heavy page in one tab is less likely to block input or rendering in another.

The memory trade-off

Isolation is not free. Every process has fixed overhead — its own memory space, runtime, and bookkeeping — so the same set of pages generally consumes more total RAM under multi-process than under single-process.

Browsers mitigate this by limiting how many renderer processes run at once and by sharing processes across tabs from the same site, so the count does not grow one-to-one with open tabs.

What you can observe yourself

Open several tabs, then check your system's process list:

• Windows — Task Manager (Ctrl+Shift+Esc), Details or Processes tab.
• macOS — Activity Monitor, filter by the browser's name.

You will see a parent process plus multiple child processes, often labeled by tab or site. Close a tab and its process typically disappears; crash one tab and the others remain. That behavior is the clearest everyday evidence of the multi-process design.

Where Avant Browser fits

Avant Browser is described as a tri-core browser supporting the IE, Firefox, and Chrome engines, and its own materials list "multi-process" among its features alongside claims of being fast, stable, and memory-leak free. In other words, multi-process here is presented as one property among several — engine choice and memory behavior are separate concerns. If you are evaluating it, treat the multi-process label as a statement about tab isolation and stability, and judge memory use on your own machine rather than assuming isolation comes without cost.