Merging two PDFs, dropping a page, or turning a stack of photos into one document are jobs that normally mean uploading the file to a website you have never heard of and hoping it deletes it afterwards. This page does all of it in the browser. Drop the files in, rearrange the pages, and save — the bytes never leave your machine, which matters when the PDF is a contract, a payslip or a passport scan.
A PDF is a container for a page description rather than a document in the sense a word processor means, and that is what decides which operations are cheap. Merging, splitting, reordering and rotating rearrange whole page objects and leave their contents untouched, so they are lossless and fast — nothing is re-rendered and no quality is lost. Editing the text inside a page is a different problem entirely, because the file stores glyph positions rather than sentences, which is why a tool that promises to edit PDF text is usually rasterising the page and drawing over it.
Rotation has a detail worth knowing. A page carries a rotation attribute that viewers apply when displaying it, so a page that appears sideways may be stored upright with a rotation of 90 — or stored sideways with no rotation at all. Rotating here changes the attribute, which is the lossless operation, and means a page scanned upside down is corrected without touching a single pixel. If a page still appears wrong in another viewer afterwards, the two are disagreeing about the attribute rather than about the content.
Everything happens in this browser through a PDF engine compiled to run in the page, so a document is never uploaded. That is the difference that matters for the files people most often need to merge — a contract, a bank statement, a medical form, a set of scanned identity documents — where uploading to a free web service means handing the contents to a third party whose retention policy you have not read. The practical limit is memory rather than a file-size rule: very large scanned documents are slower here than they would be on a server, which is the price of not sending them anywhere.
No. The files are read by JavaScript running in this tab and the new PDF is assembled in memory on your own machine. There is no server to receive them and no account to store them against. If you want to verify it rather than take our word for it, open your browser's network tab before you drop the file in and watch that nothing is sent.
Not for PDF pages. Merging copies the original page objects — the same fonts, the same vectors, the same embedded images — rather than re-rendering them, so a page that came in sharp goes out sharp. The only place quality is a question is the "save as images" export, which rasterises at twice screen resolution.
Because every page brings its resources with it. Two documents that each embed the same font end up carrying two copies of it in the merged file. The upside is that nothing is lost or re-encoded; the downside is that the arithmetic on the file size is not tidy.
No. This works at page level — reorder, rotate, remove, combine. Editing the words on a page means reflowing the layout, substituting fonts and re-encoding the content stream, which is a different tool and a much larger one. If you need the text out, use the image export and run it through an OCR tool.
Yes, though it is easier on a desktop. Selecting and reordering by touch works, and the export is the same. Very large documents are harder on a phone simply because the tab has less memory to render thumbnails into.