> For the complete documentation index, see [llms.txt](https://docs.codpeller.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codpeller.com/en/html-validator/overview.md).

# Overview

HTML Validator 2.0 FREE is a Google Chrome extension for checking the HTML of an open webpage without leaving the browser. It runs in **Chrome's Side Panel** and helps you review validation messages, inspect the HTML that was checked, and run a new validation after making changes.

## Who is it for?

HTML Validator is intended for developers, website maintainers, testers, and anyone who needs to investigate HTML markup. You can use it while reviewing a live page or an HTML file opened from your computer.

## What you can do

* Check the **Current DOM** — the HTML represented by Chrome at the moment of validation, including changes made by JavaScript.
* Select **W3C Nu** for online, standards-focused validation, or **HTML Tidy** for basic local/offline checks.
* Review **Results** with errors, warnings, and line/column information when available.
* Use **Locate** to see an issue in the read-only **HTML** viewer, or **Copy** to copy one issue's details.
* **Search HTML**, **Copy HTML**, and run **Revalidate** after changing the page.
* Check local HTML files when Chrome grants the extension file URL access.
* Customize the default engine, warning display, error-line highlighting, and **System / Light / Dark** appearance.

![Chrome Side Panel with Current DOM and W3C Nu selected](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/fODLusbtgZ6Fu4V1hTDL/images%2F02_sidepanel_validate.png)

## Current DOM: what is actually checked?

HTML Validator captures a **snapshot** of the page's current DOM when you start validation. Scripts may have changed the page since it first loaded. Consequently, the validated HTML can differ from the original HTML response sent by the server. **The extension does not offer a separate Original HTML validation mode.**

Results and line numbers refer to the captured HTML, not necessarily to the file you edit in your development environment.

## Two validation engines

| Engine        | How it works                                                           | What to know                                                                                              |
| ------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| **W3C Nu**    | Sends the checked HTML to the external validator at `validator.w3.org` | Requires an internet connection; use it only when external processing of the page content is appropriate. |
| **HTML Tidy** | Performs basic checks locally in the extension                         | Can miss HTML conformance problems or flag valid modern HTML; it is not equivalent to W3C Nu.             |

![HTML Tidy with the built-in limitation notice](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/EGfTIqPrZBdlrcgAHXRC/images%2F03_html_tidy.png)

## How to begin

1. Open the [HTML Validator listing in Chrome Web Store](https://chromewebstore.google.com/detail/hkiecfigipbfbmkbpjhmejjhiffdgmok) and check the version offered there.
2. Once HTML Validator 2.0 is installed, pin it in Chrome's **Extensions** menu.
3. Open a webpage, click the extension icon, and select **Current DOM** and a validation engine.
4. Click **Validate HTML**, then review the **Results** tab.

Continue with [Getting Started](https://docs.codpeller.com/en/html-validator/getting-started.md) for the full illustrated walkthrough and [User Guide](https://docs.codpeller.com/en/html-validator/user-guide.md) for every setting and workflow.

## Important limits

* HTML Validator **reports** HTML problems; it does not automatically repair your page.
* **Locate** opens the corresponding location in the validated snapshot inside the **HTML** tab. It does not select or highlight a live element on the webpage.
* **Revalidate** is a manual new check. Previous results do not update themselves when a webpage changes.
* Chrome controls access to local files and certain browser pages; not every tab can be inspected.
* W3C Nu can be unavailable or return HTTP errors independently of the validity of your HTML.

## Official links and support

* [Product website](https://html-validator.codpeller.com/)
* [Chrome Web Store listing](https://chromewebstore.google.com/detail/hkiecfigipbfbmkbpjhmejjhiffdgmok)
* [Privacy Policy](https://html-validator.codpeller.com/privacy.html)
* Support: <validatorhtml@gmail.com>

For specific problems, read [Troubleshooting](https://docs.codpeller.com/en/html-validator/troubleshooting.md) or [FAQ](https://docs.codpeller.com/en/html-validator/faq.md). Copying diagnostics or an error only saves the text to your clipboard; **nothing is sent to support automatically**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.codpeller.com/en/html-validator/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
