Text and Data Tools: Counts, Encodings and Safe Exports
Practical examples for counting words, converting Unicode text, handling CSV safely, and avoiding encoding mistakes.
Word counting depends on the definition
A “word” may mean a sequence separated by whitespace, a linguistic token, or a character group recognized by a language-specific parser. The Word Counter uses whitespace separation, which works predictably for many space-delimited texts but can undercount scripts written without spaces.
For example, the text red blue has two whitespace-separated words; the string red-blue is one. Punctuation and emoji can affect character and sentence estimates. Compare the tool's definition with your teacher's, client's or publishing system's requirements before relying on a target count.
Characters, Unicode code points and visible symbols
A code point is not always the same as a visually perceived character. Some emoji are built from several code points joined together; accented characters can be one precomposed code point or a letter plus a combining mark. A browser-based character counter may therefore report a different value from a social platform's limit counter.
When precise message-length restrictions matter, test with the exact platform that will receive the message. Use Character Counter for estimates and examples, not as a substitute for the destination's official validation rules.
Base64 is an encoding, not encryption
Base64 represents bytes using ASCII characters. Anyone can decode it; it does not make passwords, payment details or private text safe to disclose. Similarly, URL encoding handles reserved characters in URL components, but does not make a hostile URL safe to open.
Spreadsheet safety: values that look like formulas
When a CSV contains a field such as =2+2, some spreadsheet programs may treat it as a formula. A safe conversion should preserve text where practical. The site's CSV to Excel tool intentionally stores cells as literal text, which helps protect data integrity but means dates and sums might need explicit formatting after export.
Example source:item,code,amountNotebook,00123,19.50Marker,=2+2,4.25
After converting, verify that 00123 still has its leading zeros and that =2+2 does not execute. Then inspect delimiters and accented characters; CSV does not carry one universal encoding declaration or column type schema.
Simple text cleanup is not semantic editing
Text Cleanup and Simple Rewrites applies predefined rules. It cannot verify meaning, style, citations or originality. Before submitting a document, compare each changed sentence against the source. An automatic replacement that is grammatical in one context can be wrong in another.
A repeatable quality check
- Keep a plain-text backup of the input.
- Run the smallest operation needed: count, sort, case change, encode or export.
- Check unusual characters, line endings, leading zeros and quotation marks.
- Open the exported file in the receiving application.
- Compare a few representative lines against the original and verify the intended meaning.
Frequently asked questions
Why is my word count different in Word or Google Docs?
Different software can split contractions, punctuation, emoji and non-space-delimited scripts differently.
Is Base64 suitable for secrets?
No. It is a reversible representation. Use proper encryption and secure transmission for sensitive information.
Why are all Excel cells text?
The converter favors preserving literal content, including leading zeros and values that might otherwise execute as formulas.