Word Count in VS Code: A Markdown Extension and Plain-Text Checks
Blog / TEXT EDITORS
The Microsoft Marketplace listing for Word Count, extension ID ms-vscode.wordcount, describes an updating status-bar word count when a Markdown file is open. It is an extension workflow, not a universal built-in counter for every VS Code file type. For another format, verify the extension's scope or count a clean text excerpt separately.
Find the exact extension
Open VS Code's Extensions view with Ctrl+Shift+X on Windows or Linux, or Shift+Command+X on macOS. Search for the exact extension ID ms-vscode.wordcount and review the listing before installing. Similar names may belong to different publishers and offer different features.
Read supported file types and the publisher details rather than choosing the first result with an attractive icon. The cited listing describes Markdown behavior. Do not assume that an extension counts prose inside a Python file, a PDF, or every document in a workspace merely because its name says Word Count.
Review trust before installing
VS Code's documentation explains that extensions have the editor's permissions and advises assessing publisher trust. A counter can be useful, but its simplicity does not remove the need to review what you install. Follow your organization's policy when using a managed machine or working on confidential repositories.
If you only need a one-time count, installing an extension may be unnecessary. Copy the relevant prose to a trusted counter or a word processor instead. Top Word Counter processes its counting locally in your browser; that is a characteristic of this tool, not a guarantee about every extension or writing service.
Open a Markdown draft and inspect the status bar
After installing and enabling the extension, open a Markdown file and look for its updating status-bar count as described in the Marketplace listing. Test with a short ordinary paragraph first so you can confirm that the active file and language mode are appropriate.
Do not assume that the visible count aggregates all Markdown files in your repository. A folder can include several drafts, documentation pages, changelogs, and old versions. Establish whether you need the current file, a selected passage, or an entire publication, then use a method documented for that scope.
Distinguish Markdown source from rendered prose
Markdown can contain headings, link destinations, code fences, and formatting markers. A technical guide may include a substantial code example that should or should not count under a client's instructions. Check how your chosen method handles those parts rather than declaring every source token to be prose.
Suppose a tutorial contains 680 words of explanation and a separately measured 120-word code example. A prose-only requirement would use the explanation count; a requirement including the example would need both components. These illustrative figures show why defining scope matters more than selecting a particular extension.
Use consistent checks for documentation work
Keep source drafts unchanged when creating a cleaned copy for counting. Remove excluded code or link destinations only from that copy and retain all required explanation. Preview the rendered document to ensure you have not omitted captions, list items, or a final section from the measured passage.
At delivery, check the exact files or rendered content the recipient receives. An updating counter supports revision, but it does not replace proofreading, testing code examples, or checking whether the final export includes the latest changes. Use a consistent method so future counts remain comparable.
Frequently asked questions
Is this a built-in VS Code feature?
The cited workflow uses the Word Count extension, not a universal built-in word-count command.
Does ms-vscode.wordcount support every file type?
The Marketplace listing describes an updating count for Markdown files. Verify current supported behavior before relying on other file types.