HTML Living Standard

Living Standard

HTML is maintained as a living standard, not a finished version.

In older tutorials you will often see the term HTML5. That name is still used casually to mean modern HTML, but it is not the best way to think about HTML today. The current standard is maintained as the HTML Living Standard. That means the specification is continuously maintained instead of being frozen as one final version.

This matters because the web platform does not stop. Browsers change, new APIs appear, old patterns become obsolete and developer best practices improve. A living standard tries to describe the web as it is meant to work now, not as a snapshot from years ago.

HTML5 versus modern HTML

HTML5 was a milestone. The Living Standard is the ongoing track.

HTML5 was important because it moved the web forward with better semantics, media elements, form improvements and application features. But developers should not treat HTML5 as the final destination. Modern HTML is not a fixed box called HTML5. It is an evolving platform.

Who maintains HTML

WHATWG maintains the HTML Standard with W3C collaboration.

The HTML Standard is maintained by the Web Hypertext Application Technology Working Group, usually called WHATWG. In 2019, W3C and WHATWG agreed to collaborate on a single version of HTML and DOM. In practice, that means developers should look at the WHATWG HTML Standard as the main living source, while W3C participates through the agreed process.

You do not need to read the full specification every day. But you should know where the source of truth lives. When tutorials disagree, or when a tag, attribute or browser behavior seems unclear, the standard and MDN are stronger references than random blog posts.

Browser reality

A standard is not the same as instant browser support.

The standard describes how HTML should work, but browsers implement features over time. A feature can be in a specification before every browser supports it. A feature can also have edge cases, experimental flags or partial support. That is why professional developers check both the standard and browser compatibility.

For daily work, this gives you a practical rule: write clean, standard HTML first, then verify browser support for newer or less common features. Do not guess. Check.

// Practical developer flow
1. Write semantic HTML
2. Check MDN examples and compatibility
3. Validate important pages
4. Test in real browsers

Conformance

The standard separates valid authoring from browser recovery.

Browsers are very forgiving. If you write broken HTML, the browser will often still show something. That does not mean the HTML is good. The standard describes rules for authors and rules for user agents such as browsers. Browsers need recovery behavior because the web contains decades of imperfect pages.

As an author, your goal is not “the browser renders something”. Your goal is clean, valid, maintainable markup. That gives better accessibility, SEO, testing and long-term reliability.

Obsolete features

Old HTML can still render, but that does not make it modern.

The web keeps old behavior alive because breaking old websites would break the internet. That is why browsers can still understand many outdated patterns. But new code should avoid obsolete or presentational HTML. Use CSS for styling, semantic elements for structure and modern attributes for behavior.

How developers use this

You do not memorize the standard. You learn how to consult it.

The HTML Standard is huge because it defines how browsers, parsers, APIs, elements and edge cases work. You do not need to read it from start to finish as a beginner. You should understand that it exists, know what kind of questions it answers, and learn to use developer-friendly references first.

Version myths

Do not wait for “HTML6”. Learn modern HTML as it evolves.

Beginners sometimes ask what HTML version they should learn. The practical answer is: learn modern HTML. Use the current doctype, semantic elements, accessible forms, good metadata, responsive images where needed, and validation. The web does not require you to declare “HTML5” as a version in your page.

<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>Modern HTML document</title>
  </head>
</html>

Checklist

Use this checklist when deciding whether HTML guidance is trustworthy.

Next step

Now that the standard model is clear, move into actual authoring.

The next lesson is about editors. After that, the course moves into basic HTML and then the element system. Keep the Living Standard idea in the back of your mind: you are learning a platform that keeps evolving.