About TextBench
TextBench is an independent collection of text utilities: a counter, a case converter, a line cleaner, a JSON formatter and an encoder. Everything runs in the browser. The guides exist because the tools are only as useful as the rules behind them.
What the site is for
The tools grew out of a narrow frustration: text utilities are everywhere, and almost all of them upload your text to a server, want an account, or wrap a one-line function in a page of advertising. The text people paste into these tools is often the least publishable text they have — an unpublished draft, an interview transcript, a customer list, an internal spec, a half-finished translation.
A word counter does not need a server. Neither does a case converter, a deduplicator, a JSON formatter or a slug generator. They need a textarea and a few hundred lines of JavaScript. So that is what this site is: static HTML, one stylesheet and one script, with no network request after the page loads.
Who runs it
TextBench is run by a small independent team — a technical writer and a front-end developer who both work with plain text daily and kept rewriting the same throwaway scripts. There is no company behind it, no editorial board and no investor. That also means there is no content marketing department: pages exist because a tool or a rule needed explaining, not to fill a calendar.
How the tools are built and tested
The site is deliberately plain. No framework, no build step, no CDN, no fonts fetched from a third party, no analytics script. assets/app.js holds every function the tools use, and it makes no network calls of any kind — you can confirm that in the browser's network panel while using the site.
The counting, case, line, encoding and JSON logic is covered by a Node test file that asserts known results: that 你好世界 survives a Base64 round trip, that Hello World becomes hello-world, that empty lines and padding are removed before comparison, and that a malformed JSON document produces a message naming a line and a column rather than a stack trace. When a bug is fixed, a test is added for it.
How the guides are written
Each guide starts from one concrete problem and explains the mechanism rather than a list of clicks, because the mechanism is what transfers to the next tool. Where a rule is a convention rather than a requirement — Title Case small words, for instance — the text says so and names the conflicting conventions instead of presenting a preference as a fact.
There are no invented numbers on this site: no user counts, no percentage improvements, no case studies we cannot show. Statements about standards (RFC 8259 for JSON, UTF-8 for Base64 and URLs, Google's URL guidance for slugs) are checkable, and they are the only claims presented as authoritative.
Corrections
If a guide is wrong, or a tool returns something you can prove is incorrect, write to the contact address with the page and a minimal example. Corrections are applied to the page itself, not buried in a changelog, and the "last updated" line moves.
How the site is funded
TextBench is free and has no paid tier. Running costs are covered by advertising served by Google AdSense once the site is approved for it; the slots are marked "Advertisement" and are not personalised by anything you paste, because nothing you paste is transmitted. Advertising has no influence on which tools or guides are published, and there are no sponsored tools or affiliate links on the site.
Written by the TextBench team. Last updated November 19, 2026.