Spectral is the first pick for most teams. It is an open-source CLI and library that lints OpenAPI and AsyncAPI documents against built-in and custom rulesets, and it runs locally or in CI. Redocly CLI is a strong alternative when you want linting plus bundling and docs in one tool, and openapi-generator-validate (part of OpenAPI Generator) suits teams that already use OpenAPI Generator and want a validation step.
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
Spectral is free and open source, runs on Node.js, and supports custom rulesets for OpenAPI 2, 3.0 and 3.1.
Redocly CLI bundles linting, bundling and preview, with a free tier and paid plans; confirm current limits on the vendor pricing page.
Most linters run locally or in CI, so specs and tokens stay on your machine; avoid pasting private specs into third-party web validators.
Tool
Best for
Standout feature
Listed starting price
Free plan or trial
1 Spectral
Teams that want a configurable, CI-friendly OpenAPI linter
Custom rulesets and built-in OpenAPI rules
Free (open source)
Free plan
2 Redocly CLI
Teams that want linting plus bundling and docs preview
Lint, bundle and preview in one CLI
See vendor pricing page
Free trial (N days)
3 OpenAPI Generator (validate)
Teams already using OpenAPI Generator in their build
Validate command checks specs before generation
Free (open source)
Free plan
4 Vacuum
Fast OpenAPI linting with a Go binary and custom rules
Single binary, no Node.js needed
Free (open source)
Free plan
5 openapi-spec-validator
Python teams that want schema validation in code or CI
Pure Python, easy to call from tests
Free (open source)
Free plan
6 oasdiff
Catching breaking changes between OpenAPI versions
Detects breaking changes between spec versions
Free (open source)
Free plan
How we picked
We picked tools that genuinely lint or validate OpenAPI or Swagger documents and are currently maintained. Criteria were fit for the job, supported platforms and runtimes, price and licence, whether specs stay local, and main limits such as schema-only validation or a single-binary design. Sources are vendor pages, documentation and project repositories. Prices and plan limits change, so confirm them on the vendor site before you commit.
01
Spectral
Best for: Teams that want a configurable, CI-friendly OpenAPI linter
Spectral is an open-source linter from Stoplight that checks JSON and YAML documents, including OpenAPI 2, 3.0 and 3.1 and AsyncAPI. It ships with an OpenAPI ruleset and lets you write custom rules in JavaScript or as functions. You run it with the CLI, as a Node.js library, or through editor integrations. Output formats include JSON, YAML and stylish text, which makes it easy to wire into CI.
Because it runs locally, your spec does not leave your machine. The main cost is setup: you need Node.js and a ruleset file, and custom rules take some practice. It does not host docs or mock servers, so teams that want an all-in-one platform should look at Redocly or Stoplight's hosted product. For pure linting, Spectral is the most common open-source choice.
Pros
Custom rulesets and built-in OpenAPI rules
runs locally, in CI and as a library
Cons
Requires Node.js
rule authoring has a learning curve
Price: Free (open source), as listed by the vendor (Spectral 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 a configurable, CI-friendly OpenAPI linter.
02
Redocly CLI
Best for: Teams that want linting plus bundling and docs preview
Redocly CLI is an open-source command-line tool that lints OpenAPI documents, bundles multi-file specs, and can preview docs. It uses a configuration file to enable, disable or adjust rules, and it supports OpenAPI 3.0 and 3.1. The CLI runs on Node.js and works in CI. It is part of the Redocly ecosystem, which also offers hosted docs and a paid platform.
The CLI itself is open source, but some related features and hosted services are commercial, so check the vendor pricing page for current plans and limits. It is a good fit if you already use Redocly for docs or want one tool for lint and bundle. If you only need linting and want minimal dependencies, Spectral may be simpler.
Pros
Lint, bundle and preview in one CLI
configurable rules and extends
Cons
Some features tie into Redocly's paid platform
pricing needs checking
Price: See vendor pricing page, as listed by the vendor (Redocly CLI website). Confirm the current plan price before you buy.
Skip it if this limit matters to you: some features tie into Redocly's paid platform.
Verdict. A sensible pick for teams that want linting plus bundling and docs preview.
03
OpenAPI Generator (validate)
Best for: Teams already using OpenAPI Generator in their build
OpenAPI Generator is an open-source project that generates client SDKs, server stubs and docs from OpenAPI specs. It includes a `validate` command that checks a spec for structural problems before generation. If your build already runs the generator, adding validation is a small step. It supports OpenAPI 2 and 3.x and runs on the JVM.
The validator is not a full linting ruleset engine like Spectral. It focuses on whether the spec can be processed for generation, not on style or naming conventions. It also requires Java, which may be a burden for Node- or Python-only teams. Use it as a pre-generation gate, and pair it with a dedicated linter if you need style rules.
Skip it if this limit matters to you: validation is a smaller part of a large tool.
Verdict. A sensible pick for teams already using OpenAPI Generator in their build.
04
Vacuum
Best for: Fast OpenAPI linting with a Go binary and custom rules
Vacuum is an open-source OpenAPI linter written in Go. It ships as a single binary, so you can run it without Node.js or a JVM. It includes built-in rules, supports custom rules, and can output results in several formats for CI. It targets OpenAPI 3.x and aims for speed on large specs.
Because it is a single binary, it fits well into minimal CI images and container builds. The trade-off is a smaller ecosystem and a rule syntax that differs from Spectral, so teams migrating need to rewrite custom rules. It is a good choice when you want fast linting without a Node.js toolchain.
Pros
Single binary, no Node.js needed
custom rules and multiple output formats
Cons
Smaller community than Spectral
rule syntax differs from Spectral
Price: Free (open source), as listed by the vendor (Vacuum website). Confirm the current plan price before you buy.
Skip it if this limit matters to you: smaller community than Spectral.
Verdict. A sensible pick for fast OpenAPI linting with a Go binary and custom rules.
05
openapi-spec-validator
Best for: Python teams that want schema validation in code or CI
openapi-spec-validator is an open-source Python library and CLI that validates OpenAPI 2.0 and 3.x documents against the official schema. You can call it from Python tests or run it as a command. It is useful when your stack is Python and you want a validation step without adding Node.js or Java.
It checks structure, not style or naming conventions. If you need custom rules, use a linter like Spectral alongside it. It is maintained under the python-openapi organization. For Python teams that want a lightweight gate in pytest or CI, it is a practical fit.
Pros
Pure Python, easy to call from tests
validates against the OpenAPI schema
Cons
Schema validation only, not style linting
Python dependency
Price: Free (open source), as listed by the vendor (openapi-spec-validator website). Confirm the current plan price before you buy.
Skip it if this limit matters to you: schema validation only, not style linting.
Verdict. A sensible pick for python teams that want schema validation in code or CI.
06
oasdiff
Best for: Catching breaking changes between OpenAPI versions
oasdiff is an open-source tool that compares two OpenAPI specs and reports breaking changes. It is written in Go and runs as a CLI. It complements a linter: linting checks one spec for problems, while oasdiff checks whether a change breaks compatibility. It supports OpenAPI 3.x.
It is not a replacement for a linter and does not enforce style rules. It is most useful in CI when you want to block breaking API changes before merge. Teams that only need single-spec validation can skip it.
Pros
Detects breaking changes between spec versions
CLI and CI friendly
Cons
Focused on diffing, not full linting
needs two specs to compare
Price: Free (open source), as listed by the vendor (oasdiff website). Confirm the current plan price before you buy.
Skip it if this limit matters to you: focused on diffing, not full linting.
Verdict. A sensible pick for catching breaking changes between OpenAPI versions.
Who should use what
If you want a configurable linter for CI and are comfortable with Node.js, start with Spectral. If you already use Redocly for docs and want lint plus bundle in one CLI, choose Redocly CLI. If your build already runs OpenAPI Generator, add its validate command as a pre-generation gate. Python teams that want validation inside pytest should use openapi-spec-validator. Teams that need to block breaking changes between releases should add oasdiff alongside a linter.
What to check before you buy
Confirm the tool supports your OpenAPI version, including 3.1 if you use it.
Check the runtime: Node.js, JVM, Go binary or Python.
Decide whether you need style rules, schema validation or breaking-change detection.
Verify how custom rules are written and whether they fit your team's skills.
Keep private specs local or self-hosted; do not paste them into third-party web validators.
FAQ
What is an OpenAPI linter?
An OpenAPI linter checks an OpenAPI or Swagger document for structural errors and style problems. It applies rules to fields, naming, descriptions and references, then reports warnings and errors. Some tools only validate against the schema, while others support custom rulesets for team conventions.
Is Spectral free?
Yes. Spectral is open source and free to use. You need Node.js to run it. Stoplight also offers a hosted platform with paid plans, but the CLI and library are free.
Can I lint OpenAPI 3.1?
Support varies. Spectral supports OpenAPI 3.1, and Redocly CLI supports 3.0 and 3.1. Check each tool's documentation for the exact versions covered before you rely on it.
Are online OpenAPI validators safe for private specs?
Treat them with care. A public web validator receives your spec, which may include internal URLs or tokens. Prefer tools that run locally or can be self-hosted, and remove secrets before pasting anything into a third-party page.
Do I need a linter if I already validate my spec?
Validation catches structural errors, but a linter can also enforce naming, descriptions and team conventions. Many teams run both: schema validation for correctness and a linter for style and consistency.