Textlint is live · free · last verified 24 Oct 2026 · viability monitor
Textlint
Pluggable open-source text linting for Markdown and prose — install npm rules and fail the build on style violations.
If your docs live in Git and you already run linters, textlint earns its place in the same pipeline — one rule install and a .textlintrc, and prose problems fail the build like type errors. The v15.0.0 work on MCP structured output makes it genuinely usable for AI tooling that needs to read lint results. Skip it if you want to click "accept" on suggestions; this is a rules engine, not a proofreader.
Verdict generatedVerified 6d ago · liveness 60/100 · cite: rightaichoice.com/tools/textlint
- Node.js teams embedding prose checks into CI/CD alongside ESLint and Prettier
- Technical writers encoding a Markdown style guide as versioned npm rules
- Open-source maintainers keeping contributor docs consistent across a repo
- Builds that need autofix for common prose problems before a commit lands
- Writers who want point-and-click grammar suggestions with zero setup
- Teams needing a GUI to accept or dismiss each flagged issue manually
- Anyone expecting out-of-the-box grammar checking from an install alone
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip textlint if you want a proofreader that suggests grammar corrections as you type and you have no intention of maintaining a Node.js rule set — its value comes from rules you install and configure yourself, not from defaults.
Every rule is a separate npm dependency you own, so rule count directly adds to your dependency-review and upgrade workload.
Textlint is open source and free to use, so cost is measured in engineering time rather than licence fees: choosing rules, maintaining .textlintrc, and keeping the Node.js runtime current. That makes it inexpensive for a team already running npm-based tooling and comparatively expensive for a team without Node.js experience, where a GUI proofreader gets to first value faster.
In short
Textlint — Pluggable open-source text linting for Markdown and prose — install npm rules and fail the build on style violations. Best for Node.js teams embedding prose checks into CI/CD alongside ESLint and Prettier, Technical writers encoding a Markdown style guide as versioned npm rules, Open-source maintainers keeping contributor docs consistent across a repo. Free to use.
What is Textlint?
Textlint — Pluggable open-source text linting for Markdown and prose — install npm rules and fail the build on style violations. Best for Node.js teams embedding prose checks into CI/CD alongside ESLint and Prettier, Technical writers encoding a Markdown style guide as versioned npm rules, Open-source maintainers keeping contributor docs consistent across a repo. Free to use.
Textlint applies the linter model to prose. It's an open-source JavaScript utility that checks natural language the same way ESLint checks code — and the design decision that matters is that it ships no rules of its own. You install what you want as individual npm packages (npm install --save-dev textlint-rule-no-todo), scaffold a .textlintrc with npx textlint --init, then run npx textlint README.md against your files. Markdown and plain text work by default; HTML and other formats arrive through custom plugins. The workflow is terminal-first. Textlint imports as a Node.js module, so you can drop it into build scripts and let a prose violation fail a build the way a broken test does. Rules, presets, plugins, filters and formatters are all authorable, and many rules ship fixers so a chunk of the flagged issues correct themselves. The current baseline is v15.0.0 (2026-08-24), which raises the runtime floor to Node.js 20, removes deprecated APIs, and upgrades Model Context Protocol integration with structured output and JSON schema validation — meaning AI tooling consumes results as structured data rather than parsing free text. A free in-browser playground on the homepage lets you test rules before installing anything, and the User Manual and Developer Guide cover configuration and ignoring text. It suits developers, technical writers and open-source maintainers who want their style guide encoded as versioned npm rules and enforced in CI. Against GUI proofreaders the trade is explicit: no point-and-click suggestion triage and no grammar checking out of the box, in exchange for scriptable rules that live beside your code and travel with the repo.
Key features
- Lint Markdown and plain text out of the box
- Other formats such as HTML through custom plugins
- Install rules as npm packages, e.g. textlint-rule-no-todo
- Generate a .textlintrc with npx textlint --init
- Run from the CLI: npx textlint README.md
- Import textlint as a Node.js module in build scripts
- Automatic fixes for rules that ship with fixers
- Custom formatters, bundled and self-authored
- MCP integration with structured output and JSON schema validation (v15.0.0)
- Requires Node.js 20+ as of v15.0.0
- Author custom rules, presets, filters, plugins and formatters
- Free in-browser playground for testing rules before installing
- Open source and free to use
- Community-maintained rule collection published on npm
- Ignore-text and configuration options documented in the User Manual
Behind the verdict
Pick textlint when the problem is consistency rather than correctness. If three contributors write "e.g." four different ways and nobody can agree on heading case, encoding those as npm rules and running them in CI settles it permanently. The pluggable model is the whole point: you get exactly the rules your project needs and nothing else, which is why teams with a house style guide tend to stick with it. The v15.0.0 release is the reason to look now rather than later. Node.js 20 as the floor and the deprecated API removal are housekeeping, but structured output plus JSON schema validation over Model Context Protocol changes who can use it — an AI agent can consume lint results as data instead of regex-scraping terminal text. Where it bites: there's no grammar checker in the box. Install nothing and you get nothing. The rule ecosystem is community-maintained, so quality varies rule to rule, and you'll spend an afternoon evaluating before you trust a preset in CI. Non-developers on the team will not adopt it — the .textlintrc file is a hard wall for a marketing writer. Our honest read is to use both. Reach for textlint for the rules you can state precisely, and keep a GUI proofreader for the judgment calls a rule can't encode. Closest alternative is Vale — similar prescriptive, CI-friendly philosophy, but its rule packs are YAML rather than npm packages, so the choice often comes down to whether your team already lives in the Node toolchain or prefers a standalone binary.
Limitations
- Textlint is a programmable natural-language linting engine, not a hosted AI assistant and not a grammar checker you can use without choosing rules.
- Markdown and plain text work by default; HTML and other formats need custom plugins.
- As of v15.0.0 it requires Node.js 20 or later, removed deprecated APIs, and added developer-facing MCP integration, so older rules and code using the legacy APIs may need migration.
- Setup means npm-installing textlint plus each rule you want and configuring them in a .textlintrc file, which requires basic Node.js and CLI familiarity.
- There is no GUI for triaging suggestions — output is a report plus whatever your chosen rules can autofix.
as of 2026-10-19
Researching Textlint? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Textlint still active?
Textlint is live · free · last verified 24 Oct 2026 · viability monitor.
Viability score
How well maintained and how widely used is Textlint? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →What's new in Textlint
Checked 10 days agoAcross the latest 1 update: 1 feature update.
What do users say about Textlint?
What people actually say about Textlint — is it worth it?
Our community sentiment research written Jul 30, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
How we verified this
Every listed fact about Textlint— pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 24 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.
Verification history
We have re-verified Textlint 9 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed features, summary, who it suits, description, who should skip it, our verdict
- — changed pricing page
- — changed our verdict, limitations, who it suits, use cases, description, summary, who should skip it, setup time, pricing fit, features, hidden costs, switching out, switching in
- — changed limitations, pricing page
- — changed who should skip it, our verdict, who it suits, summary, features, description
- — changed limitations, platforms, pricing page
Showing the 6 most recent of 9 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Textlint cost in 2026?
Textlint: Free to use. Pricing last verified 24 Oct 2026.
Where the pricing makes sense
The company stage and team size where Textlint's pricing actually pencils out — and where peers do it cheaper.
Textlint is open source and free to use, so cost is measured in engineering time rather than licence fees: choosing rules, maintaining .textlintrc, and keeping the Node.js runtime current. That makes it inexpensive for a team already running npm-based tooling and comparatively expensive for a team without Node.js experience, where a GUI proofreader gets to first value faster.
Has Textlint's pricing changed?
No plan price for Textlint has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Textlint?
Pick Textlint if you are Node.js teams embedding prose checks into CI/CD alongside ESLint and Prettier, Technical writers encoding a Markdown style guide as versioned npm rules, Open-source maintainers keeping contributor docs consistent across a repo, Builds that need autofix for common prose problems before a commit lands.
Look elsewhere if you are Writers who want point-and-click grammar suggestions with zero setup, Teams needing a GUI to accept or dismiss each flagged issue manually, Anyone expecting out-of-the-box grammar checking from an install alone, Projects pinned to Node.js versions below 20 on the current release.
Skip it if Skip textlint if you want a proofreader that suggests grammar corrections as you type and you have no intention of maintaining a Node.js rule set — its value comes from rules you install and configure yourself, not from defaults.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Textlint actually fits — and what changes day-one when you adopt it.
Add textlint and textlint-rule-no-todo as dev dependencies, generate .textlintrc with npx textlint --init, and run npx textlint README.md in the CI job that already runs tests.
Outcome: Pull requests with leftover TODOs or style violations fail the build before merge, so documentation quality stops depending on reviewer attention.
Encode the house style guide as a rule preset published to npm, then have every docs repo install it alongside textlint and run it on the Markdown folder.
Outcome: One versioned package defines the style for all repositories, and improving the guide is a normal dependency bump reviewed like code.
Import textlint as a Node.js module and consume results through the v15.0.0 MCP integration with structured output and JSON schema validation.
Outcome: The assistant receives lint findings as validated structured data rather than free text, so prose checks can drive automated edits reliably.
Use cases
- Fail a CI/CD build when Markdown docs violate your style guide
- Enforce consistent writing across a team's technical blog or docs folder
- Write custom rules that catch domain-specific terminology mistakes
- Feed lint results to an AI agent as structured MCP output instead of parsing text
- Catch leftover TODO comments in prose before publishing
- Keep open-source README files consistent across many contributors
- Automatically fix common prose problems in files tracked in Git
Setup time & first value
How long it actually takes to get something useful out of Textlint — broken out by persona, not the marketing-page minute.
Roughly 10-15 minutes for a developer already comfortable with npm: npm init, npm install --save-dev textlint, install one rule, run npx textlint --init, then npx textlint README.md. Add the browser playground first if you want to compare rules before committing. Assembling a full house style guide from scratch is a multi-session job, not a one-sitting install.
Switching to or from Textlint
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From a GUI proofreader: export your style preferences as a checklist, then find or write textlint rules that encode each item and pin them in .textlintrc.
- →From Vale: map your existing style rules onto textlint rules or presets, and run both on the same Markdown folder until output matches.
- →From no linting at all: start with the no-todo rule from the getting-started guide, get it passing in CI, then add rules one at a time.
- ↗To a GUI proofreader: keep textlint in CI for prescriptive rules and add the proofreader for suggestions your rules cannot express.
- ↗To ESLint-only tooling: there is no direct path — textlint targets natural language, so you would lose prose checks rather than port them.
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Textlint”, and we withheld 6: 6 could not be judged, because “Textlint” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Textlint.
Official links
What are the best Textlint alternatives?
The closest alternatives to Textlint we list are AiEditor, Eskritor and Wordtune. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| AiEditor | Freemium | Pricing not published | — |
| Eskritor | Freemium | Pricing not published | — |
| Wordtune | Freemium | Pricing not published | — |
Alternatives to Textlint
View all
AiEditor
Open-source AI rich text editor: embed the AI editing loop in Vue, React, Angular or Svelte and point it at your own LLM
Tools that pair well with Textlint
Common stack mates teams adopt alongside Textlint, with the specific reason each pairing earns its keep.
AiEditor
Open-source AI rich text editor: embed the AI editing loop in Vue, React, Angular or Svelte and point it at your own LLM
Eskritor
Eskritor is a free AI text generator that drafts blogs, essays, emails, resumes, stories, and citations from a prompt, with style and length controls.
Wordtune
Wordtune is an AI writing assistant from AI21 Labs that paraphrases, rewrites, proofreads, and summarizes text and YouTube videos.
Textlint vs its closest rival
Textlint's closest head-to-head is with Writer — If your priority is on-brand, automated content generation at enterprise scale with IT security and governance, Writer is the clear choice — but it's expensive and overkill for individuals. For developers and technical writers who need a programmable, pluggable linter to enforce style in Markdown, textlint is free, powerful, and integrates into CI/CD, though it requires comfort with CLI and Node.js. Verdict generated
Head-to-head comparisons
Textlint vs Writer
If your priority is on-brand, automated content generation at enterprise scale with IT security and governance, Writer is the clear choice — but it's expensive and overkill for individuals. For developers and technical writers who need a programmable, pluggable linter to enforce style in Markdown, textlint is free, powerful, and integrates into CI/CD, though it requires comfort with CLI and Node.js.
GeneratedTextlint vs Letterhead
For technical writers and dev teams who want a free, programmable linter for Markdown/prose, Textlint is the obvious pick. For media companies managing multiple newsletters at scale with AI curation and deliverability features, Letterhead’s enterprise platform justifies the custom pricing. Choose Textlint for lightweight automation; choose Letterhead when portfolio-wide analytics and revenue tools matter more than cost.
GeneratedTextlint vs Surfer Ai
If you need to crank out SEO-optimized articles at scale and track visibility in AI search results, Surfer AI is the clear choice. If you're a technical writer or developer who wants to enforce style rules programmatically in Markdown text, textlint is a powerful, free, open-source tool. They solve completely different problems – one generates content, the other lints it.
GeneratedFrequently asked questions
Used Textlint? Help shape our editorial sentiment research.