What merging PDFs without a file upload means
ZAMAZY Merge PDF reads selected PDF files in browser memory. A local Web Worker performs the merge and output checks. The download refers to a temporary browser object, not an uploaded result on a server.
Last reviewed:
Loading software is different from uploading your PDFs
The page, styles and processing software need network access when they first load. Cloudflare delivers these assets and receives the technical request information needed to serve them. The selected PDF bytes, original names and merged output are not sent by the Merge PDF processing flow.
Usage analytics is separate from file processing. It can measure allow-listed interactions, technical outcomes, browser/device categories and referral context, while document contents and original filenames remain excluded. Check the current privacy page for the defined data categories and retention. A pseudonymous browser identifier can connect repeat visits.
What can be checked
With clearly labeled synthetic examples, browser network inspection can check whether processing sends their bytes or markers. Offline tests must first load the required worker and parser assets; opening only the landing page does not necessarily preload every component.
Offline behavior depends on which assets the browser has cached. A successful offline test is evidence for that tested setup, not a promise that the website always opens offline or that every browser behaves identically. Documents are not stored in a service-worker cache by this flow. The tool does not queue analytics for a later connection.
Keep control of the result
The originals remain unchanged. Changing selection or order invalidates the old download. Any offered removal of document features requires explicit agreement. Review the result before submitting it and use the current privacy and supported-PDF information for the applicable boundaries.