ABOUT

About TheAllTools

Why this site exists

Most "free" online tools aren't really free of cost to you — they're free of money but not of your data. You upload a photo to compress it and it sits on someone's server. You paste a password idea into a "generator" and have no way to know whether it was logged. You need to format one JSON blob and get walked through an account signup first. TheAllTools started from a simple annoyance with that pattern: a lot of these tasks are simple enough that a browser can do them entirely on its own, with no server round-trip and no account required. So that's what this site does — one utility per page, running in your browser, with the source of truth being whatever your device can compute.

How the "runs locally" part actually works

This isn't just a slogan — it's a specific technical choice that shapes every tool on the site. Text tools (word counter, case converter, diff checker) use plain JavaScript string operations on whatever you type into a textarea; the text never leaves the DOM node it's sitting in. Image tools (compressor, resizer, watermark adder, favicon generator) use the browser's Canvas API — the image is decoded into a canvas element, transformed pixel-by-pixel or re-encoded, and the result is offered back as a downloadable file, all without a network request. Developer tools like the hash generator use the Web Crypto API (SubtleCrypto) built into every modern browser, the same cryptographic primitives your own code would call. The password generator uses crypto.getRandomValues() rather than Math.random(), because the latter is not cryptographically secure and shouldn't be trusted for anything security-sensitive. The practical upshot: close the tab, and there's nothing to clean up, because nothing was ever sent anywhere to begin with.

What's on the site

Tools are organized into seven categories, each covering a cluster of related everyday tasks:

How tools get chosen, built, and maintained

New tools are added based on two things: what's genuinely useful often enough to justify a dedicated page, and what actually fits the browser-only model — a tool that fundamentally requires a server (like a huge batch-processing job or a database lookup) doesn't belong here. Priority tends to go to tools that solve a task people hit repeatedly (checking word count, converting a color code) over novelty tools that get used once. Existing tools get revisited periodically to fix reported bugs, tighten up edge cases (for example, making sure a hash generator handles empty input or unicode correctly), and improve the explanatory content on each page so it's actually useful rather than filler. This is genuinely one person's project, run and maintained independently — there's no team, no outside investors, and no roadmap beyond "build the next useful thing and keep the existing ones working."

Get in touch

Found a bug, have an idea for a new tool, or need to reach out for a business inquiry? Visit the contact page for the details on what to include and how to get a useful response.