You can inspect whether a particular tool sends your input across the network during a test. That is more useful than relying on a privacy slogan. Use a harmless sample document, keep the Network panel open, and distinguish the requests needed to load the application from requests triggered by processing your file.
Steps
- Open Chrome DevTools and select Network before visiting the tool. Edge and Firefox have similar panels, though labels differ.
- Visit Merge PDF and wait for its application code to load.
- Keep All request types selected and enable Preserve log if an action might navigate. Start without a domain filter so requests to another host remain visible.
- Clear the request log, add two small PDFs containing a distinctive harmless test phrase, and run the merge.
- Inspect new requests, including their destination, method, type, initiator and any request payload. Look for file bytes, encoded content, extracted text or your sample phrase. An upload need not be a large POST to this site's own domain.
- Inspect an active WebSocket connection's messages too, if one is present. Copy and download the result, then continue observing briefly for requests triggered after processing.
JavaScript modules, fonts and static assets are application downloads. Consent-enabled analytics may add event requests. Inspect their payloads rather than assuming every request is a file upload or every small request is harmless. Do not share an exported network log containing cookies, tokens or private URLs.
What the result means
If the run succeeds without a request carrying the sample input, that supports the claim that this operation processed the file locally during your test. It does not establish how every tool, future release, browser extension or error path behaves. Repeat the check for the tool and options you actually intend to use.
A remote page still receives the requests needed to serve it, including ordinary connection information. Local file processing describes where the transformation happens; it does not mean your visit creates no network traffic or that the website has passed an independent security audit.
If the Network panel was opened after the action, redo the test. It cannot show requests from before it started recording. Check that recording is active and that a filter has not hidden the requests you need to inspect.
Offline
As a second check, load the tool and its required modules, then select Offline in DevTools or disconnect the device. Try the same small operation again. Success demonstrates that this loaded workflow can run without a current network connection.
Failure is less conclusive. A tool may process files locally but still need a module, font or worker that has not loaded yet. Browser cache eviction and service-worker state also affect offline availability. Do not assume that visiting the home page once makes every tool available offline.
Reconnect afterward and observe whether delayed requests appear. Offline success by itself does not rule out later transmission.
Keep the test and your real data separate
Use a dummy PDF for inspection. For real documents, keep originals, verify the downloaded pages and clear sensitive clipboard contents or shared-screen views when finished. Browser extensions and device access remain separate trust decisions from the website's processing design.
These steps apply to file tools and text utilities such as JSON Formatter. Test the exact operation rather than generalizing from a different tool's behavior.
Reference
Chrome DevTools Network documentation explains recording, filters, request payloads and offline emulation. This guide describes a practical observation procedure, rather than a certification of all possible data flows.
Bookmark Security for the same checklist.