Workflow utility · runs in your browser

Count the words before you prompt.

A calm, local word and character counter for shaping AI prompts before you send them. It counts the text you provide; it does not claim to calculate model-specific tokens.

Prompt scratchpad

Drop .txt or .md

Length planning by model

Approximate context use
GPT-40 / 8,192 tokens
Within planning range
Start with a preset
Customize this template

0Words
0Characters
0Lines
0Est. tokensApprox. for GPT-4
0 minReading timeAt about 200 words/min
0 minSpeaking timeAt about 130 words/min
$0.0000Est. API cost Illustrative input rate: $30.00 per 1M tokens for GPT-4. Actual provider pricing, output tokens, and billing rules may differ.GPT-4 planning rate

Planning estimate only: based on the approximate input token count and an illustrative input rate. Provider pricing, output tokens, and billing rules may differ.

Token estimate is for rough planning only; actual tokenization varies by model and tokenizer.

Use the count as a check.

A longer prompt is not automatically a better prompt. Look for the smallest context and constraint set that lets another person review the request.

Brief-first check

  • Is the task specific?
  • Is the audience named?
  • Are constraints visible?
  • Can the output be reviewed?

Why this belongs in the workflow.

Small tools are useful when they make a review step clearer, not when they promise to replace judgment. This utility keeps the work visible and processes the input locally in your browser.

Privacy note. The current version does not upload your text to a server. Avoid pasting confidential material into any browser tool unless you understand the device and browser you are using.

Continue with a small utility or a practical guide that supports the same step in your workflow.

How to use the AI prompt counter.

  1. Paste a draft prompt into the scratchpad.
  2. Compare words, characters, and the approximate token count.
  3. Use the result as a planning signal, then check the final prompt in the model you actually use.

Example: prepare a support triage prompt

Input: a task, audience, constraints, and output shape before sending a long prompt.

Task: turn these support notes into a triage table Audience: the on-call engineer Constraint: mark unknowns instead of guessing Output: issue, evidence, next check

Verify: the count helps compare versions, but the person sending the prompt still checks whether the source notes are complete.

What this tool does not promise

It does not produce official token counts, guarantee a prompt will fit a model, or judge whether the prompt is factually correct. Tokenization and context limits vary by model and may change.

Important: All processing happens locally in this browser. Token counts are estimates, not official model billing measurements.

Continue the workflow

when the prompt still lacks a clear task, audience, constraint, or output shape.

when the counted prompt is preparing progress notes for another reader.

when you need to inspect headings, lists, or a handoff structure before sharing.

Frequently asked questions