Free text tools
A set of everyday text utilities that run entirely in your browser. Find and replace words or regex patterns, sort lines and remove duplicates, compare two versions of a document with word-level diff highlighting, convert text between camelCase, snake_case and other naming conventions, count words and characters, generate lorem ipsum placeholder text, and check readability scores.
All processing happens locally in JavaScript, directly in your browser tab. The text you paste in is read by the page's script, and our servers are not involved at any point.
Read the complete text tools guide
Why text tools should not need a server
Most text jobs are small and frequent: counting words before a submission, tidying a pasted list, comparing two drafts, renaming a batch of identifiers. A server-based tool receives a copy of whatever you paste, and what happens to that copy afterwards depends on the service's retention policy. These tools do the same jobs with JavaScript running in the page.
For everyday text jobs the work is small enough that no server is needed in the first place. Counting words is a split on whitespace. Diffing two texts is a longest-common-subsequence comparison that runs in a Web Worker. Converting case is a handful of regular expressions over the input. None of it benefits from a round trip to a remote machine.
In-browser tools do the work where the text already is. The text you paste stays in the textarea, the result appears next to it, and our servers are not involved at any point.
How the text tools work
Every text tool on this site is a small JavaScript module. The word counter splits on whitespace and counts the resulting array. The diff tool uses a longest-common-subsequence algorithm to find the minimum set of insertions and deletions between two strings. The case converter applies a sequence of regex transformations to map between camelCase, snake_case, kebab-case, and similar conventions. The readability checker applies the Flesch and Flesch-Kincaid formulas to the sentence and syllable counts of the input.
None of this requires a network connection. The page loads once, the JavaScript runs in your tab, and the work happens in milliseconds. The CSP on every page sets connect-src 'none', so the browser would block any fetch, XMLHttpRequest, or WebSocket request anyway. That is a strong second layer, though not an absolute guarantee: CSP does not block every channel, such as navigating the page to another site.
In-browser text tools vs the alternatives
| Approach | Privacy | Cost | Best for |
|---|---|---|---|
| In-browser (this site) | Processed locally | Free | Quick counts, diffs, sorting and case changes |
| Online grammar and style checkers | Server-side | Free tiers, paid plans | Grammar and style suggestions on public copy |
| Word processors | Depends | Free or paid licence | Full document editing workflow |
For a one-off count, a quick diff, or converting some identifiers from snake_case to camelCase, in-browser is the obvious choice. For full editing and grammar checking on a long document, a word processor is the right tool. The two complement each other.
When to use these tools
- Editing a draft? Track changes between two versions with the diff comparison tool and keep an eye on length using the word and character counter.
- Cleaning up a copy-pasted list? Sort lines alphabetically and remove duplicates, then use find and replace with regex to normalise formatting.
- Renaming variables across a snippet? Switch identifiers between camelCase, snake_case, and other naming styles using the case converter.
- Mocking up a layout? Drop in placeholder copy from the Lorem Ipsum generator, then test how dense it reads with the readability score checker.
- Need a URL-safe slug for a blog post or filename? Convert any heading with the slug generator.
Frequently asked questions
- Are these text tools free?
- Yes. Every tool is free to use without an account, daily quota, ads or email signup. A few tools cap very large inputs to keep the tab responsive: the diff compares changed regions of up to 12,000 lines per side, and find and replace runs regex mode on up to 200,000 characters. Each tool page lists its limits.
- Is my text sent to a server?
- Every tool runs as JavaScript inside your browser tab. All processing is local, and our servers are not involved at any point.
- Can I sort a list and remove duplicates at the same time?
- Yes. Turn on Remove duplicates in sort lines, plus Trim whitespace or Remove empty lines if you need them. They are applied before the sort, so one pass gives a clean, ordered list. Duplicate matching ignores letter case.
- Will the diff tool handle large documents?
- Up to a point. The diff runs in a Web Worker in your browser. Lines that match at the start and end of both texts do not count toward the limit; the changed region between them is compared when it has at most 12,000 lines on each side and 1.5 MB in total, and a larger changed region is marked as not compared.
- Does the word counter match what desktop word processors count?
- Closely. Words are separated by whitespace, hyphenated terms count as one word, numbers count as words, and each Chinese or Japanese character counts as one word. Word processors apply slightly different rules to dashes, symbols and some punctuation, so totals for the same text can differ slightly. Character counts are shown both with and without spaces.
- Are readability scores accurate?
- The Flesch-Kincaid and related scores are widely used heuristics based on average sentence length and syllable count. They are not a substitute for actual reader testing, but they are widely accepted as a rough proxy.
- Can I use the case converter on identifiers in source code?
- Yes. The case converter handles camelCase, snake_case, kebab-case, PascalCase, UPPER CASE, lower case, and Title Case. It splits on existing case boundaries and separators, though note that acronyms are lower-cased rather than preserved (HTMLParser becomes htmlParser in camelCase).