Do my files get uploaded to ToolerWork servers?
No. All file processing on ToolerWork happens locally in your browser. Your files never leave your device. We do not collect, store, or transmit your file content.
100% Client-Side · No Server Upload
How ToolerWork Works
Every tool on ToolerWork processes your files entirely inside your browser tab. No server upload, no signup, no data collection. Here is exactly how it works.
Step by Step
01
You choose a file in your browser
When you drop or select a file on a ToolerWork tool, the browser reads the file directly from your device into memory. Nothing is sent to any server at this point.
02
Processing runs locally using browser APIs
Depending on the tool, processing uses PDF-lib for PDF tasks, Canvas API for image tasks, WebAssembly (WASM) modules for compression and conversion, and local AI models for background removal. All of this runs inside your browser tab.
03
Result is generated in memory
The processed output — compressed PDF, merged document, resized image, or transparent PNG — is generated entirely in your browser memory. It never touches our servers.
04
File downloads directly to your device
The browser creates a temporary local URL for the output file and triggers a download. The file goes straight to your downloads folder from your browser — not from a server.
Technology Behind the Tools
These open-source libraries power the local processing on ToolerWork.
PDF-lib
PDF merge, split, compress, protect, unlock, and watermark operations
PDF.js (pdfjs-dist)
PDF rendering and page preview in the browser
Canvas API
Image resize, compress, convert, and format transformation
@imgly/background-removal
AI-powered background removal using local ONNX models in the browser
Tesseract.js
OCR (text extraction from images) running locally via WebAssembly
FFmpeg.wasm
Video processing and conversion in the browser via WebAssembly
JSZip
ZIP file creation for batch image or file downloads
XLSX.js
Spreadsheet parsing and generation in the browser
Privacy Guarantee
No server upload
Files are processed in your browser memory. No network request is made with your file data.
No account needed
You never need to log in or create an account to use any tool on ToolerWork.
No data retention
When you close or refresh the page, all file data is cleared from memory automatically.
Frequently Asked Questions
How can a browser process a large PDF without a server?
Modern browsers support WebAssembly (WASM), which allows compiled code to run at near-native speed inside the browser tab. PDF-lib and other libraries use this to process files entirely on the client side.
Is browser-based processing slower than server-based?
For most tasks — merging 2-3 PDFs, compressing an image, converting a file format — browser processing is just as fast or faster because there is no network round-trip. For very large files or AI models, the first run may take a few seconds to load the model, but subsequent runs are fast.
What happens to the output file after I download it?
Once you download the file, the browser releases the temporary memory used for the output. Nothing is retained. Refreshing the page clears all state.
Does ToolerWork collect any data about my files?
No. We cannot see your file contents. Our analytics only track general page views — not file names, sizes, or content. See our Privacy Policy for full details.