Choose the count that matches your task
''A word count, a character count and a byte count answer different questions. This counter shows several views of the same pasted text so you can check an article limit, prepare a form response, inspect a list or estimate how much UTF-8 data a string contains. It does not decide which rule a publisher or receiving system uses. Read that rule first, then compare the matching result rather than treating all length limits as interchangeable.
Enter plain text and review the word count, Unicode character counts with and without spaces, line count, approximate sentence count and UTF-8 byte count. The input stays in your browser for the calculation. Up to 100,000 input characters are supported, subject to the memory available on your device. The tool counts the text that is present, including copied headings or footnotes, so remove material that does not belong in your submission before making a final length decision.
Use the count as feedback while editing. A longer passage can lose useful meaning if you cut words at random. First remove repeated ideas, then shorten phrases, and finally recheck the exact text you plan to paste. If the destination counts differently, test a short sample there and treat its accepted result as the practical rule for that destination.
Understand words, characters and spaces
''Words depend on boundaries
When the browser provides Intl.Segmenter, the counter uses its word segmentation to find word-like units. This is more useful than assuming every word is separated by a single space, especially with punctuation or languages whose writing does not follow that pattern. If the browser does not provide that feature, an approximate regular expression fallback is used. Neither method is an editorial ruling about whether a hyphenated expression should count as one word in a particular publication.
Names, contractions, URLs, abbreviations and mixed scripts can expose differences between counters. For a school or publication limit, check whether the instructions include titles, references, tables or captions. The software can count only the supplied text; it cannot infer which sections the receiving organization wants included. Keep a separate count for the main text and supplementary material when the rules distinguish them.
Unicode characters are not always visible symbols
The character count follows Unicode characters rather than counting only the number of positions in JavaScript's internal UTF-16 storage. Even so, a visual symbol can consist of more than one Unicode code point. An accented letter may be stored as one code point or as a base letter plus a combining mark. A family emoji or a flag can contain several code points while looking like one item. The displayed count therefore need not equal the number of visible marks you would point at on a screen.
The version without spaces helps when a limit excludes whitespace. Tabs, line breaks and unusual spacing deserve attention when text has been copied from another application. A blank-looking character can still be part of the source. Do not assume that deleting ordinary spaces also removes all invisible formatting. Inspect a short sample, especially if a destination reports a larger count than expected.
Read lines, sentences and UTF-8 bytes
''A line is based on a line break in the pasted text, not a visual wrap caused by the width of the input box. A long paragraph can wrap across ten screen rows while still being one logical line. Conversely, a list copied from a document may contain a real break after every short fragment. If your count changes when you join wrapped text, that usually reflects changes to the actual text rather than the width of the page.
The sentence count is approximate. Punctuation such as a full stop, question mark or exclamation mark is a useful clue, but natural language contains initials, decimal numbers, abbreviations and quoted fragments. “Dr. Rao arrived at 3.5 hours” has periods that do not all mark completed sentences. Use this metric as a rough structural aid. Read the text yourself when the exact number of sentences is part of an assignment or review rule.
UTF-8 byte count describes the encoded data size of the text. Basic ASCII characters such as A, 7 and a plain space normally take one byte each in UTF-8. Many accented letters take more, and many emoji take still more. A text with 200 Unicode characters can therefore occupy far more than 200 UTF-8 bytes. File formats may add metadata, line ending changes or a byte order marker, so this number is not a promise of the size of every saved file.
| Question | Useful result | What to check |
|---|---|---|
| Is this article within a word limit? | Words | Which sections the rule includes |
| Will this field accept my text? | Characters | The field's own counting method |
| How many items are in a one-item-per-line list? | Lines | Blank lines and final line breaks |
| How large is the text in UTF-8? | Bytes | Whether the destination adds other data |
A practical editing and verification workflow
''Begin with a clean source. Paste just the text you intend to measure, then check the start and end for accidental navigation labels, page numbers or an extra signature. If the text came from a PDF, look for line breaks within sentences and for words split across two lines. Joining those breaks may change both the line count and the word boundaries. Keep a copy of the unedited text while you repair it.
Make a small reference test before relying on a surprising result. A phrase such as “red blue green” should clearly contain three space-separated words. Then add punctuation, an emoji and a new line one at a time. This shows which metric changes and helps distinguish a segmentation choice from a paste mistake. You do not need to test every character; choose the features that appear in your real text.
For a maximum length, leave a modest practical margin if your destination uses an unknown algorithm. A draft that is exactly on the boundary in one counter may exceed it elsewhere because of a heading, a newline or a compound word. After pasting into the final form, check its own indicator and preview. Recount after every substantive edit, since a last-minute note can be enough to cross the limit.
For a list audit, compare the line count with your knowledge of the list. Blank lines and wrapped entries can create a mismatch. If each record is supposed to be on one line, first confirm that no record contains an intentional internal line break. Do not remove duplicates just to make the count look right: a repeated record can be either a genuine duplicate or an intended repeated event.
For data work, decide whether you need characters or bytes before changing the text. Replacing an accented name merely to reduce bytes may damage the data. A better solution can be to store the original correctly or reduce unrelated text. The counter reveals the size; it does not decide what information is acceptable to discard.
Common surprises and how to resolve them
''Two counters disagree
Compare an identical source rather than two separately copied versions. Check leading and trailing spaces, line endings, smart punctuation, nonbreaking spaces and headings. If the source is identical, compare the definitions. One tool may count UTF-16 code units, another Unicode code points, and another user-perceived characters. Word boundaries can also vary. Choose the method required by the receiving system, and record the rule if you are sharing a result with a team.
The text looks short but uses many bytes
Look for non-ASCII scripts, accented characters and emoji. These are legitimate content, but UTF-8 may use multiple bytes for each code point. A byte limit is a storage constraint, not a visual length limit. If the destination enforces bytes, test its validation with the final text. Do not use the character result as a substitute.
The line count seems too large
Text copied from narrow columns often contains hard breaks at the ends of visual lines. A blank line between paragraphs adds another break as well. Use a line-break cleanup tool only after deciding which breaks carry meaning. Poetry, addresses, code and lists may require their original line structure. Recheck the cleaned text for joined words before using its new count.
Large entries may take longer on a device with limited memory. If the input reaches the 100,000-character boundary, work with meaningful sections and label their totals. Summing counts can be appropriate for independent paragraphs, but segmentation at the boundary can change a word or sentence count. Keep boundaries at complete paragraphs rather than cutting through a word.
Practice: audit a mixed-language form response
Consider a form response containing an English paragraph, an accented name, a short phrase in another script and an emoji. Start by counting the exact plain text version you intend to submit. Record the Unicode character total and UTF-8 byte total separately. They describe different properties, so do not write only “length” in your notes. If the form gives no definition, test a small sample there before investing time in cuts that may be unnecessary.
Use a short reference sample to investigate a discrepancy. First enter an ordinary ASCII word, then add a space, then add the accented name, and finally add the emoji. Note which metric changes and by how much. This is more informative than repeatedly pasting the whole response and trying to infer the rule from a large total. The test should use harmless sample text rather than private information you do not need to expose in the destination.
Visually identical accents can be stored differently. One form may use a single precomposed code point, while another uses a letter followed by a combining accent. The text can look the same but produce different code point and byte counts. This counter does not promise to normalize those forms into one representation. For an exact data comparison, preserve the original and use the normalization rule required by the system, rather than deleting marks from a person's name.
Line endings can also affect byte comparisons between environments. A browser's pasted text, an exported text file and a server's stored string may not use the same newline representation. The displayed UTF-8 count describes the text supplied here. If a storage limit is critical, validate the final stored or transmitted representation in the actual system. Do not assume that a text editor's file size includes exactly the same material as the counter.
For a language without routine spaces between words, a space-only count is especially unhelpful. The browser's available segmentation can provide a better practical result, while the fallback remains approximate. If a publication defines word counts for that language, use its method. The counter should support your editing process, not replace a language-specific rule that the destination explicitly supplies.
After editing, paste the final response into the form and read the complete preview. Check that the beginning and end survived, paragraph breaks are sensible and the destination accepts the value. Save that accepted version with the rule you used. A count taken from an earlier draft or from a version without the final signature is not evidence that the submitted text met the limit.
Local processing and a reliable review
This tool carries out its operation in your browser. It does not send the values you enter to a remote processing service, and it does not need an account to produce a result. The page still runs within your device and browser environment: anyone with access to your screen, an exported file, or a copied clipboard value may be able to read that material. Choose input that you are allowed to handle on the device you are using.
The practical input limit for this tool is 100,000 text characters. A limit is a boundary, not a promise that every device will handle the largest possible entry at the same speed. Other tabs, low available memory, browser extensions and an old browser can affect responsiveness. If the page appears busy, allow the operation to finish before repeating it. When a large text task can be divided safely, try a small representative sample first and then process clearly labelled parts.
Keep your source separately until you have checked the output. A browser result can be useful and still be unsuitable for the final place where you intend to use it. The receiving form may have different limits, a house style may need a manual edit, or a document may require facts that no mechanical conversion can infer. Compare one simple case by hand, then inspect a case near the boundary that matters to your work.
For a strict submission, use this counter while drafting and then verify the complete final text in the receiving system. That last check connects the useful local measures with the actual rule your work must satisfy.
Frequently asked questions
Is a word always separated by spaces?
No. Word boundaries depend on language, punctuation and the segmentation method available in your browser. Intl.Segmenter is used where supported, with an approximate regular expression fallback otherwise. Treat the count as a practical measure rather than an authority on every compound, symbol or script. A destination with a strict rule may count the same text differently.
Does the character count treat an emoji as one character?
It counts Unicode code points, which need not match visible emoji. Some emoji are single code points, while a family, flag or modified emoji can use several. A visual character count based on grapheme clusters is a different measure. If a form limits characters, compare a short emoji sample in that form before assuming the same counting rule.
Why are characters and bytes different?
Characters describe text units; bytes describe the UTF-8 encoding of those units. Basic ASCII usually needs one byte per character, while many other characters need multiple bytes. The byte total is useful for a system with an explicit UTF-8 storage limit. It does not measure the eventual size of a Word document, PDF or other file with formatting and metadata.
Are line wraps counted as new lines?
Only actual line breaks in the text create logical lines. The input can wrap visually because the browser window is narrow without changing the underlying count. If you copied from a PDF or a column layout, those visible wraps may have become real breaks during copying. Inspect the source or try a small sample to distinguish the two situations.
Is the sentence count exact?
No. It is an approximation based on textual boundaries and punctuation. Abbreviations, initials, decimals, dialogue and repeated punctuation can create ambiguous cases. Use it to get a rough sense of structure, then read the passage when an exact sentence total matters. A teacher or editor may apply a rule that a mechanical counter cannot infer.
Does this count include headings and references?
It includes every part of the text you paste. The tool cannot recognize which sections your assignment or publication excludes. For a rule that excludes references, count the main text separately. Save the two totals with clear labels if you need to report them. Remove page headers and navigation text accidentally copied from a webpage.
Can I count text without uploading a file?
Yes. Paste plain text directly into the input. The calculations run locally in the browser rather than sending the passage to a remote counting service. Formatting from a source document may not survive a plain text paste, but visible words, punctuation and line breaks can remain. Check the pasted content before treating the results as final.
What does without spaces mean for unusual whitespace?
Whitespace is more varied than an ordinary keyboard space. Tabs, line breaks and nonbreaking spaces can affect what appears blank and how counts differ. Use the two character results to compare the supplied text, and inspect unusual copied material if a number is unexpected. The receiving service may define an excluded space differently, so its validation remains important.
Why did copying from a PDF change my word count?
PDF text extraction can insert line breaks, split words, omit spaces or repeat headers. The counter measures the extracted text as pasted, including those changes. Read a few paragraph transitions and check any hyphenated line endings. Repair extraction errors only when you can compare them with the source, then run the count again.
Can I use this for a social media character limit?
It can help estimate length, but a platform may apply its own rules for links, emoji or special content. Compare the final text with the platform composer before posting. A plain character count does not know whether a service shortens URLs or assigns them a fixed length. Keep the platform preview as the final practical check.
How much text can I paste?
The input limit is 100,000 characters. Large inputs also depend on your browser and available memory. If you need to divide a longer document, split it at complete paragraph boundaries and label each part. Adding separate totals is simplest when the parts are independent; cutting through a word or sentence can alter segmentation at the join.
Will changing case change the counts?
It can. Most simple English letters stay the same length when changed between uppercase and lowercase, but Unicode case mappings can alter the number of code points or bytes in some languages. Recount the actual converted text rather than assuming the previous totals still apply. A case conversion can also damage names or codes, so review meaning separately.
Can this tell me how long a speech will take?
The tool measures text rather than predicting a speaker. Speaking rate changes with pauses, audience, language and delivery style. A word count can support your own estimate, but rehearse the actual speech and time it for a reliable duration. Do not treat an unmeasured words-per-minute assumption as a precise result from the counter.
Does the tool check grammar or originality?
No. A count does not evaluate grammar, factual accuracy, quality or plagiarism. It reports structural measures of the supplied text. Use a human review or an appropriate separate process for those questions. A passage can meet every length target and still need editing for clarity, attribution or correctness.
Why did my saved text file have a different byte size?
A saved file may use another encoding, different newline characters, or extra markers and metadata. This tool reports UTF-8 bytes for the supplied text. Check the file encoding and line ending settings in the editor used to save it. A rich document format also contains structure and formatting beyond the text itself.
What should I check just before submitting?
Count the exact final version, confirm which sections belong in the rule, and paste it into the destination. Check that no paragraph was lost and that the destination accepts the length. If there is a mismatch, compare counting definitions and invisible whitespace before removing useful content. Keep the final accepted text with the reported total for reference.
Useful next steps
Choose a related tool when its operation matches the next part of your task. Check the result at each stage so a small source mistake does not carry into the final output.