> 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/faq.md).

# FAQ

## 1. What does HTML Validator check?

It validates a **snapshot of the Current DOM** of the open Chrome page. The snapshot includes changes already made by JavaScript. Results refer to that snapshot.

## 2. What is Current DOM?

It is the HTML represented by Chrome at the time a validation starts, after any JavaScript changes that have already occurred.

## 3. Does it validate Original HTML from the server?

No. HTML Validator 2.0 FREE does not provide a separate Original HTML mode or claim to reproduce the exact HTTP response.

## 4. Do I need Chrome DevTools?

No. The main validation workflow takes place in **Chrome's Side Panel**.

## 5. What's the difference between W3C Nu and HTML Tidy?

**W3C Nu** is an external, online standards-focused validator. **HTML Tidy** performs basic local checks; it can miss conformance errors or flag valid modern HTML. Their results may differ.

## 6. Is checked HTML sent to an external service?

**Yes, when you use W3C Nu:** the checked HTML is sent to `validator.w3.org`. **HTML Tidy** performs its checks locally. Choose the engine with the page's sensitivity in mind.

## 7. Can I validate without an internet connection?

**HTML Tidy** can run locally on HTML that the extension can access. **W3C Nu** requires an internet connection and an available external validator.

## 8. How do I check a local HTML file?

Open the file in Chrome. If you see **Local file access is disabled**, enable **Allow access to file URLs** in the extension's Chrome settings, reopen the Side Panel if necessary, and retry. See [Troubleshooting](https://docs.codpeller.com/en/html-validator/troubleshooting.md).

![The Chrome local-file access permission](https://content.gitbook.com/content/Vo3wsnX9XzgpNcXIAwRg/blobs/aTLPikaW45U92VG7cQB1/images%2F14_chrome_file_permission.png)

## 9. What does Locate do?

**Locate** opens the corresponding position in the **HTML** tab's read-only validated snapshot. It does not highlight a live webpage element or edit the source code.

## 10. What does Copy do on an error?

It copies that issue's details to your clipboard. For web pages, the `Page:` field includes the origin and pathname but omits the query and fragment. For local files, it includes only the filename. Review copied details before sharing them.

## 11. What are Search HTML and Copy HTML?

On the **HTML** tab, **Search HTML…** searches within the displayed validated snapshot; **Copy HTML** copies that snapshot. Review copied markup before sending it to anyone.

## 12. Can HTML Validator automatically fix HTML?

No. It reports issues. You make changes in your editor or project and then run validation again.

## 13. What does Revalidate do?

It manually captures and checks the page again. Previously displayed results do not become current automatically after you edit or reload a page.

## 14. What does HTTP 429 mean?

The external service or an intermediary may be limiting requests. This is not proof that the HTML is invalid. Avoid repeated rapid retries and try again later; no fixed recovery time is guaranteed.

## 15. What is Copy diagnostic info?

In **About HTML Validator**, this action copies technical context such as the extension version, engine, theme, browser, and operating system. It omits the actual web address and local file path. **Copying does not automatically send a support report.**

## 16. How do I change the theme?

Open **Settings** (gear icon) and choose **System**, **Light**, or **Dark** under **Appearance**. **System** follows the operating system preference.

## 17. Can I hide warnings or change error highlighting?

Yes. **Settings → Results** contains **Show warnings** and **Highlight error lines in HTML viewer**. These settings change the display, not the page's HTML.

## 18. How can I contact support?

Open **Help & Feedback** (the **?** icon) → **Contact Support**, or email <validatorhtml@gmail.com>. Explain what happened and include safe diagnostic details if helpful. Do not send private HTML or secrets without reviewing them.

For detailed workflows see the [User Guide](https://docs.codpeller.com/en/html-validator/user-guide.md); for errors and access restrictions see [Troubleshooting](https://docs.codpeller.com/en/html-validator/troubleshooting.md).


---

# 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/faq.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.
