Merge PDF

No. Your files are read and combined by code running inside your own browser, using your device's memory. No part of a document you add is sent over the network, which is also why the merge starts immediately instead of waiting on an upload. You can check this yourself: open your browser's developer tools, watch the Network tab, and merge a file. The requests you will see are this page loading its own code, and — if one of your documents uses Chinese, Japanese or Korean text — a character table that this site serves to your browser so it can draw those characters. That request says which table is needed and nothing about your file.

No. The output contains exactly the pages from the files you added, in the order you set. There is no watermark, no footer, and no added cover page — and no paid version that removes one, because there is nothing to remove.

We set no limit of our own on file size, page count, or how many documents you merge at once. Because the work happens on your machine, the real ceiling is how much memory your browser will give the tab: a desktop computer handles large documents comfortably, while a phone runs out sooner. If a very large merge fails, try it on a desktop browser or combine the files in smaller batches.

Bookmarks are kept. The merged file gets one top-level bookmark per document you added, named after the file, with that document's own outline beneath it, so a merged table of contents still tells you which file each section came from. Two things change: a bookmark whose page you removed moves to the nearest page that is still there rather than disappearing, and a bookmark that pointed at a web address or at a different file keeps its name but loses the jump, because a merged document should not carry links you did not ask for. Page content is copied faithfully too — text, images, vector graphics, embedded fonts, and each page's size and orientation come through unchanged. Interactive form fields, annotations, and internal cross-references are a different matter: they are not guaranteed to survive, and some may be dropped or flattened. If any of those matter for your document, open the merged file and check it before deleting your originals.

Yes. A PDF that opens without asking for a password is merged normally, even if it carries permission restrictions. If a file is encrypted, the tool notices while it is reading it, marks that file as locked, and asks you for the password; enter it and the document is unlocked in your browser and merged like any other file. The password is used in the page you are on, is never sent anywhere, and is not saved — reload the tab and it is gone. If the password is wrong the tool says so and asks again, and that file stays locked: the merge waits until you unlock it or remove it, rather than quietly leaving it out. A file whose encryption your browser cannot open at all is reported as unreadable and skipped, and your other files still merge. The merged file that comes out is not password-protected, so add a password again afterwards if you need one.

Yes, and there is no catch to go looking for: no sign-up, no trial period, no watermark to pay to remove, and no cap on how often you can use it. We intend to fund the site with advertising displayed alongside the tool. The tool itself is not going behind a paywall.

Any current version of Chrome, Edge, Firefox, or Safari, on Windows, macOS, Linux, Android, or iOS. The tool needs a browser new enough for modern JavaScript and Web Workers, which covers releases from roughly the last four years. It does not run in Internet Explorer, and older phones may run out of memory on large documents.