Paste any draft to measure reading ease, grade level, sentence density, and difficult-word load using classic readability formulas.
Your readability score, grade level, formula breakdown, and editing guidance will appear here.
Measurement before revision
The Readability Scorer calculates surface features of the text in the application. It counts words, sentences, characters, syllables, and difficult words, then applies several established formulas. Flesch Reading Ease estimates relative ease, while Flesch-Kincaid, Gunning Fog, SMOG, Coleman-Liau, ARI, and Dale-Chall express difficulty through different grade-level assumptions. Showing the formulas together makes disagreement visible instead of pretending one number is definitive.
Scores are useful for locating friction, not judging the value of an idea. A low grade level does not prove that instructions are complete, and a high one does not make a research paper poor. Formulas cannot evaluate factual accuracy, logical order, empathy, cultural context, visual hierarchy, accessibility, or whether a reader has the background knowledge a document assumes.
Begin with a real audience and task. A public benefits notice may need plain steps; a specialist protocol may require exact terminology. Inspect the report for long sentences and dense vocabulary, revise one source of friction at a time, and score the new version. Read both versions side by side so a shorter sentence does not drop a warning, exception, citation, or essential relationship between ideas.
Use the consensus grade as a benchmark across drafts, not a universal pass mark. Short samples can swing sharply, and lists, headings, abbreviations, code, names, or multilingual text can distort formula assumptions. Finish with a human comprehension check: ask someone from the intended audience what action they would take, what remained unclear, and which terms required explanation.
Broad public; short steps and familiar terms
Score the complete application guide, inspect the longest sentences, define required legal terms, and retest after breaking multi-action paragraphs into numbered steps. Do not remove a condition merely to lower the grade level.
New practitioners who still need exact commands
Analyze the prose separately from code blocks. Shorten setup explanations, keep API names unchanged, add a plain-language definition before specialist terminology, and ask a new team member to perform the instructions. Successful completion matters more than an easy score.
Time-limited decision makers
Check sentence load and difficult-word density, then move the decision, risk, owner, and deadline to the opening. Replace internal abbreviations where possible and use bullets for independent facts. Preserve the numbers and qualifications that affect the decision.
Readability is not one score. The tool combines sentence structure, word familiarity, and grade-level formulas.
Flesch Reading Ease estimates how quickly a broad audience can move through your text.
Average sentence length reveals whether ideas are packed too tightly for fast comprehension.
Consensus grade level combines multiple formulas so one outlier does not dominate the report.
The analyzer flags uncommon or syllable-heavy words that may slow readers down.
The implementation follows the metric family exposed by the text-readability README.
Scores text from very easy to very confusing based on words per sentence and syllables per word.
Ease score
Converts sentence and syllable load into an estimated US school grade.
Grade level
Weights long sentences and complex words to estimate years of education needed.
Grade level
Uses polysyllabic words across sentence samples; best when the input has three or more sentences.
Grade level
Uses letters per word and sentences per hundred words instead of syllable counts.
Grade level
Uses characters per word and words per sentence to approximate comprehension grade.
Grade level
Highlights unfamiliar-word density to estimate how challenging the text feels.
Grade level
Use it before publishing, submitting, or sending any text where clarity affects trust.
Keep articles accessible while preserving the keywords and headings that matter.
Check whether essays and reports match the expected audience level.
Make proposals, briefs, and policies easier for busy readers to understand.
Lower friction in outreach, newsletters, onboarding, and support replies.
Give reviewers a shared scoring baseline before style edits begin.
Verify that generated or humanized text did not become harder to read.
Score your text before you publish, submit, or send it.
