LexiLint Logo

LexiLint: Proofread published webpages

Check the entire page in one click

Proofread the rendered page before readers see it. Spell checking runs on your device; optional AI grammar uses the provider key you configure.

US and UK English spell check included  |  Optional Gemini BYOK grammar

See LexiLint in Action

Features

Offline Spell Checking

  • Checks supported live, staging, and localhost pages
  • US and UK English variants included; six additional languages with Premium
  • Custom dictionary for technical terms, names, and brands
  • No extension usage analytics or remote error reporting
  • Highlights possible misspellings on the rendered page

AI Grammar Checking

  • Grammar, style, clarity, punctuation checking
  • Multi-provider support: Gemini (free), OpenAI (premium), Claude (premium)
  • Bring Your Own API Key (BYOK) - you control the data
  • Checks headings, paragraphs, and lists in context
  • Context-aware checking for headings, paragraphs, lists

How It Works

  1. Click the LexiLint icon in your browser toolbar
  2. Click "Check Spelling" for offline scan (instant)
  3. Click "Check Grammar (AI)" for AI analysis (free with API key)
  4. Click highlighted errors to see suggestions
  5. Accept suggestions or add words to custom dictionary

Who Uses LexiLint?

Content Creators

"Publish every page with confidence."

Articles, posts, and landing pages.

Developers

"Ship clean copy with the code."

Staging, localhost, and documentation.

Professionals

"Make every client-facing page polished."

Client sites, presentations, and reports.

Editors & QA

"Give every page one final check."

Review live pages before readers do.

LexiLint and Grammarly solve different jobs

Grammarly helps you write. LexiLint helps you publish.

Use Grammarly while typing. Use LexiLint to check the finished webpage.

Feature LexiLint Grammarly
Check published webpages
Works on localhost/staging sites
100% offline spell checking
BYOK (Your own API key) Free
Check while typing in email/text fields
Works in Gmail, Google Docs, Slack

How offline spell check stays offline

One click. No uploads. Zero network requests.

  1. LexiLint reads the visible text on the page.
  2. It checks each word locally using the dictionary for your selected language.
  3. Suggestions appear directly on the page.

AI grammar goes directly to your chosen provider using your own API key. LexiLint never receives the text.

Spell-check inside Claude and Cursor

Use LexiLint MCP to proofread AI-generated text without spending AI tokens on spell check.

  • Works with Claude Desktop, ChatGPT, and Cursor
  • One-line install: npx lexilint-mcp
  • Offline spell check; BYOK for AI grammar

LexiLint Premium

🎉 Limited Time Offer - 50% OFF

Offline spell check and English AI grammar (Gemini) stay free, forever. Premium adds OpenAI & Claude, plus spell check and grammar in 6 more languages.

Lifetime

$29.99
$59.99
-50%

One-time payment

  • ✅ All free features
  • ✅ OpenAI provider
  • ✅ Anthropic Claude provider
  • ✅ 6 additional languages (Spanish, French, German, Russian, Polish, Turkish)
  • ✅ Lifetime updates
Get Lifetime Access

Monthly

$2.99/mo
$5.99/mo
-50%

7-day free trial

  • ✅ All free features
  • ✅ OpenAI provider
  • ✅ Anthropic Claude provider
  • ✅ 6 additional languages (Spanish, French, German, Russian, Polish, Turkish)
  • ✅ Test all languages risk-free
  • ✅ Cancel anytime
Start 7-Day Free Trial

💳 Secure checkout via Polar.sh (powered by Stripe)

🔒 Monthly includes 7-day free trial

🔑 BYOK model - You provide your own API keys

Your Words. Your Privacy.

Offline spell check stays on your device. AI grammar goes directly to the provider you choose.

On-Device Spell Checking

The spell-check operation does not upload page text and works without an internet connection.

BYOK Provider Choice

Optional grammar checking sends selected text directly to the provider configured with your API key.

No Extension Analytics

The current extension does not collect usage analytics, telemetry, or page text.

Browser Profile Storage

Provider keys are stored through Chrome's extension storage API and are not sent to Ignite App. Protect access to your device and browser profile.