How it works
The tool comes to your browser. Your file stays where it is.
Two ways to convert a file
Most online converters upload your file to a server, process it there, and send the result back. PieToolkit does the opposite: the tool is downloaded to your browser, and your file stays where it is.
The difference is not a slogan. It changes what the site can see, how fast a job finishes and where the limits are.
What runs where
- The page itself is a static file served from a global CDN, so it loads fast everywhere.
- The engine of each tool is JavaScript and WebAssembly that runs in a background thread of your browser (a Web Worker), so the page stays responsive while it works. The PDF editor runs PDFium, the PDF engine inside Chrome. The image converters run libwebp, libavif, mozjpeg and oxipng, well-known open source encoders.
- Your files are read from your disk straight into that thread, and the result is handed back to you as a download. No network request carries your data.
- Heavy code loads only on the page that needs it, the first time you use that tool, and your browser caches it for the next visit.
What we can and cannot see
We cannot see your files, their names or their contents. What reaches our server after a finished job is a count: which tool, whether it worked, how many files and their total size in bytes. Those counts feed the live numbers above the footer. A search that finds no tool sends the words you typed, so we can build the missing tool. Never a file, never an identifier. The privacy policy lists everything.
The website and network checks are the one exception: they cannot run inside your browser alone, so the address you type goes to the outside services that answer the check. The privacy policy names each one and what it receives.
Why this is faster
There is no upload, no waiting in a queue and no download of a processed file. A set of photos becomes a PDF in the time it takes your device to decode them. Converting a folder of images splits the work across up to four Workers, one per spare core, so several files convert at the same time.
Where the limits are
Because the work happens on your device, very large jobs depend on your device's memory. A laptop handles hundreds of photos in one go; a phone is happier with smaller batches. Each tool states its practical limits on its page, and the PDF editor tells you before it opens a file that is too large.
Send to phone
A finished file can jump to your phone with the QR code beside the Download button. Your phone and your computer connect to each other directly, encrypted end to end; our server only introduces the two devices and never sees the file.