Online Text Tools in 2026: Word Count, Case Conversion, Cleaning, Slugs and Readiness — Free and in the Browser

The single most-asked text question — how many words is this — has no universal answer, because a word is a convention, not a fact. Is mother-in-law one word or three? Is 2026 a word? Does a bare URL count? Different counters draw the line differently, which is why the same passage reads 1,480 in one tool and 1,510 in another. The honest approach is to pick one counter, learn its rules and use it consistently — the word counter reports words, characters, characters without spaces, sentences, paragraphs and a reading-time estimate from a single definition applied the same way every time.

For limits, the number that matters is almost never words. An assignment says 1,500 words but the real constraint is the box it is pasted into; a form field caps at 500 characters, and a title tag caps at a pixel width that tracks characters. When a ceiling is about space, count characters, not words — the word counter gives both, and the same counting discipline is what makes a title fit the search-result budget in the title tag and meta description guide. Reading time is a friendlier cousin of both: a rough minutes-to-scan figure that helps you judge whether a page is too long for its purpose.

Most people reach for a case converter expecting one button and are surprised there are several genuinely different ones. Uppercase and lowercase are the obvious pair, but sentence case (only the first letter of each sentence capitalised) and title case (each major word capitalised) are different instructions with different rules. The case converter handles all of them, including capitalise-every-word, which looks like title case but is not: real title case leaves small words like of, and, the and a lowercase unless they open the title, so a headline that capitalises everything reads as amateur. The treatment of those small words is exactly the kind of detail a title carries in a search result.

Case is also where Unicode quietly breaks naive tools. Converting a Turkish word to uppercase follows different dotted- and dotless-I rules than English, and folding accents before or after upcasing changes the result. For everyday English content the case converter behaves exactly as you expect; when text mixes scripts, the safe assumption is that case is locale-sensitive, which is why related cleanups like removing accents deserve their own dedicated tool rather than a side effect of a case change.

The unglamorous majority of text work is turning pasted chaos back into usable data. A list copied from a spreadsheet has the same city entered a dozen times; a scraped page leaves double spaces and ragged line breaks; a set of names arrives unsorted. Three tools cover almost all of it: remove duplicate lines collapses repeated entries while keeping the first occurrence, text trimmer strips leading and trailing whitespace and collapses the extra spaces and blank lines that survive a copy-paste, and sort lines puts a list in order so duplicates become visible and adjacent — often you sort first, then de-duplicate, because sorting turns far-apart repeats into neighbours a de-duplicator handles cleanly.

The find and replace tool is the fourth corner of this job, and it is where a plain find-box stops being enough: swapping a misspelt brand across a document, normalising a hyphenated word to its closed form, or replacing a placeholder token before publishing. Used carefully it is a bulk editor; used carelessly it is how a short word inside a longer one changes at once. The discipline is to replace whole words and preview the count before applying — the same measure-twice habit that keeps a byte target from ruining an image in the image file size guide.

Some text transformations are not about tidiness but about producing a string that another system will accept. A URL slug has a precise shape — lowercase, words hyphen-separated, accents folded to plain letters, punctuation gone — and building it by hand is how you end up with a capital letter or a stray symbol in a permalink. The text to slug tool applies the contract directly, and the accent folding it does internally is the same job the standalone remove accents tool does on its own for legacy forms that reject non-ASCII characters.

Two more are pure web plumbing. Paste rich text into a plain-text field and you get a wall of markup; strip HTML tags removes the tags and leaves the human-readable text, the inverse of the HTML entity encoder, which escapes angle brackets and ampersands so they display as text instead of being interpreted as code — the thing you need when showing a code sample on a page. And when a layout needs a neutral stand-in before real copy exists, the lorem ipsum generator produces filler of exactly the length you specify so you can judge the space, not the sense.

Beyond counting and cleaning, a few text tools read the writing itself. The readability analyzer scores how hard a passage is to read — the familiar grade-level formulas that look at sentence length and syllables per word — which is genuinely useful when you are writing for a broad audience and want to know whether a paragraph has quietly become a wall of subordinate clauses. It is a signal, not a verdict: a high score can mean clear and can also mean simplistic, and specialist writing should not be flattened to please an index, any more than a health number should override how you actually feel.

Adjacent to readability sits the harder-to-formalise question of whether text sounds like a person or a machine. The AI text humanizer rewrites flagged passages toward more natural rhythm and phrasing. Treat output from any such tool the way you treat a calculator's answer here: as a strong first draft to review, not a finished result to ship unseen — the tools that show their working, whether a percentage formula or a readability score, are the ones you can actually verify.

Not every text tool earns its place on a daily job; a few exist for the moments you genuinely need them and nothing else will do. The reverse text tool flips a string backwards, which is not a party trick but the correct answer when a filename or code fragment must be read right-to-left, or when you need text that renders in reverse. The palindrome checker tests whether a phrase reads the same both ways, ignoring spaces, punctuation and case — the kind of one-off question a search box throws up that is annoying to verify by eye.

Everything on this list takes text and returns text, entirely inside the page, which makes them a clean fit for the reason the calculators and file tools on this site give: privacy. A draft, a client's copy, a scraped contact list, a document you are mid-editing on — pasting any of it into a server-side tool hands a readable copy of that text to someone else's machine, often logged, sometimes stored. A client-side tool does the work on your own device and the text never leaves it; there is no account, no upload, and you can confirm it yourself in the browser's Network tab.

For transformations this mechanical there is no reason for the data to travel, and the tools that keep it local are the ones you can use on sensitive text without a second thought. That is the same design principle behind the whole site: compute where the data already is, show the working, and let the Network tab prove nothing left.

Mapped to the questions that bring people here, the toolkit sorts itself out quickly, and the pattern is that each small job has a dedicated page that answers the exact phrasing rather than a single do-everything box.

• Essay, post or field length: the word counter for words and characters, and reading time for whether it is too long.
• Headline or label formatting: the case converter, with title case rather than capitalise-every-word for real headings.
• A list copied from a spreadsheet: sort lines, then remove duplicate lines, then trim the whitespace.
• Bulk corrections across a document: find and replace, with whole-word matching and a preview count.
• A clean permalink from a title: text to slug, lowercase, hyphenated and accent-free.
• A legacy form that rejects an accent or a symbol: remove accents, or the HTML entity encoder for special characters.
• Rich text pasted as markup: strip HTML tags to recover just the readable text.
• Filler before real copy exists: the lorem ipsum generator at the exact length you need.
• Is this too hard to read: the readability analyzer for a grade-level signal.