Every PDF tool. Nothing uploaded.

Why no PDF here is ever uploaded

Search for "merge PDF" and you will find dozens of sites that all work the same way. You upload your document, their server does the work, and a line of small print assures you the file will be deleted within an hour. You have no way to check. And the documents people merge and split are rarely holiday photos — they are bank statements, Aadhaar copies, marksheets, medical reports, signed agreements.

That architecture made sense in 2010, when browsers could not read a PDF. It does not make sense now. pdf-lib can rewrite a PDF's page tree in JavaScript. pdf.js — the engine inside Firefox — can render and parse one. qpdf compiled to WebAssembly performs genuine AES-256 encryption. The capability has been sitting in your browser for years. Most sites keep uploading anyway, because the upload is where the business model lives.

Every tool here does the work on your machine instead. That is not a privacy promise you have to trust; it is an architecture you can verify. Open your browser's developer tools, switch to the Network tab, and use any tool on this site. You will see the page load, you will see a library arrive once from a CDN, and then nothing. No upload request, because there is nothing to upload to.

What that changes in practice

Four things follow, and all of them favour you. There is no file size limit, because there is no upload to cap — only your own device's memory. There is no queue and no "3 files per day", because there is no server cost for anyone to recover. Tools keep working offline once the page has loaded. And page operations are genuinely lossless: merging and splitting copy pages between documents without decoding them, so text stays selectable and images stay at full resolution.

The honest trade-off: heavy work uses your CPU. Rendering a 200-page PDF to images takes longer on an old phone than it would on someone else's server farm. We think that is the right trade, and we would rather tell you than pretend otherwise.

The tools we deliberately do not offer

You will not find PDF to Word here, or Word to PDF. They are the highest-volume searches in the entire PDF category, and we do not offer them because we cannot do them well.

The reason is structural, not technical laziness. A PDF does not contain paragraphs, tables or headings. It contains instructions like "draw the glyph 'H' at x=72, y=710". Turning that back into a Word document means inferring that a run of glyphs was a heading, that a gap between columns was a table boundary, that two blocks of text were not one sentence. It is guesswork, and Adobe gets it wrong on its own format. A bad PDF-to-Word is worse than none, because people trust the output and send a broken document to an employer.

The same applies to editing existing text, and to Word-to-PDF, which needs a full layout engine to reproduce Microsoft's pagination and font fallback. If your CV's formatting shifts, the conversion has failed at the only thing that mattered.

Built for how Indian forms actually work

Several tools here exist because Indian portals have specific, unforgiving requirements — a single PDF under 200KB, an exact page range from a 40-page statement, a document whose password came by SMS. Those are precisely the files that should not be uploaded, and precisely the ones every free tool asks you to upload.