Workflow guide

How to verify Fileees no-upload browser processing

Use DevTools to verify Fileees browser-local tools, understand Network tab signals, and spot the remote network tools that are marked exceptions.

Short answer

To verify Fileees no-upload processing, open DevTools, use the Network tab, filter Fetch/XHR while running a browser-local tool, and confirm your selected file contents are not sent to Fileees servers. Static assets may load, and remote network tools are marked exceptions.

Open PDF Merger

Best for

Privacy claims are easier to trust when users can inspect browser behavior directly instead of relying only on a marketing sentence.

  • Checking sensitive file workflows before use.
  • Teaching teammates how browser-local processing behaves.
  • Comparing local tools with marked remote network exceptions.

Privacy notes

  • Supported file tools process selected files locally in the browser.
  • Remote network tools are marked exceptions and use guarded Fileees functions for public lookups.

Common mistakes

  • Confusing static library downloads with file-content upload.
  • Testing only after the tool has already run without clearing the Network log.
  • Forgetting that remote lookup tools are intentionally marked exceptions.

Limitations

  • Static assets and libraries may load while the page is open.
  • Browser extensions, proxies, and antivirus tools can add their own network activity.
  • This check verifies browser behavior for the sampled workflow, not every future browser or extension configuration.

Steps

  1. Open a browser-local tool such as PDF Merger or Image Compressor.
  2. Open DevTools, choose the Network tab, and clear the current log.
  3. Filter Fetch/XHR, run the tool, and confirm there is no request carrying your selected file contents.
  4. Repeat with a marked remote network tool such as DNS Lookup to see how Fileees labels exceptions.

FAQ

Does no-upload mean no network requests at all?
No. The page may load static assets and libraries. The important check is whether your file contents are sent during supported local processing.
What should I filter in DevTools?
Use the Network tab and filter Fetch/XHR while running the tool.
Are remote network tools different?
Yes. Remote network tools are marked exceptions and use guarded Fileees functions for public lookups.
Can I verify image and PDF tools this way?
Yes. Run a small sample file and inspect the network activity before and during processing.

Related tools

PDF MergerCombine multiple PDF files into one browser-local documentImage CompressorCompress JPG, PNG, and WebP images locallyDNS LookupResolve public DNS records through a rate-limited Fileees network function