About Tooltrusty

Why this site exists

Tooltrusty started from a habit that turned out to be hard to defend. Like most people who work with files and text all day, I kept a folder of bookmarks to free online utilities — a JSON formatter, an image compressor, a word counter — and I used them without thinking much about what happened after I pressed the button.

What happens, on most of those sites, is an upload. The file or the text goes to a server, gets processed there, and comes back. Somewhere in that round trip your content sat on hardware you do not control, was probably written to disk, and may well have been logged. For a photo of a cat that is a non-issue. For a client contract, a screenshot of an internal dashboard, an API response with a customer's details in it, or a draft you have not published yet, it is a real problem — and it is precisely those files that people run through free online tools, because those are the files that need converting and cleaning.

Modern browsers removed the need for any of it. The File API can read a file the user selects, the Canvas API can decode, transform and re-encode an image, and JavaScript can handle text transformations far faster than a network round trip. All of the work that these tools were sending to a server can be done in the tab the user already has open. Tooltrusty is that idea applied consistently to 90 tools.

How the tools actually work

When you open a tool page, the browser downloads the HTML, one shared stylesheet, one small shared script and a short block of JavaScript written for that specific tool. That JavaScript is the tool. When you paste text, it is held in a variable in your browser's memory. When you choose an image, the browser reads it with the File API and draws it into a canvas element, where it can be resized, re-encoded, watermarked or inspected. When you save the result, the browser builds the new file locally and hands it to your download folder.

At no point is there an HTTP request carrying your content, because there is no endpoint on this site that accepts one. Tooltrusty is a set of static files. There is no database, no upload directory and no processing queue, and adding one would mean rebuilding the site from scratch.

You can verify this yourself in about thirty seconds, and I would encourage it rather than taking my word for it:

1. Open any tool page and let it finish loading.
2. Disconnect from the internet — turn off Wi-Fi or switch on airplane mode.
3. Use the tool. It will keep working, because everything it needs is already in the page.
4. If you want to go further, reconnect, open your browser's developer tools, switch to the Network tab, and use the tool again. You will see no request carrying the text or file you just processed.

What this site does collect

Being honest about this matters more than claiming perfection. Tooltrusty itself has no accounts, no cookies of its own and no analytics that identify you. However, this site is supported by advertising through Google AdSense, and ad networks do set cookies and collect data about the browser viewing the page in order to serve and measure ads. That is data about your visit — the page you are on, your approximate location, your device — and it is entirely separate from the content you put into a tool, which never leaves your device and therefore cannot be collected by anyone.

The Privacy Policy sets out exactly what those third parties collect and how to opt out. If the distinction is not clear, the short version is: advertisers can see that you visited the image compressor; nobody, including me, can see the image you compressed.

How the site is built

Tooltrusty is static HTML, one CSS file and vanilla JavaScript. There is no framework, no build step in the browser and no third-party analytics library. Each page loads only the code its own tool needs, which is why a text tool does not download image-processing logic. The result is pages that typically weigh well under 100 KB and work on an old phone over a slow connection.

Every tool page carries a written explanation, a worked example and a short FAQ. That is partly for search engines, but mostly because a tool that does not explain its own assumptions is hard to trust — particularly the calculators, where the answer depends entirely on which formula was chosen and which simplifications were made. Where a calculator makes an assumption, the page says so.

Limits and honesty

These are utilities, not professional software. The calculators produce estimates from a small number of inputs and are not a substitute for advice from a qualified professional — the Disclaimer covers this in detail. The image tools re-encode through the browser's own codecs, which are excellent but not identical to a dedicated compression suite. The minifier uses safe pattern-based rules rather than a full parser, so it will not match a build-tool minifier's output. Where a tool has a limitation worth knowing about, it is written on that tool's page rather than buried here.

Get in touch

If a tool gives a wrong answer, breaks on a particular file, or is missing an option that would make it genuinely useful, I would like to know. Bug reports that include the browser and the kind of input that caused the problem are the most useful. You can reach me through the contact page or directly at muhammadtanzeel935@gmail.com.

Last updated: 6 September 2026