The W3C Nu HTML Checker is the first pick for most developers because it implements the current HTML standard and runs both online and offline. Teams that want validation inside their build should look at HTML-validate, and anyone who wants a hosted service with extra checks can use the W3C validator site or the Nu checker's web interface.
We run no ads and no affiliate links at launch. The order of a list follows our published method.
Prices are the starting prices vendors list publicly. Plans change, so confirm the current price on the vendor page before you buy.
Key takeaways
The W3C Nu HTML Checker is free and open source, and it is the reference validator for the living HTML standard.
HTML-validate is a free, open-source Node.js linter that runs locally and fits into CI pipelines.
Online validators send your markup to a third-party server, so avoid pasting secrets, tokens or production data.
The W3C validator site and the Nu checker share the same engine, so results should match.
Tool
Best for
Standout feature
Listed starting price
Free plan or trial
1 W3C Nu HTML Checker
Developers who want the reference HTML standard checker
Implements the current HTML standard
Free (open source)
Free plan
2 HTML-validate
Teams that want HTML linting in Node.js and CI
Configurable rules and shareable presets
Free (open source)
Free plan
3 W3C Markup Validation Service
Quick one-off checks of a public page or snippet
Simple web form for URL, file upload or direct input
Free
Free plan
4 HTMLHint
Developers who want a lightweight, configurable HTML linter
Small rule set that is easy to configure
Free (open source)
Free plan
5 Total Validator
Users who want HTML checks plus accessibility and link checks
Combines markup, accessibility and broken-link checks
See vendor pricing page
Free trial (30 days)
How we picked
We picked tools that actually validate HTML markup, not general linters or accessibility-only scanners. Criteria were fit for the job, supported platforms, price and licence, whether checks run locally or send data to a server, and known limits such as Java or Node.js requirements. Sources are vendor pages, official documentation and project repositories. Prices and plans change, so confirm details on the vendor site before you commit.
01
W3C Nu HTML Checker
Best for: Developers who want the reference HTML standard checker
The Nu HTML Checker is the validator maintained by the W3C. It checks documents against the living HTML standard and reports errors and warnings with line and column numbers. You can use it through the web interface at validator.w3.org/nu/, as a REST API, or as a standalone Java jar for offline and batch use.
Because it is the reference implementation, its results are what most other tools compare against. The jar runs on any system with a Java runtime, which makes it usable in CI. The main drawback is that it has no project-level configuration for ignoring specific rules, so teams often wrap it in scripts. Developers who need rule configuration should pair it with a linter.
Pros
Implements the current HTML standard
available as a web service and a command-line jar
Cons
Command-line output is verbose
no built-in project config file
Price: Free (open source), as listed by the vendor (W3C Nu HTML Checker website). Confirm the current plan price before you buy.
Skip it if this limit matters to you: command-line output is verbose.
Verdict. A sensible pick for developers who want the reference HTML standard checker.
02
HTML-validate
Best for: Teams that want HTML linting in Node.js and CI
HTML-validate is an open-source linter for HTML written in JavaScript. It ships as an npm package and can run from the command line, in a Node.js script or through editor integrations. It offers a set of recommended rules plus style presets, and you can turn rules on or off in a config file.
It is a good fit for projects that already use Node.js tooling. Because it runs locally, your markup does not leave your machine. It is not the W3C engine, so a few edge-case results may differ from the Nu checker. Teams that need strict conformance to the standard should run both.
Pros
Configurable rules and shareable presets
runs locally and in CI
Cons
Requires Node.js
not the official W3C engine
Price: Free (open source), as listed by the vendor (HTML-validate website). Confirm the current plan price before you buy.
Skip it if this limit matters to you: requires Node.js.
Verdict. A sensible pick for teams that want HTML linting in Node.js and CI.
03
W3C Markup Validation Service
Best for: Quick one-off checks of a public page or snippet
The W3C Markup Validation Service is the long-running web front end for checking HTML. You can validate by URL, upload a file or paste markup directly. It reports errors with line numbers and links to the relevant part of the specification.
It is best for quick checks and for validating pages that are already public. Because you submit markup to a third-party server, do not paste secrets, tokens or private production data. The service asks heavy users to run their own instance or use the Nu checker API instead of hammering the shared endpoint.
Pros
Simple web form for URL, file upload or direct input
Skip it if this limit matters to you: sends submitted markup to W3C servers.
Verdict. A sensible pick for quick one-off checks of a public page or snippet.
04
HTMLHint
Best for: Developers who want a lightweight, configurable HTML linter
HTMLHint is an open-source static analysis tool for HTML. It runs as a command-line tool and through editor plugins, and it reads a configuration file so you can choose which rules apply. Rules cover common issues such as missing alt text, duplicate IDs and unclosed tags.
It is lightweight and quick to set up, which suits small projects and teams that want a short rule list. The rule set is smaller than some alternatives, and the project's release cadence has slowed, so check that it covers the checks you need before adopting it.
Pros
Small rule set that is easy to configure
CLI and editor integrations
Cons
Fewer rules than some linters
project activity has slowed
Price: Free (open source), as listed by the vendor (HTMLHint website). Confirm the current plan price before you buy.
Skip it if this limit matters to you: fewer rules than some linters.
Verdict. A sensible pick for developers who want a lightweight, configurable HTML linter.
05
Total Validator
Best for: Users who want HTML checks plus accessibility and link checks
Total Validator is a desktop application and command-line tool that checks HTML markup along with accessibility and broken links. It runs on Windows, and there are builds for other platforms. It reports issues in a single pass, which can save time when you want several kinds of check at once.
The tool is commercial. A free trial is available, and continued use requires a licence; check the vendor pricing page for current terms. It suits teams that want an all-in-one checker rather than separate tools. Developers who only need standard conformance can use the free W3C checker instead.
Pros
Combines markup, accessibility and broken-link checks
desktop app and CLI
Cons
Paid licence after the trial
desktop app is Windows-focused
Price: See vendor pricing page, as listed by the vendor (Total Validator website). Confirm the current plan price before you buy.
Skip it if this limit matters to you: paid licence after the trial.
Verdict. A sensible pick for users who want HTML checks plus accessibility and link checks.
Who should use what
If you want the reference check against the HTML standard, use the W3C Nu HTML Checker, either online or as a jar. If your project uses Node.js and you want configurable rules in CI, use HTML-validate. If you need a quick check of a public page, the W3C Markup Validation Service is the simplest option. If you want markup, accessibility and link checks in one pass, look at Total Validator and confirm the licence terms first.
What to check before you buy
Confirm the tool checks against the current HTML standard, not an outdated version.
Check whether validation runs locally or sends markup to a third-party server.
Verify the runtime requirements, such as Java, Node.js or Docker.
Confirm the tool can run in your CI pipeline and return a non-zero exit code on errors.
Review the licence and pricing terms, including any limits on free use.
FAQ
Is the W3C validator still maintained?
Yes. The Nu HTML Checker is maintained by the W3C and tracks the living HTML standard. The older Markup Validation Service remains available, but the Nu checker is the current reference engine.
Can I validate HTML offline?
Yes. The Nu HTML Checker jar and the official Docker image run locally without sending markup to a server. HTML-validate and HTMLHint also run locally. This is the safer choice for private or unreleased markup.
Do online validators store my HTML?
Policies vary by service. Treat any online validator as a third-party service and avoid pasting secrets, tokens or production data. Prefer local tools when the markup is sensitive.
What is the difference between a validator and a linter?
A validator checks conformance to the HTML standard. A linter applies style and best-practice rules that you configure. Some tools, such as HTML-validate, do both, but the two jobs are not the same.
Do I need Java to run the Nu checker?
The standalone jar and the npm wrapper require a Java runtime. The Docker image avoids installing Java on the host. The web interface needs only a browser.