How Local File Processing Works

The processing boundary

When you choose a file in a tool identified as local, browser APIs read it into the current tab. JavaScript or WebAssembly then performs the requested operation in memory and creates a downloadable result. The file selector does not itself upload the file, and the tool code does not post document bytes to a QuickMerge processing endpoint.

The browser may still request the HTML page, stylesheets, scripts, icons, document libraries, or OCR language files. Those requests are distinct from the document being processed. You can inspect this boundary in browser developer tools, as described on the privacy proof page.

What stays local

• Selected file bytes and the working document representation
• Extracted text, spreadsheet cell values, and passwords entered into tool controls
• Generated PDF, image, text, ZIP, CSV, or Excel bytes until you download them

What may use the network

• The QuickMerge page and its static assets from Netlify
• Approved third-party code libraries and OCR language resources loaded when a tool needs them
• A contact message only when you intentionally submit the contact form
• Google Analytics and advertising only after optional consent

Memory, performance, and browser limits

Local processing trades server upload risk for device work. A large scanned PDF can need several times its file size in memory while pages are decoded. Older phones, private browsing modes, or tabs already using substantial memory may fail sooner than a desktop browser. Close unused tabs, start with the original file, and process smaller batches when necessary.

Closing or refreshing the tab releases the page’s working state through the browser. QuickMerge does not promise secure deletion from operating-system swap, browser crash recovery, or a downloaded file’s storage location; those are controlled by your device and browser.

Privacy-conscious measurement

Optional measurement is off until consent. When allowed, QuickMerge sends allowlisted product events such as a tool page view, file selected, processing succeeded, and download clicked. The payload excludes filenames, file contents, extracted text, passwords, table values, exact page selections, and raw error messages.

You can decline and continue using the tools. Use the Privacy choices control in the footer to revisit the decision.