What stays in the browser
Selected file bytes, decoded pixels, PDF page contents, filenames shown in the workbench, previews, and generated downloads remain in the current browser session. The application does not intentionally attach file content or filenames to analytics events.
What site services receive
Google Analytics 4 and Cloudflare Web Analytics can receive ordinary page and request data such as URL, approximate region, browser category, timestamps, and IP-derived information under their policies. Advertising is disabled and all Google advertising consent signals are denied.
Browser compatibility requirements
The implementation was reviewed on 2026-08-12 against its required web APIs. Use a current browser with JavaScript, WebAssembly, workers, canvas, Blob downloads, and sufficient memory, then verify important output on your device; private browsing and managed devices may impose extra restrictions.
Why local tools can still fail
A compressed 40MB scan may require hundreds of megabytes when decoded. Corruption, encryption, unusual color profiles, unsupported PDF structures, extension policies, and low memory can stop processing even though no upload is involved.
Third-party software and license notices
Frequently asked questions
Does local processing mean the site receives no network request?
No. The page, code, fonts, and analytics still use network requests. Local processing means the selected file content is not uploaded to the application server for the supported operation.
Why can results differ between browsers?
Browsers can differ in canvas color management, memory ceilings, download handling, font availability, and codec implementation. Compare critical output in its destination app.
What should I do with confidential files?
Use an updated trusted browser, close unrelated extensions and tabs, verify the downloaded result, clear the session, and follow your organization's rules for sensitive documents.