Toolpit
Loading your page…
Toolpit
Loading your page…
Open a tool, drop in your file, and the work happens on your own machine. That’s why your document is not uploaded for processing. Large files and on-device AI can take time, and models may need downloading before the first run.
Private — processed on your device, never uploaded
The website, scripts and optional models are downloaded to your browser. Account, payment, advertising and analytics services use the network separately from file processing.
Dropping a file hands it to the page through the browser’s own File API. The bytes go into this tab’s memory — not to a network request.
JavaScript and WebAssembly libraries run on your device. Processing time depends on the tool, file size and device; some tools download models on first use.
Saving requires an account and costs 10 tokens. The result is handed to your browser’s download flow. Closing the tab does not delete files you saved or cached website assets.
You do not have to take our word for it. Open your browser’s developer tools, switch to the Network tab, and use any tool on Toolpit. You will see the page load, its scripts download and the ads fetch themselves. When you save a result while signed in, you will see one small request that charges 10 tokens to your account. What you will not see is a request carrying your file, its name or anything read from it, because file processing stays local. Offline processing depends on the tool’s scripts and models already being cached and on browser support. Website saving needs a connection to check your account and charge tokens.
Because there is no upload, size limits are set by your own device rather than by a free-tier quota. A large PDF is processed at the speed of your CPU, and the progress bars you see are real work happening locally — not a queue position on somebody else’s server.