Why Doesn't This Tool Ask You to Upload Your File?
Most online PDF tools work the same way. You choose a file, it uploads to a server somewhere, that server does the work, and you download the result. Foliovex skips that step entirely. Here's what actually happens instead, and how you can check it yourself rather than just taking a privacy policy's word for it.
What "uploading" actually means
When you use a typical online PDF tool, your file leaves your device entirely — it travels over the internet to a server you've never seen, sits there (even if only for a few seconds) while it's processed, and the result travels back. During that window, your file exists somewhere outside your control, on hardware run by a company you're trusting based on a privacy policy you probably haven't read in full.
What happens here instead
Foliovex's tools are built with pdf-lib and pdf.js — open-source JavaScript libraries that can read and write the actual PDF file format directly inside a web browser. When you select a file, your browser reads the raw bytes into its own memory, performs whatever operation you asked for — merging, compressing, adding a watermark, whatever it is — and assembles a new PDF, entirely using your device's own processor. The "Download" button doesn't fetch anything from a server afterward; it just saves the file your browser already built, locally.
How to verify this yourself
You don't have to take this on faith, and you shouldn't have to. Open your browser's developer tools (F12 in most browsers, or right-click anywhere and choose "Inspect"), click the Network tab, and then use any tool on this site. Watch what happens: the page's own files load once, and then — nothing. No request fires when you select a file, process it, or download the result. If a file were being sent anywhere, it would show up as a network request in that tab, with a real size and a real destination. It doesn't, because there isn't one.
What this actually gets you
- No wait for an upload to finish before the work even starts — especially noticeable on a slow connection or a large file.
- No file sitting on a server that could be misconfigured, breached, or simply retained longer than you'd expect.
- The tool has no technical ability to see your file's contents, because it never receives them in the first place — not "we promise not to look," but "there's nothing here to look at."
The honest tradeoff
This isn't free. Processing happens using your own device's memory and processing power, not a dedicated server's, so a genuinely enormous file is limited by your own hardware rather than someone else's. For the overwhelming majority of everyday PDFs this makes no practical difference — but it's the honest reason this approach isn't how every tool works.