LanguageTool Free for non-native indie English: character limits first

When not to rely on LanguageTool

Legal contracts, medical instructions, and formal fundraising materials need human review. Do not paste customer names and unreleased numbers into unknown plugins. If a browser extension requests broad site permissions, tighten the grant before you continue.

If your English problem is structural confusion rather than articles and tense, rewrite the outline first. A green grammar pass will not rescue structure.

Scenario defaults

One person writing English cold emails and short updates should default to LanguageTool Free and check by field. One person maintaining long English landing pages and a help center should try Free in sections first, then reconsider Premium after repeated monthly caps. Teams that need shared terminology and care about GDPR language should read the official Business materials before buying seats instead of stretching a personal Premium.

If you already pay for Grammarly and only write short English sentences, do not stack Premium by default. Spending the same money on a native-speaker review of one critical email is often higher leverage.

Current recommendation

For non-native indie English checks, default to LanguageTool Free and let the 2,000-character field limit decide whether you must split sections. When long drafts stably hit the cap and you need a personal dictionary plus stronger style checks, buy against the live Premium page that day. Avoid duplicate subscriptions when a similar assistant already covers the job. Treat live on-page prices as authoritative; this article freezes only observed feature boundaries.

Fix a review order. Correct facts and links first, run grammar second, tone last. Reversing the order polishes outdated prices.

Before adding frequent “errors” to a personal dictionary, confirm they are brand spellings rather than real mistakes. Dictionaries remember stubbornness. A stubborn wrong spelling for a year costs more than one red underline.

Open browser extensions and editor plugins only on sites where you actually write. Fewer permissions lower the chance of pasting secrets into the wrong box. A writing assistant is a tool, not a second brain.

Split suggestions into must-fix and optional. Must-fix covers clear grammar errors and negations that change meaning. Optional covers overly formal tone preferences. Accepting everything turns product voice into a manual.

Check subject lines alone. They are short and still decide opens. Even with a wide character budget, do not stack three synonym adjectives in a subject. Specific and short beats ornate.

If you generate English docs with a static site, put LanguageTool on the pre-publish list next to link checks. Docs are crawled more often than emails; wrong plurals and prepositions linger. Fix once and the benefit outlasts a tweet.

When a team shares an error glossary, keep version history. Today’s product-name exception must be reversible tomorrow. A glossary without history becomes an untouchable inheritance.