- Are my PDFs uploaded to a server?
- No. The files are read into memory in your browser tab, merged there with the pdf-lib JavaScript library, and the result is offered as a local download. There is no upload request at all — you can watch the network tab to confirm.
- Is there any quality loss when merging?
- No. Pages are copied at the object level, not re-rendered: text, fonts, vector graphics, and embedded images move into the new file byte-for-byte. Nothing is converted to a bitmap, so the merged pages are visually identical to the originals at any zoom level.
- Can I merge password-protected (encrypted) PDFs?
- Not directly. If a file is encrypted, the tool rejects it with an error when you add it rather than producing a corrupt merge. Remove the password first — most PDF viewers can save a decrypted copy once you have opened the file with its password — then add the decrypted file here.
- What are the file and page limits?
- Up to 20 PDFs per merge, each up to 64 MB. There is no hard page limit — the practical ceiling is your device’s memory, since every source file and the merged result live in RAM while the tool works. Hundreds of pages merge comfortably on an ordinary laptop.
- Does the page order follow the list order?
- Yes, exactly. The merged PDF contains all pages of the first file in the list, followed by all pages of the second, and so on. Use the arrow buttons to reorder files before merging; any change to the list invalidates the previous result so you always download what you see.
- Are bookmarks and form fields preserved?
- Page content, yes — everything drawn on the pages survives intact. Document-level structures are a different story: bookmarks (the outline tree) and interactive form field definitions live outside the pages, and because this tool copies pages into a brand-new document, those structures may be lost or stop working in the merged file. If your PDFs rely on fillable forms or a navigation outline, check the result before discarding the originals.