WHATWG

Definition

WHATWG (Web Hypertext Application Technology Working Group) is a community of browser vendors and contributors that maintains the HTML and DOM Living Standards, continuously updated specifications that describe how browsers should parse and render web content. It was formed by engineers from major browser makers who felt that W3C's process at the time was moving too slowly to keep pace with practical web platform needs.

Overview

WHATWG began when engineers from browser vendors grew frustrated that the W3C's standards process of the mid-2000s was pursuing a different direction for the future of web markup than what browsers were actually shipping and what web developers needed, so they started an independent effort to document HTML as browsers actually implemented and evolved it. That grassroots origin shaped the organization's defining characteristic: rather than versioned specifications released periodically, WHATWG maintains its standards as continuously updated "living standards" that change whenever browser vendors agree a change reflects reality or improves the platform. Mechanically, WHATWG's specifications are edited collaboratively on public repositories where anyone can propose changes, and adoption of a change typically requires signals of implementer interest from the major browser engines before it is merged into the living standard. This differs fundamentally from a staged, versioned recommendation process; there is no "HTML5.1" or "HTML6" milestone in WHATWG's model, only a single continuously evolving HTML Standard. The DOM Standard, Fetch Standard, and URL Standard follow the same continuous-update model, each maintained as the canonical source that browser implementers reference directly. For years, W3C and WHATWG published competing HTML specifications, creating confusion about which document was authoritative, until the two organizations formalized an agreement under which WHATWG's living standards are the single canonical source for HTML and DOM, with W3C publishing periodic snapshots aligned to them rather than independent competing text. This resolved a long-standing tension between a fast-moving, implementer-driven process and a formal multi-stakeholder standards body. In practice, browser engineers, spec authors, and toolmakers treat the WHATWG HTML Standard as the authoritative reference for parsing algorithms, element behavior, and DOM APIs, since it reflects what shipping browsers actually do rather than an idealized or aspirational design. Web developers rarely read the living standard directly but benefit from its precision whenever a browser inconsistency gets resolved by referring back to the spec's exact parsing algorithm. The living-standard model's responsiveness comes at the cost of stable version numbers that developers or documentation can cite precisely, since the specification has no discrete releases to point to, which can make it harder to communicate exactly which browser behaviors were guaranteed at a given point in time compared to a versioned standard. Because anyone can propose a change, the practical authority of the living standard still rests on whether major browser engines actually agree to implement it, meaning WHATWG's process depends heavily on ongoing cooperation between competing vendors rather than a single governing authority forcing consensus.

Key Concepts

• Maintains HTML, DOM, Fetch, and URL as continuously updated living standards
• Founded by browser vendor engineers dissatisfied with an earlier W3C process
• Changes require signals of implementer interest from major browser engines
• Specifications edited collaboratively in public, version-control-based repositories
• Now the canonical source W3C's HTML recommendations are aligned to
• No discrete version releases, unlike traditional numbered specifications
• Documents exact parsing algorithms used to resolve browser inconsistencies

Use Cases

Frequently Asked Questions

Related in Programming