What may not survive a merge?
Page content is copied, but bookmarks, attachments, interactive forms, document scripts, and some document-level metadata are not guaranteed to survive. The browser safeguards allow up to 150 MB and 2,500 pages.
Validate each PDF, show its page count, reorder files, and combine up to 2,500 pages locally. The workflow rejects unreadable or password-protected input before merge begins.
Three simple steps
Choose two or more PDFs totaling no more than 150 MB.
Wait for local preflight, then review page counts and order.
Merge and download the current page-content copy.
Privacy first
Tool input and results are processed in temporary state for the current page. The TabPebble application does not send them to a server, write them to a database, or create processing history. Pages and code still load through ordinary network requests. Your browser may restore a tab, while downloads and clipboard copies remain on the device until you remove or replace them.
FAQ
Page content is copied, but bookmarks, attachments, interactive forms, document scripts, and some document-level metadata are not guaranteed to survive. The browser safeguards allow up to 150 MB and 2,500 pages.
Select two or more PDFs, wait for the local page-count check, arrange the file order, then merge and download. The pdf-lib engine runs in your browser; the TabPebble application does not upload the PDFs or keep processing history. Pages and code still load over the network.
No. Unreadable or password-protected PDFs are rejected before merging. Use readable, unprotected copies within the combined 150 MB and 2,500-page limits. Browser memory can impose practical limits below these safeguards.
Yes. Core tools are free to use and do not require an account.
No. The TabPebble application performs the tool task in your browser and does not put input into site requests; ordinary page and code requests still reach the hosting service.