10 text utilities you'll actually use every week
Changing case, removing duplicate lines, generating filler text, converting number bases and escaping HTML: the small jobs that keep coming back.
None of these jobs deserve a spreadsheet, a browser extension, or five minutes of a developer's time — they're thirty-second text fixes that keep showing up whether you work with data, code or content. That starts with turning a name column exported in ALL CAPS from a legacy system into something presentable with the case converter, and runs through deduplicating a mailing list before you import it. Here are ten, grouped by the problem each one solves:
- Switching between UPPERCASE, lowercase and Title Case
- Converting text to camelCase or snake_case
- Sorting lines and removing duplicates from a list
- Generating filler text (Lorem Ipsum), Latin or plain-English
- Converting between binary, octal, decimal and hexadecimal
- Encoding and decoding HTML entities
- Escaping code so a page displays it instead of running it
- Counting words and characters against a hard limit
- Comparing two versions of a text line by line
- Turning a title into a valid URL slug
All of it runs in your browser — nothing you paste, including text with real names, emails or config values, ever leaves the tab.
Changing case and text format
The most common trigger: a legacy export or a database dump lands with every field in ALL CAPS, and pasting that straight into a report or an email looks sloppy. The case converter fixes that and more — UPPERCASE, lowercase, Title Case, camelCase and snake_case, all from the same text box.
The detail most people get wrong: Title Case isn't "capitalize every word." Standard style guides (AP, Chicago, MLA) keep short articles, coordinating conjunctions and prepositions — "a", "the", "of", "and", "in" — lowercase unless they open or close the title. "The Lord of the Rings" is correct; "The Lord Of The Rings" looks more consistent but is wrong by every major style guide. For developers, camelCase and snake_case solve a different problem: renaming keys when an API returns customer_name and your JavaScript expects customerName, or the reverse when mapping into a snake_case database schema.
Sorting lines, removing duplicates, cleaning lists
Before importing a mailing list into an email tool or feeding a batch of URLs to a crawler, deduplicating it first avoids emailing the same contact twice or wasting crawl budget on a repeated URL. The text cleaner sorts alphabetically, strips repeated lines, and removes stray blank lines — the kind that sneak in when you copy a list out of a PDF — in one pass.
To confirm exactly how many lines or words survived the cleanup, the word counter gives you an instant count, which also doubles as a quick check against a character limit on a form field.
Generating filler text for layouts
When a design is ready but the final copy isn't, dropping in obvious placeholder text keeps a stakeholder from mistaking a draft for the finished page. The Lorem Ipsum generator produces filler text in classic Latin or plain English, by word count, sentence count or paragraph — however much space you need to fill.
The Latin version exists for exactly that reason: a paragraph of Latin obviously reads as filler, while a plausible-sounding English paragraph can slip through a rushed review and end up published by accident.
Converting binary, octal, decimal and hexadecimal
A Unix file permission like chmod 755 is really three octal digits encoding read, write and execute for owner, group and everyone else. A color like #1a73e8 is hexadecimal. A status flag in a log file sometimes shows up in raw binary. The number base converter translates between binary, octal, decimal and hex — or any base in between — without doing the arithmetic by hand.
One stable technical fact worth knowing: each hex digit represents exactly 4 bits, so two hex digits cover a full byte (0–255) — which is why web colors are written as six hex digits, two per channel for red, green and blue.
Encoding HTML entities and escaping code
Pasting an HTML snippet into a blog post, a rendered README, or a CMS field carries a specific risk: the browser sees <div> and tries to open a tag instead of showing you the literal text <div>. The HTML entity encoder converts those characters into their safe entities (<, >, &) and also generates JavaScript string escapes, so text with quotes or line breaks can be dropped into code without breaking the syntax.
The detail that matters: escaping < and & is exactly what separates displaying code from runningit. It's the same underlying reason a form that fails to escape user input is vulnerable to XSS — this tool just applies by hand the transformation a web framework should be applying automatically.
Four more worth bookmarking
These come up less often than the five above, but they're worth keeping in the same tab group:
- Compare text: see exactly what changed, line by line, between two versions of a contract, a config file or a paragraph before you overwrite one with the other.
- Slug generator: turn an article title into a clean, URL-safe slug, accents and special characters stripped, ready to publish.
- Regex tester: validate a regular expression against real sample strings before it ships in code, instead of debugging it blind.
- Word counter: check the exact length before a hard character limit — a meta description, a tweet, a form field.
Frequently asked questions
Do these text tools upload my content to a server?
No. Case conversion, deduplication, base conversion and HTML escaping all run in your browser — nothing you paste in is transmitted anywhere. That matters because the text people paste into these tools is rarely a toy example: it's often a real customer list, a config file, or a snippet with personal data.
Isn't Title Case just capitalizing every word?
No, and that's the most common mistake. Standard style guides (AP, Chicago, MLA) keep short articles, coordinating conjunctions and prepositions — "a", "the", "of", "and", "in" — lowercase unless they open or close the title. "The Lord of the Rings" is correct Title Case; "The Lord Of The Rings" is not, even though it looks more consistent.
When would I need camelCase or snake_case instead of Title Case?
When you're renaming keys between systems that follow different naming conventions — a REST API returning "customer_name" that a JavaScript codebase expects as "customerName", or the reverse when mapping into a database that expects snake_case. Doing that by hand, field by field, is where typos creep in.
What's a slug and why does it need to drop accents and special characters?
A slug is the URL-safe version of a title: lowercase, no spaces, no punctuation, words joined by hyphens. Accented characters and symbols can get percent-encoded into ugly, broken-looking URLs on some platforms, so they're normalized away before publishing.
Why does HTML need < and & escaped before you display it as text?
Because a browser treats any < it encounters as the start of a tag. Paste raw HTML into a page without escaping it and the browser tries to render it instead of showing it as text — and if that HTML comes from user input, that's the exact mechanism behind an XSS attack. Escaping < to &lt; and & to &amp; is what turns executable markup into inert, displayable text.
Is there a size limit on the text or lists I can process?
No hard limit — since everything runs locally, the ceiling is your device's memory, not a service quota. Lists of a few thousand lines or a couple of megabytes process instantly; very large files may take a moment longer, but there's no signup and no usage cap.
Related tools
- Change case — UPPERCASE, lowercase, Title Case, camelCase, snake_case.
- Sort and deduplicate lines — Clean up text lists in one pass.
- Lorem Ipsum generator — Filler text in Latin or plain English.
- Number base converter — Binary, octal, decimal, hex, any base.
- HTML entity encoder — HTML entities and JavaScript escapes.
You might also like: 13 privacy-first developer tools and the best developer tools of 2026.