Why Toolew runs your tools in the browser

When we started building Toolew, we set one rule that shaped almost every technical decision: if a tool can do its job on your device, it should never send your data to us. Today the large majority of Toolew’s tools follow that rule. This article explains how that works, why it matters, and where the exceptions are.

The traditional model: upload, process, download

Many online tools follow a simple pattern. You choose a file, it is uploaded to a server, the server processes it and you download the result. This model made sense when browsers were limited, but it has real drawbacks:

• Privacy. Your contract, payslip, passport scan or source code now sits on someone else’s computer. Even with good intentions, files can be logged, cached, retained longer than expected or exposed in a breach.
• Speed. Uploading a 200 MB video on a typical home connection can take longer than processing it.
• Cost and limits. Servers cost money for every file processed, which is why many services impose file-size caps, daily limits or queues.

What modern browsers can do

Browsers have quietly become powerful computing platforms. A few technologies make local tools possible:

• The File API lets a page read a file you select or drop, without uploading it. The data stays in the browser’s memory.
• Canvas and createImageBitmap give access to the same image decoders and encoders the browser uses to display pictures. Toolew’s Image Compressor uses them to resize and re-encode photos to JPEG, PNG or WebP.
• WebAssembly (Wasm) runs code compiled from languages such as C, C++ and Rust at near-native speed. This is how a full build of FFmpeg, the industry-standard video toolkit, can run inside a web page for tools like Video to GIF.
• The Web Crypto API provides fast, audited implementations of hashing and encryption algorithms, used by our hash, checksum and encryption tools.
• Web Workers run heavy work in the background so the page stays responsive while a large file is processed.

When you merge documents with Merge PDF, for example, the open-source pdf-lib library reads each file in your browser, copies the pages into a new document and hands you the result as a download created on your device. Nothing travels over the network except the web page itself.

How you can verify it

You do not have to take our word for it. Open your browser’s developer tools (F12 on most desktop browsers), switch to the Network tab and use a local tool. You will see the page and its scripts load, but no request carrying your file. For tools that are heavier, such as video conversion, you will see a one-time download of the processing engine from a public CDN, which is then cached by your browser; your video is still processed locally.

The exceptions, and why they exist

Some tasks genuinely need information from the internet. We label every such tool on its page, and they send only what the task requires:

• DNS lookup and propagation checks ask public DNS-over-HTTPS resolvers for the domain you enter.
• Currency conversion fetches daily reference exchange rates.
• The Pwned Password Checker sends only the first five characters of your password’s SHA-1 hash, a technique called k-anonymity, so the password never leaves your device.
• What Is My IP has to ask a server what address your request came from.
• Speech to Text, where supported, uses your browser’s built-in speech service, which in some browsers sends audio to the browser vendor.

Our own servers receive only what you deliberately send: feedback and contact messages, and the projects you choose to save if you create an account. These are covered in our Privacy Policy.

Speed and limits

Because processing happens on your device, speed depends on your hardware rather than a shared queue. A recent laptop compresses a batch of photos in a few seconds. Phones are slower for heavy tasks such as video conversion, and very large files are limited by available memory rather than an arbitrary cap. For most everyday jobs, local processing is noticeably faster than uploading.

Works offline

Toolew is a progressive web app. After you have opened a tool once, its code is cached, and because the work happens on your device, many tools keep working with no connection at all, which is useful on flights, in places with poor coverage or simply to save mobile data. You can also install Toolew from your browser menu so it opens like an app.

Large files and integrity

Local processing is also useful for verifying files. The File Checksum Calculator reads a file in chunks and computes SHA-256 or other hashes as it goes, so you can verify a multi-gigabyte download against the checksum published by its developer without uploading anything.

What this means for you

• You can use Toolew for sensitive documents with much less risk than upload-based services.
• There are no artificial file-size limits for local tools; the practical limit is your device’s memory.
• Results appear as fast as your device can compute them.
• Many tools keep working offline once loaded.

We think this is how utility software on the web should work: fast, private and respectful of the person using it. If you notice a tool that could run locally but does not, or have ideas for new tools, tell us through the feedback box on any tool page or at saudaprime@gmail.com.