About TextKit
Text Is Everywhere, Tools Are Scattered
Text is the most common thing a computer handles, and the tools for working with it are everywhere and nowhere. The case converter is on one site, the JSON formatter on another, the diff tool on a third, and the regex tester on a fourth. You clean up text copied from a PDF in one tab, dedupe a list in another, encode a URL in a third — and by the time you're done you've cycled through six URLs and lost track of which one had the result you needed.
TextKit exists because text work shouldn't require tab gymnastics. Twenty-nine tools live in one workspace, share one clipboard model, and — when a single tool isn't enough — chain together into a pipeline that runs them in sequence.
29 Tools, One Workspace
The tools are grouped by what you're trying to do to the text, not by the algorithm behind it:
Case & transform 🔤
Case converter (UPPER, lower, Title, Sentence) and text reverse; sort lines, find-and-replace (with regex), add line numbers, and wrap/unwrap to a column width.
Clean 🧹
Remove duplicate lines, collapse extra spaces, strip empty lines, and remove line breaks — the cleanup crew for text mangled by a PDF copy or a spreadsheet export.
Encode 🔐
Base64, URL, HTML entity, hex, binary, and Morse encode/decode, plus a hash generator (SHA-1/256/384/512) for checksums and content fingerprints.
Compare & count 🔢
A character-level text diff that highlights what was added, deleted, or changed; and a word counter with sentence, paragraph, and reading-time stats.
Format & generate ✨
Markdown to HTML, JSON formatter, CSV ↔ JSON converter; plus Lorem Ipsum, password, slug, UUID, and text repeater generators.
Extract 📥
One tool that pulls every email address and URL out of a block of text — deduped, ready to paste.
Pipeline: Build Your Own Text Workflow
Single tools solve single steps. Real text work is rarely one step — it's "clean up the line breaks, dedupe, sort, then encode for a URL." Doing that by hand means four tools, four copy-pastes, and four chances to grab the wrong buffer.
TextKit's pipeline editor lets you stack tools into a repeatable workflow: add the steps in order, configure each one, run it once, and get the final output. The whole pipeline serializes into a shareable URL, so the cleanup recipe you built for one export can be handed to a teammate — or bookmarked for next month's report. It's the difference between a tool and a process.
Privacy by Design
The text you process here is often text you'd rather not share: draft copy, internal notes, configuration files with real values, log lines with user data. TextKit does all of its work in your browser. There's no server that receives your input, no analytics on what you typed, no history kept across visits. Paste a paragraph, run a diff, generate a hash — the data stays in the tab and is gone when you close it. The specifics are in the privacy policy.
Built for Writers and Developers
TextKit sits at the overlap of two audiences who handle text all day but rarely share tools. Writers get case conversion, word counts, Markdown preview, and text diff for tracking edits. Developers get Base64, URL and HTML encoding, JSON formatting, regex testing, UUID and password generation, and hash checksums. The pipeline is where the two audiences meet — a writer's cleanup routine and a developer's encoding chain are both, at bottom, a sequence of text operations. Built with Astro for fast static pages and Vue for the interactive tools.