Count words in Obsidian notes and Markdown

Start with the active note

Official help describes Word count as a core plugin for the active note. On desktop it appears in the status bar; on mobile, at the top of the right sidebar. If missing, first check core-plugin settings and your environment.

It does not automatically count a folder or entire vault. Define notes belonging to a chapter collection. Before seeking extensions, identify what is missing: counting an extracted paragraph and preparing one combined project version are different tasks.

Source, reading text and project are distinct

A note contains Markdown syntax, links, organizational data and prose. Whole-file length need not match reader-facing text. Label the measure instead of declaring one universally correct.

Narrative may include prose and headings; technical audits may need source; exported articles may exclude tags, properties and editorial comments. Decide before comparing. The brief official documentation does not specify every Markdown construction, so we do not attribute unverified handling rules to the core plugin. Test a sample in your actual version when an edge case matters.

Link destinations and displayed labels can differ

Obsidian documents wikilinks and Markdown links with alternate displayed text. Extraction may retain the destination filename, visible label or both.

Keep this exact Italian source for its arithmetic: La cura del [[Giardinaggio|giardino]] richiede pazienza. The intended rendered sentence is “La cura del giardino richiede pazienza.” Our engine counts 6 words and 39 characters including spaces in the rendered text, versus 7 words and 56 characters in uninterpreted source. The technical name “Giardinaggio” contributes to the difference.

This checks our engine, not Obsidian’s native count. Prepare the representation answering your question; a generic counter cannot infer it.

Separate note organization from reading content

Properties hold structured status, topics, dates and links. Obsidian documents their YAML storage at the start of a file. These need not belong to every editorial count.

For three property lines and a page of prose, export prose only when that is the delivery. A technical archive audit may include metadata instead. State the decision. Do not delete original properties just to lower the number: count a copy or extraction, preserving archive organization and the delivery scope.

A linked item is not automatically another chapter

Decide whether repeated references should appear repeatedly in a combined output. Navigation links do not create chapters. List delivered notes and internal references. If a passage appears twice, check whether it is intentional.

Do not automatically deduplicate the project: identical sentences can serve different purposes and near-duplicates may require editing. When export renders an embed, check the passage’s beginning, end and position. A total cannot detect wrong order or establish that the reference is where readers need it.

Build totals from a verifiable inventory

For a small collection, list note name, inclusion and count. Chapters of 800, 950 and 1,100 words total 2,850. Add a 250-word introduction for 3,100. A 600-word research note stays out when it is outside delivery.

These are invented values, not a real vault measurement. The table reveals twice-counted notes and missing sections. Use a method producing the same verifiable inventory for larger collections. External tools and community plugins have their own options; word totals alone do not make them equivalent to the core plugin. Check file selection, exclusions and content handling.

Test a small note when counters disagree

Make a note with a heading, sentence, labeled link and property, then another with visible prose only. Measure both and state whether you are investigating words, characters or inclusions.

Our word counter analyzes pasted text. It does not reconstruct a vault, follow wikilinks or render embeds. Pasted source is measured as source under our rules. If plain prose still differs, test apostrophes and hyphens. Determine whether segmentation or incomplete export explains it before changing every note to force agreement.

Keep delivery text separate from notes

Save the prepared submission and attach its count to that version. Notes can keep changing without making the communicated total ambiguous. Recount if delivery text changes.

Record included notes, property treatment, link representation and version date. Include scope-changing decisions, not every application setting. This preserves Obsidian’s organizational role while tying the count to what another person reads. If a recipient mandates a program or rule, prepare that format and use its measure for official verification.

Use counts to find real imbalances

A long chapter merits reading: does it contain two topics, repeat material or need more space? Compare sections serving the same purpose. Research notes and polished chapters need not be similar lengths.

Counts raise revision questions, not impose uniformity. After cutting, check remaining references in delivery text. Removing necessary context can improve an indicator while worsening comprehension. Finish by reading the document rather than simply reaching a target.