Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Vale

vale.sh

  • Free plan
  • Windows
  • macOS
  • Linux
  • Web
  • Self-hosted
8.0 Club score Visit vale.sh

What Vale is

Vale is an open-source command-line linter that checks prose against style-guide rules. It runs offline as a single binary, without an account, server, or model. It supports formats including Markdown, AsciiDoc, reStructuredText, MDX, MyST, Quarto, Typst, HTML, XML, DITA, Org, and QDoc, and can extract and check comments in 19 programming languages. Vale Views can select prose in OpenAPI, Jupyter notebooks, commit messages, transcripts, docstrings, JSON, YAML, and TOML. Users can write custom rules in YAML and choose which rules and styles apply to files. Ready-made style packages include Google, Microsoft, Red Hat, readability, and Harper grammar styles. Editor integrations include VS Code, Cursor, Windsurf, Neovim, Sublime Text, Zed, Emacs, JetBrains IDEs, Obsidian, Oxygen XML, and Qt Creator. Vale can run in GitHub Actions or as a pre-commit hook. Its language server offers autocomplete, diagnostics, hover popups, and quick fixes. In CI, only error-level alerts return a non-zero exit code; warnings and suggestions pass. The free plan is MIT-licensed; paid plans start at $19/user/mo.

Who it suits

Vale suits people and teams that want style-guide checks in their editors and alongside code, including documentation teams. It can also suit teams that want checks in GitHub Actions or pre-commit workflows.

Good to know, and what to watch

  • Runs offline without an account, server, or model.
  • Supports custom YAML rules and ready-made style packages.
  • Language server provides diagnostics and quick fixes.
  • Can run in GitHub Actions and as a pre-commit hook.
  • Warnings and suggestions do not fail CI.
  • Questions and support are directed to GitHub issues or Discord.

Vale

Free

Free plan · paid from $19/user/mo

Getting started

  1. Open https://vale.sh/
  2. Install Vale for Linux, macOS, Windows, or use the self-hosted option
  3. Choose an editor integration or run Vale as a command-line tool
  4. Add or select style rules and configure them in YAML
  5. Connect checks to GitHub Actions, a pre-commit hook, or an LSP editor

Limits to check

The free plan is MIT-licensed and open-source. In CI, warnings and suggestions do not produce a non-zero exit code; only error-level alerts do.

The Club's review

Overview

Vale is an open-source command-line linter that applies style-guide rules to prose. It is best suited to writers, documentation teams, and developers who need the same editorial standards in source files and editors. Its rule-driven, offline design favors consistency and control over the broader rewriting assistance of hosted writing apps.

Founded in 2017, Vale runs as a single binary without an account, server, or language model. You decide which rules and styles apply to each file, making it a practical choice for organizations with a house style or terminology policy. It is less suitable if you want an immediately polished, consumer-facing writing assistant with minimal configuration.

For a wider comparison, see our Writing Style Checkers list.

Key features

Checks across documents and code

Vale handles Markdown, AsciiDoc, reStructuredText, MDX, MyST, Quarto, Typst, HTML, XML, DITA, Org, and QDoc. It can extract comments from 19 programming languages, including Go, Rust, Python, JavaScript, TypeScript, and Java. That makes editorial checks relevant to documentation repositories and source code, not only finished articles.

Vale Views select prose inside OpenAPI documents, Jupyter notebooks, commit messages, transcripts, docstrings, JSON, YAML, and TOML. This coverage is valuable when important wording is embedded in structured files, although teams must configure the selections and rules to avoid checking the wrong content.

Rules and style packages

Rules are written in YAML, and configurations determine which rules and styles apply to files. Ready-made packages include Google, Microsoft, Red Hat, readability, and Harper grammar styles. Custom style guides, terminology management, and brand-voice rules let teams turn internal guidance into enforceable checks. The trade-off is ongoing rule maintenance: Vale delivers a framework for standards, not a finished house style for every organization.

Editors and automation

Listed integrations cover VS Code, Cursor, Windsurf, Neovim, Sublime Text, Zed, Emacs, JetBrains IDEs, Obsidian, Oxygen XML, Qt Creator, and Vim ALE. Its language server adds autocomplete, diagnostics, hover popups, and quick fixes in LSP-capable editors. Vale also runs in GitHub Actions and as a pre-commit hook, so checks can sit beside code review and local editing.

Its CI behavior is deliberately selective: warnings and suggestions do not fail a pipeline, while error-level alerts return a non-zero exit code. That lets teams distinguish advisory feedback from release-blocking rules, but requires care when deciding which findings deserve error status.

Pricing

Vale uses a freemium model. The Free plan costs nothing, is MIT-licensed and open source, and includes the core linter approach without a published seat or usage quota. It is the natural starting point for individuals, open-source projects, and teams able to manage their own configuration.

Paid access starts at 19 /user/mo. Custom pricing applies where a plan is not given a public price. The paid offering is the relevant route for organizations that need team workflow features, custom style guides, terminology management, and brand-voice rules under a managed arrangement.

Platforms

Vale is available on Linux, macOS, Windows, the web, and as a self-hosted deployment. The binary and self-hosted options suit teams that keep writing workflows close to their repositories or require control over where checks run; web availability provides an additional access point without changing the rule-based model.

Who it's for

Choose Vale for documentation teams and engineering organizations that need one configurable style system across editors, markup, code comments, structured content, and CI. It is particularly compelling when offline operation, YAML-defined rules, and self-hosting matter. A casual writer seeking automatic rewrites, or a team unwilling to maintain style configuration, should look elsewhere.

Pros and cons

Pros

  • Offline and account-free: the single-binary design works without a server or model.
  • Unusually broad coverage: markup, code comments, and structured-content views extend checks into engineering workflows.
  • Configurable standards: YAML rules, terminology controls, brand-voice rules, and established style packages support a real house style.
  • Strong integration surface: major editors, LSP features, GitHub Actions, and pre-commit hooks connect writing review to daily development.
  • Free open-source entry point: the MIT-licensed Free plan removes a price barrier for individual and open-source use.

Cons

  • Configuration is part of the job: teams must select and maintain rules and Views for reliable results.
  • Not an online writing assistant: its rule-based model does not provide the broader hosted-assistant experience some writers expect.
  • CI policy needs deliberate setup: only errors fail builds, so warnings and suggestions can pass unnoticed unless teams review them separately.
  • Commercial terms are limited: paid access starts at 19 /user/mo, while fuller seat and renewal terms require clarification.

Alternatives

Sapling is a better fit when you want a freemium web, Windows, extension, API, or self-hosted service with a free trial and AI-detector quotas.

StyleMCP suits teams seeking an API-oriented service: its free plan includes 5,000 requests per month, all API endpoints, basic rule-based rewrites, a default SaaS pack, and community support.

DeepL Write is the alternative for users who prefer an AI writing assistant across Android, iOS, desktop, and browser extensions; its Write Pro add-on is €6.99 a month when billed annually with VAT included.

Hemingway Editor is aimed at writers wanting a web or desktop editor with metered AI sentence plans, including Individual 5K at $8.33 a month billed annually.

ProWritingAid fits writers who want guided reports and rephrasing, with a free plan capped at 500 words per report run and two runs per day.

textlint is another free, MIT-licensed rule-based option, but it requires Node.js 20 or newer.

Trinka offers a freemium writing service across web, desktop, extensions, API, and self-hosted deployments.

Claritar is suited to client-analysis workflows, with a free tier limited to one client, one seat, and five analyses per month.

Verdict

Vale is the right choice for technical writers, documentation teams, and developers who want enforceable style rules embedded in editors, repositories, and CI while keeping checks offline. Its main reason to choose it is the combination of broad format coverage and deep configurability. Look elsewhere if you want a hosted assistant that rewrites prose for you or if your team cannot invest in maintaining rules.

The verdict

Vale offers offline prose checks with configurable rules and broad editor support. Its CI behavior is worth noting: only error-level alerts produce a non-zero exit code.

Questions people ask

Does Vale work offline?

Yes. Vale runs offline as a single binary without an account, server, or model.

Which editors integrate with Vale?

Listed integrations include VS Code, Cursor, Windsurf, Neovim, Sublime Text, Zed, Emacs, JetBrains IDEs, Obsidian, Oxygen XML, Qt Creator, and Vim ALE.

Can teams create their own style guide?

Yes. Users can write custom Vale rules in YAML and choose which rules and styles apply to files.

How much does Vale cost?

A free plan is available. Paid plans start at $19/user/mo.

Can Vale run in continuous integration?

Yes. It runs in GitHub Actions, as a pre-commit hook, and through its language server in LSP-capable editors.

What the maker publishes

Alert behavior
Only error-level alerts cause Vale to return a non-zero exit code; warnings and suggestions pass in CI. source
Automation
Vale can run in GitHub Actions, as a pre-commit hook, and through its language server in LSP-capable editors. source
Code comments
Vale can extract and check comments in 19 programming languages, including Go, Rust, Python, JavaScript, TypeScript, and Java. source
Custom rules
Users can write their own Vale rules in YAML and configure which rules and styles apply to files. source
Documentation platforms
Mintlify and Promptless are listed as hosted documentation platforms that run Vale. source
Editor integrations
Listed editor integrations include VS Code, Cursor, Windsurf, Neovim, Sublime Text, Zed, Emacs, JetBrains IDEs, Obsidian, Oxygen XML, and Qt Creator. source
Founded
2017 source
Intended users
Vale is aimed at people and teams who want style-guide checks in their editors and alongside their code, including documentation teams. source
Language server
Vale’s language server provides editor autocomplete, diagnostics, hover popups, and quick fixes. source
Markup formats
Vale supports markup including Markdown, AsciiDoc, reStructuredText, MDX, MyST, Quarto, Typst, HTML, XML, DITA, Org, and QDoc. source
Offline use
Vale runs offline as a single binary, without an account, server, or model. source
Platforms
Vale runs on macOS, Windows, and Linux. source
Purpose
Vale is an open-source command-line linter that checks prose against style-guide rules. source
Structured content
Vale Views can select prose in OpenAPI, Jupyter notebooks, commit messages, transcripts, docstrings, JSON, YAML, and TOML. source
Style packages
Vale offers ready-made packages including Google, Microsoft, Red Hat, readability, and Harper grammar styles. source
Support
The project directs users to GitHub issues or Discord for questions and support. source

Checked against the maker's pages on 29 Sept 2026.