About this character counter
This character counter measures your text as you type. It counts every character including spaces, the characters without spaces, the words, the sentences, the lines and the paragraphs.
Characters are counted the way people read them: an emoji such as 👍 or an accented letter such as é counts as one character, even when it takes several bytes in memory. Words are groups of characters separated by spaces or line breaks.
Character limits matter on many platforms: a tweet allows 280 characters, a Google title shows about 60, a meta description about 155 and an SMS 160. Paste your draft here to check it before you publish.
Sentences end with a period, a question mark or an exclamation mark; a last sentence without one still counts. Lines follow your line breaks, and paragraphs are blocks separated by an empty line.
Which controls should I check first?
The Character Counter form labels its controls as Your text. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| Hello world. Second one! ↵ ↵ New para 👍 | {"chars": 36, "nospace": 29, "words": 7, "sentences": 3, "lines": 3, "paragraphs": 2} |
What counts as one text element?
Text can be handled as visible graphemes, Unicode code points, bytes, words or complete lines. These units differ. A joined family emoji may look like one character while containing several code points; an accented character may use more than one encoded byte. Use the unit stated in this tool's method before comparing results with an editor or database. Line tools should receive one entry per line, while word tools use their documented whitespace boundaries. A transformation that preserves every visible word can still change separators, and a transformation that preserves every byte does not necessarily operate on complete visible characters.
How should I prepare a representative sample?
Start with a short excerpt containing the features that matter to your job: an accented letter, a number, punctuation, a repeated item, or a blank line. Choose the relevant options and inspect the result before processing the full text. Keep a separate source copy so that you can compare exact spaces and case. If duplicate labels refer to different records, attach identifiers before applying a list operation that could remove them. Text processing cannot infer whether two identical-looking names belong to the same record. A small sample makes delimiter mistakes easier to see than a long unstructured paste.
Which differences should I inspect after conversion?
Compare the first and last entries, any blank entries, and text around punctuation. Check whether the intended operation preserves line endings, joins tokens with spaces, or substitutes a custom delimiter. These are distinct behaviors: reversing words does not preserve the original layout, while reversing lines keeps each line's internal content together. A normalized comparison can intentionally ignore case or accents, whereas an exact comparison retains them. Read the stated method instead of assuming that all text tools share one normalization policy. If another application reports a different count, compare the boundary rules before treating either number as incorrect.
Why can copied text behave differently elsewhere?
A destination can apply its own normalization, line-ending rules, font substitution or length limits. Fancy Unicode letters are different characters from ordinary ASCII letters even when they look like a font change. Some destinations cannot display those glyphs, and searching plain text may not match them. Likewise a byte count changes with encoding, while a visual count may remain unchanged. Test a small converted sample in the receiving application before replacing a large document. Retain ordinary text when accessibility, searching or exact identifiers matter. A local text result is data rather than proof that the destination interprets it the same way.
How should I handle whitespace deliberately?
Tabs, ordinary spaces, nonbreaking spaces and explicit newlines can look similar on screen but carry different structure. A spreadsheet paste may introduce tabs, while a copied paragraph may contain hard line breaks from a PDF. Choose an operation suited to that structure before cleaning it. Trimming edges differs from collapsing internal whitespace; deleting line breaks differs from replacing them with spaces. Inspect a two-line sample to ensure that words do not accidentally join. If a tool normalizes separators, save the cleaned result under a new name so that the original layout remains available for comparison.
Does a space count as a character?
Yes. The first number counts spaces too; the second one (characters without spaces) leaves out spaces, tabs and line breaks.
How are words counted?
A word is any group of characters between spaces or line breaks, so « well-known » is one word and « 2026 » is one word.
Is my text sent anywhere?
No. The counting runs in your browser; nothing you paste leaves your device.