V8 in one sentence

V8 is the open-source JavaScript and WebAssembly engine built by Google. It reads the text of a script and turns it into machine code the CPU can execute, and it does that quickly enough that most people never notice the translation happening. If you have used Chrome, Edge, Node.js, or Deno, you have already run V8.

v1

Why it is called V8

The name is a nod to the eight-cylinder car engine. The team wanted something that suggested power and speed, and a big motor was the obvious reference. There is no acronym behind it. V8 is just a name, which is why you will also see it written as v8 in version strings.

v2

How V8 runs your code

V8 does not read a script once and hope for the best. It watches how the code behaves and changes strategy as it learns.

v3

1. The parser turns source text into an abstract syntax tree, then into bytecode.
2. Ignition, the interpreter, starts executing that bytecode right away so work begins without a long wait.
3. Sparkplug and Maglev compile hot functions to machine code without heavy optimization, which is a middle step between interpreting and full tuning.
4. Turbofan watches functions that run often and recompiles them with aggressive optimizations based on the types and object shapes it has actually seen.

Objects get hidden classes under the hood, and property reads get inline caches. When your objects keep a stable shape, those caches stay fast. When shapes change constantly, V8 throws away its assumptions and falls back to slower paths.

v2

Where you meet V8

• Chrome and other Chromium-based browsers, including Edge, Brave, and Opera.
• Node.js, Deno, and Electron, all of which pair V8 with their own APIs for files, networking, and timers.
• Edge platforms such as Cloudflare Workers, which pack many isolated V8 instances into a single process.
• Mobile and desktop apps that embed the engine to script their own internals.

What V8 is not

V8 has no file system, no network stack, and no timer functions on its own. It runs JavaScript and WebAssembly and nothing else. Node.js and Deno are the ones that hand it those extras. V8 is also not the same thing as the language standard. The ECMAScript spec defines what JavaScript must do, and V8 is one implementation of that spec, alongside JavaScriptCore in Safari and SpiderMonkey in Firefox.

Version numbers and release pace

V8 publishes a new major version about every four weeks, timed to land in a matching Chrome milestone. The version shows up in a browser's user agent data and in the v8 property of process.versions in Node.js. That steady cadence is why a feature can exist in the latest V8 before your browser or your server runtime picks it up.

What this means if you write JavaScript

The practical advice is dull but useful. Keep object shapes consistent, do not add and delete properties inside hot loops, and avoid passing wildly different types into the same function. Modern V8 handles a lot of messy code well, so the bigger wins usually come from removing wasted work rather than from outsmarting the optimizer. Profile first, then optimize what the profile points at.