The HTML Living Standard: Continuous Evolution, Not Versions

HTML 4.01, finalized in 1999, was followed by a long gap before 'HTML5' began circulating as a term in the mid-2000s. But unlike a software release with a clear ship date, HTML5's individual features — semantic elements, <canvas>, native video and audio, form input types — were implemented by different browsers at wildly different times over roughly a decade.

There was never a single date when 'HTML5 was complete' in any browser. This made the traditional versioned-specification model, which implies a discrete before/after boundary, a poor match for how browsers actually evolve: incrementally, feature by feature, on independent timelines.

WHATWG's HTML Living Standard replaces version numbers entirely with a single, continuously-updated specification document. When browser vendors reach consensus on a new feature or a clarifying change to existing behavior, it's incorporated into the document directly — there's no scheduled release, no waiting for a numbered version, no 'HTML6' to anticipate.

This means the specification you read today may differ in small ways from what you'd have read a year ago, reflecting genuine, ongoing refinement — checking the document's own change history or dated snapshots is the correct way to track what's changed, rather than looking for a version number.

Despite this technical shift, 'HTML5' remains extremely common in everyday developer conversation, job postings, and documentation — used colloquially to mean roughly 'the modern web platform capabilities that emerged from the mid-2000s onward', encompassing semantic elements, native multimedia, canvas graphics, and the broader shift away from Flash and other plugin-based approaches.

It's useful to recognize this as informal shorthand rather than a technically precise reference: there is no formally maintained 'HTML5' specification document anymore, and the actual current, authoritative reference for any HTML feature — old or new — is the WHATWG HTML Living Standard covered in the previous lesson.

There Is No 'HTML6'. Unlike CSS levels or ECMAScript editions, HTML has no discrete version number anymore. The 'Living Standard' model treats HTML as a single, continuously-updated document — a deliberate response to how mismatched versioned releases were with the reality of how browsers actually ship features.

Versioned Releases Didn't Match Browser Reality. Traditional spec versioning (HTML 4.01, then eventually 'HTML5') implies a discrete before/after moment. But in practice, browsers implement individual features incrementally and continuously — no single browser ever fully supported all of 'HTML5' on the exact day it was finalized.

Why Versioning Broke Down. Why did discrete version numbers like 'HTML5' poorly match how browsers actually implement HTML features?

• →There was no real mismatch; versions matched implementation perfectly
• →Browsers ship individual features incrementally and continuously, not as one discrete version-complete moment
• →Version numbers were purely a marketing concern with no technical basis

The Living Standard Updates Continuously. Instead of periodic major version releases, the HTML Living Standard is updated on an ongoing basis as new features reach consensus and existing sections are clarified — there's no 'HTML5.1' or 'HTML6' to wait for; the single document simply reflects the current state at any given moment.

Living Standard Update Model. If a new HTML element reaches consensus among browser vendors, when does it get added to the specification?

• →Only when the next major numbered version is officially released
• →As soon as it reaches consensus, updated continuously in the living document
• →Only during a scheduled annual release cycle

What 'HTML5' Still Means Colloquially. Despite the technical shift away from versioning, 'HTML5' persists colloquially as shorthand for 'the modern web platform capabilities that emerged starting around the mid-2000s' — semantic elements, native multimedia, canvas, and more — even though there's no longer a formal HTML5 specification document.

The Colloquial 'HTML5'. Is there currently a formally maintained specification document called 'HTML5'?

• →Yes, it's actively maintained as a separate document from the Living Standard
• →No, it's now colloquial shorthand; the actual spec is the HTML Living Standard
• →Yes, but it was frozen and never updated since 2014

Living Standard Model Understood. You now understand why HTML abandoned discrete version numbers for a continuously-updated Living Standard model, and how 'HTML5' persists as useful colloquial shorthand despite no longer being a formally maintained specification document.

Use A Modern Living-Standard Element. <dialog> is part of the actively evolving WHATWG HTML Living Standard, not a fixed old spec.