A set of everyday text utilities that run entirely in your browser. Compare two versions of a document with inline 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 without leaving your browser tab.
All processing happens locally in JavaScript, directly in your browser tab. The text you paste in is read by the page's script and never sent to any server.
Read the complete text tools guide
Writers and editors handle text that nobody else should see yet. A draft of a book chapter. A draft that cannot leave the organisation yet. Internal material before it goes out. A press release under embargo. The content has value and often has obligations attached to it. Pasting any of it into a free online word counter or grammar tool means handing a copy to a third party whose retention policy you have not read.
For everyday text jobs the work is small enough that no server is needed in the first place. Counting words is a one-line function. Diffing two strings is a well-understood algorithm with mature JavaScript libraries. Converting case is regex on the input. None of it benefits from a round trip to a remote machine.
In-browser tools just do the work where the data already is. The text you paste stays in the textarea. The result appears next to it. When you close the tab everything is gone.
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 setsconnect-src 'none', so the browser would block any outbound fetch anyway, providing a hard guarantee that nothing leaks.
| Approach | Privacy | Speed | Best for |
|---|---|---|---|
| In-browser (this site) | All local | Instant | Sensitive drafts, ad-hoc checks |
| Online grammar and style checkers | Server-side | Fast | Grammar and style suggestions on public copy |
| Word processors | Depends | Fast | 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.