Online text tools
This category holds 6 online text tools for working with raw content: counting words, characters and reading time, transforming strings across uppercase, camelCase or slug form, comparing two versions line by line, sorting lines alphabetically or naturally, removing invisible duplicates, and escaping text for HTML, JSON, SQL or regular expressions.
They serve writers and programmers alike. A writer uses them to trim a meta description to 160 characters or review keyword frequency; a developer uses them to clean an email list before importing it, to work out why two identical-looking lines are not deduplicated (invisible spaces, CRLF endings, homograph Unicode characters), or to escape a string correctly before dropping it into a template. All processing is local, which makes them safe for internal content.
Tools in this category
Word Counter
Count words, characters and lines in text
String Utilities
Reverse, shuffle and manipulate text strings
Text Diff
Compare two texts and show differences
Line Sorter
Sort text lines alphabetically
Duplicate Remover
Remove duplicate lines from text
Text Escaper
Escape and unescape special characters
Frequently asked questions
How many characters should a meta description have?
Between 150 and 160 characters: Google truncates anything longer and appends an ellipsis. The title is best kept between 50 and 60. The word counter shows a live count so you can tune both before publishing.
Why are two identical-looking lines not detected as duplicates?
There is almost always an invisible difference: trailing spaces, a non-breaking space instead of a normal one, CRLF line endings against LF, or Unicode characters that render identically but carry different codes. Turning on the trim and normalisation options catches them anyway.
Is escaping text enough to prevent injection attacks?
It is a necessary layer but never the only one. Each context demands its own escaping (HTML, attribute, URL, JavaScript, SQL) and picking the wrong one leaves the hole open. For SQL always use parameterised queries, and against XSS combine auto-escaping templates with a Content Security Policy.