Half your email is apology. Find it before you send it.

Paste a draft and see exactly where you overexplain — the hedging, the second apology, the three-paragraph justification for a one-line ask — with a plain-English trim for every flagged sentence and a suggested concise rewrite.

  • Your draft never leaves the device
  • No sign-up · no install · no account
  • Per-sentence flags, not a vague score
  • Concise rewrite you can copy

Check an email draft

0 / 8,000 characters

Paste a draft above — or load the sample to see how the detector works. Nothing is uploaded. Your draft stays in this browser and is cleared when you leave.

Privacy you can verify, not just trust

Most writing checkers are cloud services: paste your email, and it travels to their server to be analysed — and often stored. This one can't: the check runs entirely in your browser, on this device. Your draft never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. Don't take our word for it:

New cross-origin requests during use: 0
  1. Press F12 to open developer tools, then the Network tab.
  2. Paste a draft and check it above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no draft text ever leaves your device.
  3. Extra credit: disconnect your internet after this page loads — pasting, checking and copying the rewrite still work.

How to stop overexplaining your emails

Overexplaining is rarely a writing problem — it is a nerves problem. You are not sure the ask will land, so you pad it: a hedge, an apology, a paragraph of reasons before the one sentence that matters. The reader skims past the padding and misses the ask anyway. The fix is mechanical, and this page does it sentence by sentence:

  1. Paste the draft and check it — the detector scores every sentence for hedging, redundant apologies, over-justification, wordy phrases, filler openers and closers, long sentences and repeated points, and gives you a conciseness score from 0 to 100.
  2. Read each flag in plain English — every flagged sentence shows the exact phrase that triggered it and a suggested trim, so you can decide whether the words earn their place or just buy reassurance.
  3. Take the concise rewrite as a starting point — the tool applies the same trims and drops filler sentences, usually cutting a fifth to a third of the words. Read it once before sending: it is a mechanical trim, and anything that carried real meaning should go back in.

What makes this detector different

The pages that top the results for this search are mostly general writing checkers or AI detectors. A business writing checker scores clarity, conciseness and tone as one blended number and puts its rewrite behind a fair-use limit; an email length checker only counts words; and AI email detectors answer a different question entirely — whether a machine wrote the message. None of them is built for the specific habit this page targets: overexplaining. This is the only free, fully client-side checker we found that scores hedging, redundant apologies and over-justification as their own signals, flags each sentence with a plain-English trim, and hands you a concise rewrite — with a live network-request counter so you can verify the privacy claim yourself.

When is trimming the right choice — and when is it the wrong one?

Trimming is right when the padding exists to reassure you, not inform the reader: the second apology, the reason nobody asked for, the opener that says nothing. It is the wrong choice when the length carries real information — a first-time instruction, a sensitive apology, a clarification that prevents a misunderstanding. If the reader genuinely needs the context, keep it. The detector flags patterns; you decide which ones are padding.

Honest limitations

Pattern matching, not understanding

The tool matches words and phrases. It cannot know your intent, your relationship with the reader, or whether a long explanation was justified.

Tone is contextual

“Sorry” in a genuine apology is not a flaw, and a hedge can be polite rather than weak. A flag is a prompt to re-read, not an order to delete.

The rewrite is mechanical

It applies phrase replacements and drops filler sentences. It can produce awkward or over-short wording — read it before sending.

No grammar or spelling check

The tool only looks for overexplaining patterns. It does not check grammar, spelling, punctuation or facts — use a spellchecker alongside it.

One email at a time

Drafts are capped at 8,000 characters. A whole thread scores badly for reasons that have nothing to do with overexplaining — check one email at a time.

Scores are this tool's own

The 0–100 score comes from this page's pattern list. It is not a published readability standard, and it is not comparable with scores from other checkers.

Frequently asked questions

Does my email draft upload anywhere?

No. The check runs entirely in your browser — your draft never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the detector.

What does the conciseness score mean?

It is a 0–100 score from this tool's own rules: 80 or more means concise and ready to send, 60–79 mostly tight with a few trims, 40–59 overexplaining, and under 40 heavily overexplained. It is relative to this tool's pattern list, not to any published readability standard, and it is not comparable with scores from other checkers.

Is every flagged sentence wrong?

No. The detector matches word and phrase patterns; it cannot know your intent, your relationship with the reader, or whether a long explanation was actually needed. A first-time instruction, a sensitive apology and a legal clarification all legitimately need more words, and a hedge can be polite rather than weak. Treat each flag as a prompt to re-read, not an order to delete.

Can I trust the concise rewrite?

As a starting point, yes; as a finished email, no. The rewrite applies the same phrase replacements and drops filler sentences mechanically, so it can produce awkward or over-short wording. Read it once before sending, and restore anything that carried real meaning.

What counts as overexplaining?

Six things: hedging ("just", "I think maybe", "sort of"), redundant apologies (more than one "sorry"), over-justification ("the reason is", "as you know"), wordy phrases ("due to the fact that" for "because"), filler openers and closers ("I hope this email finds you well"), and sentences over 25 words. The tool also flags words that repeat across two or more sentences, which usually means the same point is being made twice.

How long a draft can I check?

Up to 8,000 characters — one email, not a whole thread. Longer drafts are usually threads or documents; paste one email at a time for a useful score.

Does it check grammar or spelling?

No. It only looks for overexplaining patterns. It does not check grammar, spelling, punctuation or facts, and it does not know whether what you wrote is true — use a spellchecker alongside it if you need one.

What does this tool NOT do?

It does not understand your email, judge whether your tone fits the relationship, or know whether a long explanation was justified. It does not send email, store drafts, or learn from what you paste. The score and the rewrite are heuristics — your judgement is the final check.