Your file never leaves your device
49 of the 59 tools here do their work inside your browser. There is no upload, no queue, and no copy on a server to trust, leak or delete.
What actually happens when you use most PDF sites
You pick a file. It is uploaded to a server you know nothing about, in a country you were not told, processed there, and offered back as a download. Somewhere on that server your document sits until a cleanup job removes it. You are asked to take on trust that the job runs, that nobody copied anything first, and that the company will still exist and still care next year.
For a holiday photo, fine. For a contract, a payslip, a passport scan, a medical letter or a client file, that is a real decision being made on your behalf, usually without being mentioned.
What happens here instead
Your browser reads the file straight from your disk into the memory of the page, does the work there, and hands you the result. The document is never put on the network. Not encrypted in transit and deleted later — never sent.
| Upload-based tools | The browser-side tools here | |
|---|---|---|
| Where the work happens | A server you cannot see | The tab in front of you |
| Who else has your file | The operator, their host, their subprocessors | Nobody |
| What happens if they are breached | Your document is in the breach | There is nothing of yours to breach |
| Works without internet | No | Yes, once the page has loaded |
| Speed on a large file | Limited by your upload speed | Limited by your processor |
| What you have to trust | A deletion policy | Something you can verify in the Network tab |
Check it yourself — this is the point
A privacy claim you cannot verify is a marketing line. This one you can test in under a minute, and we would rather you did:
- Open any browser-side tool below and let the page finish loading.
- Turn off your Wi-Fi, or switch your network to offline in the browser’s developer tools.
- Use the tool. Merge, split, compress, rotate, sign — it all still works.
Nothing that needs a server survives being disconnected from one. That is the whole demonstration.
The 10 tools that do use a server, and why
Being straight about the exceptions is the only thing that makes the rest believable. These are the jobs a browser genuinely cannot do on its own. Each one says so on its own page as well, before you choose a file.
- Repair PDF — processed on our server and deleted afterwards
- Word to PDF — processed on our server and deleted afterwards
- PowerPoint to PDF — processed on our server and deleted afterwards
- HTML to PDF — processed on our server and deleted afterwards
- PDF to PDF/A — processed on our server and deleted afterwards
- Protect PDF — processed on our server and deleted afterwards
- Unlock PDF — processed on our server and deleted afterwards
- AI Summarizer — the text is sent to the AI provider this site is configured with; a scanned page is read in your own browser first, so the image itself is never uploaded
- Translate PDF — the text is sent to the AI provider this site is configured with; a scanned page is read in your own browser first, so the image itself is never uploaded
- Grammar Check — processed on our server and deleted afterwards
What this means under GDPR
The regulation governs what happens to personal data once it is transmitted. If the document is never transmitted, most of it simply does not engage: there is no processor to appoint, no international transfer to justify, no retention schedule to publish and no breach to notify — because there is no copy anywhere except the device in front of you.
That is a different position from a supplier promising to delete your file in an hour. It is the difference between a policy and an architecture. See our GDPR page for how the rest of the site handles data, and the privacy policy for the formal version.
The 49 tools that never send your file anywhere
Merge PDFSplit PDFRemove PagesExtract PagesOrganize PDFRotate PDFScan to PDFCompress PDFOCR PDFJPG to PDFExcel to PDFText to PDFMarkdown to PDFPDF to JPGPDF to WordPDF to MarkdownPDF to PowerPointPDF to ExcelEdit PDFSign PDFFill PDF FormsPage NumbersHeader & FooterWatermark PDFCrop PDFRedact PDFCompare PDFImage ConverterCompress ImageRemove MetadataUpscale ImagePassport PhotoWatermark ImageMeme GeneratorColor PickerWord CounterCase ConverterDuplicate RemoverFind & ReplaceDummy TextQR Code GeneratorInvoice GeneratorAge CalculatorBarcode GeneratorUnit ConverterPercentage CalculatorPassword GeneratorResume BuilderE-Invoice Viewer
Questions
- How can a PDF tool work without uploading the file?
- Your browser is a capable computer. It can read a PDF, re-draw its pages, re-encode its images and write a new file, all in the tab you have open — the same machinery that lets a browser play video or run a game. The file is read from your disk into the page’s memory and never put on the network at all.
- How do I know my file is not being sent somewhere?
- Check rather than trust us. Open your browser’s developer tools, switch to the Network tab, and run the tool. On a browser-side tool you will see no request carrying your document — and you can go further and disconnect from the internet entirely after the page has loaded. The tools keep working.
- Which tools do send my file to a server?
- The ones listed on this page, and they say so on their own pages too. They are the jobs a browser genuinely cannot do alone: converting Office documents, PDF/A archiving, repairing a damaged file, PDF encryption, and anything AI. Those files are processed and then deleted, and the AI tools pass the text to the provider the site is configured with.
- Is this better for GDPR?
- It removes the question rather than answering it. If a document is never transmitted, there is no processor to appoint, no transfer to justify, no retention period to argue about and no breach to report — because there is no copy anywhere but your own device. For legal, medical and HR documents that is a materially different position from a vendor promising to delete things later.
- Is there a file size limit?
- Not one we impose for the browser-side tools — the limit is your device’s memory, and a few hundred pages is comfortable on an ordinary laptop or phone. There is no upload to time out and no queue to wait in, which is also why large files are usually faster here than on a site that has to receive them first.