Use Merge PDF when you have two or more PDFs that need to become one local output. The exact workflow is:
- Open Merge PDF.
- Choose Choose PDF files and select the PDFs from this device.
- Review Merge order before running the operation.
- Use Move earlier, Move later, or drag the file cards to put the PDFs in the right sequence.
- Use Open file options when a source PDF needs a page-range preview instead of using every page.
- Optional: set Output file name, Section dividers, or Print-shop cover sheet in the options panel.
- Choose Merge N PDFs, then download the merged PDF when the output is ready.
The important privacy detail is narrow and specific: the merge operation runs in the browser. The site still loads normal app assets such as pages, JavaScript, WebAssembly, and fonts. After you choose files, Lemmafour should not need to send the selected PDF bytes to a document-processing server to create the merged output.
That difference matters for contracts, statements, filings, school forms, and other packets where the PDF itself is the sensitive object. It is also why the merge page includes the Local - 0 sent proof control. Open it after selecting files, or verify with the browser’s Network tab, and check for yourself that the document-processing flow is local.
What to check before merging
The merge operation is simple; the mistakes are usually human. The output is only as correct as the order and ranges you choose.
Start with file order. If the first file is a cover letter, the second is a contract, and the third is an appendix, the cards should appear in that same sequence in Merge order. On a phone, use the visible move controls instead of relying only on drag gestures. Dragging and scrolling compete for the same finger movement on touch screens, so buttons are often more predictable for important packets.
Next, check page ranges. A source card showing Pages: all means every page from that source is included. If you only need pages 2-4 from one PDF, open that file’s options, preview the pages, and apply the range there. Do not wait until after the merge to notice that a cover sheet, receipt, or blank scan slipped into the final packet.
Finally, decide whether the output needs separators. The Section dividers option can add a divider page between PDFs. That is useful for print packets and client review bundles, but it is not always appropriate for official forms or submissions where page count must stay exact. The Print-shop cover sheet option is a convenience for print instructions, not a guarantee that a print shop will use those settings.
Why the private route matters for merged packets
A merged PDF often contains more information than any single input file. A contract packet might include the agreement, tax form, signed appendix, and ID scan. A bank packet might include statements from several months. A school or medical packet might combine several forms that were harmless separately but sensitive as a bundle.
With an upload-based tool, the path is: file to server, processing on the server, result back down. HTTPS protects the file in transit — but it still arrives at infrastructure someone else operates. With Lemmafour, your browser reads the files and merges them itself. That’s the whole claim — no more, no less. It isn’t encryption and it isn’t a certification; it’s the file simply never being sent.
Don’t take the claim on faith. Open the Local - 0 sent panel while you work, or open your browser’s Network tab and watch what the page actually sends: you’ll see the app’s own scripts and fonts load, and nothing carrying your documents.
Edge cases that change the merge result
Page size differences are normal. Merging a letter PDF with an A4 PDF does not make the pages the same size. It preserves the page sizes unless another tool later changes them. If consistency matters for printing, open the merged output and use Print Doctor or page tools before sending it onward.
Rotation can also surprise people. If a source PDF has sideways pages, merge will carry those pages into the output. Rotate them before or after merging, but check the final file in a second PDF viewer when the packet is important.
Bookmarks, page labels, and form fields can be more complicated than visible pages. A merged file is a new PDF, not the original documents stapled together with all reader behavior guaranteed unchanged. If the output will be filed, signed, or sent to a formal workflow, keep the originals and review the exported file directly.
Large PDFs are limited by browser memory. Because there is no server doing the work, your device does it — a modern laptop shrugs at jobs an older phone may struggle with. If a phone runs out of memory, use a desktop browser or split the job into smaller groups, then merge those groups.
One honest limitation
Merge is a page-assembly tool. It does not redact sensitive content, remove metadata, certify signatures, OCR scans, or validate filing requirements. If one page contains information that should not be shared, merge is the wrong fix by itself. Use redaction for sensitive content removal, delete pages for whole unwanted pages, or organize pages when the issue is order.
The safe pattern is boring and reliable: merge, download, reopen, inspect page order and page count, then send the file through the channel your recipient expects.
Sources for background browser concepts: MDN WebAssembly and Chrome DevTools Network panel.