How local processing works
Most ToolPouch tools process your files directly in your browser. Nothing is uploaded, nothing is stored, and no server is involved.
How it works
You open the tool
The tool page loads in your browser along with the processing code - JavaScript, WebAssembly, or Canvas API.
You select a file
Your file goes from your disk into the browser's memory. It does not leave your device at any point.
Browser processes it
The conversion, compression, or transformation happens entirely within your browser using your device's CPU.
You download the result
The processed file is saved directly from your browser back to your disk. No server was ever involved.
Traditional converters vs ToolPouch
Traditional approach
- 1. Upload file to remote server
- 2. Wait in processing queue
- 3. Server processes file
- 4. Download result
- ⚠ File exists on someone else's server
ToolPouch approach
- 1. Select file from your device
- 2. Browser processes it instantly
- 3. Download result
- ✓ File never left your device
Technologies we use
When is a server needed?
A small number of operations genuinely require server processing - for example, formats that browsers cannot decode natively. Any tool that requires server processing is clearly labelled. For the vast majority of ToolPouch's 209 tools, everything runs locally.
When server processing is needed, your file is sent securely, processed, and returned. It is not stored after processing.