Merge or split PDFs without uploading the documents

How the local PDF pipeline works

When PDF work begins, the page loads its bundled copy of pdf-lib from the same site. Each input is read into browser memory. During a merge, pages are copied into a new PDF document in the order supplied. During a split, each source page is copied into its own newly saved PDF. The resulting bytes become temporary browser download URLs.

What merging changes

Page artwork and text are copied rather than converted to screenshots. The output name is sanitized to avoid characters that are unsafe in filenames. The current interface does not provide drag-to-reorder controls, so choose the input files in the order you want them merged.

What splitting changes

Splitting creates one download per page using names such as document-page-1.pdf. It does not lower image resolution or reduce the source document's quality. Splitting can still increase the combined byte size because each new document needs its own PDF structure.

Limits and compatibility

• The website accepts up to 30 MB per input file.
• Password-protected or malformed PDFs may fail to load.
• Digital signatures can become invalid when a document is rebuilt.
• Complex forms, attachments, outlines, scripts, or unusual object structures should be checked in the output before the original is discarded.
• A document with many pages can consume much more memory than its compressed size suggests.

Privacy

The implementation contains no upload request for PDF data. The document and output exist in the browser session. Network requests for the site or advertising are separate from the local PDF bytes; the converter does not pass the selected file to them.