Word Count by Section

What it does

Word count and section balance are two different writing-quality signals. Total word count tells you whether you're hitting an assignment, article, or submission length target. Per-section balance tells you whether your structure is actually doing what you intended — a 1,500-word essay with 60% of words in one section and 5% in another almost always has a structural problem (one section is doing too much heavy lifting; another is underdeveloped). Professional editors and writing coaches consistently flag imbalanced section weights as the most common revision target after wordy paragraphs.

The tool takes any Markdown-formatted document (using # / ## / ### headings to delimit sections), parses it, and reports: total words, total characters (with and without spaces), paragraph count, sentence count, estimated reading time at 200, 250, and 300 wpm (typical English silent reading speeds), and a per-section breakdown showing words in each ## heading section, plus that section's percentage of the whole. Section depth follows Markdown heading levels — ## sections are typically the structural divisions; ### are subsections within them.

Common applications: long-form blog post balancing (most posts work best when no single H2 section dominates more than 25-30% of total words), academic paper structure analysis (intro should be ~10%, methods ~20%, results ~30%, discussion ~30%, conclusion ~10% in typical scientific papers), book chapter pacing (consistent chapter length signals professional editing — wildly variable lengths feel sloppy), newsletter/article cropping (target word count for a specific publication — Atlantic features run 4,000-8,000; NYT op-eds 800-1,200), and conference presentation prep (slides at 100-150 words per minute of speaking time).

How to use it

1. Paste your Markdown document — use # / ## / ### headings to define sections.
2. Read total stats: words, characters, paragraphs, sentences, reading time.
3. Scan the per-section breakdown — each H2 with word count and percentage of total.
4. Identify imbalanced sections: any section >30% of total or <5% may need restructuring.
5. Iterate — restructure outline, repaste, recompare until distribution feels right.

When to use this tool

• Auditing structure of long-form blog posts, articles, or essays.
• Verifying a paper meets word-count requirements (assignment minimums, journal max).
• Checking book chapter consistency in a manuscript.
• Pacing speeches or presentations — calculate speaking time at typical 130-150 wpm rate.
• Editing client manuscripts where you need to summarize structure across multiple files.

When not to use it

• Plain text without heading structure — no sections to break down; use a basic word counter instead.
• Real-time word counting while writing — most editors (Word, Google Docs, Notion) show this natively.
• Comparing across documents in different formats — best for a single Markdown source.
• Multi-language documents (Chinese, Japanese without spaces) — tokenization assumes whitespace-separated languages.

Common use cases

• Educational use &mdash; demonstrating the underlying concept
• Onboarding a colleague who needs the same calculation/conversion
• Verifying a number or output before passing it on
• Quick use during a typical workday