Your files, your device. Here is how it works.
What stays local
Image processing uses the browser canvas. PDF tools use browser-side libraries. File contents are processed in your browser; the tool does not send the selected file to a processing server. Keep your original and review every downloaded result.
What still uses the network
Loading the site, code libraries and Google Analytics involves network requests. Microsoft Clarity session replay is disabled across this site. Local file processing does not mean anonymous browsing or zero network activity. This explanation is not an independent security certification.
How to check for yourself
Use a non-sensitive test file. On a desktop browser, open Developer Tools → Network, clear the log and keep recording while processing. Inspect fetch/XHR requests and their Payload sections for file contents; distinguish asset downloads and analytics from file transfer. A blob: download refers to data created locally. Seeing no upload in one test supports that tested flow, not every feature or future version.
Offline use has limits
Some tools can continue once their code has loaded. PDF, HEIC and ZIP dependencies may load only on first use. The site is not currently an installable offline PWA; do not assume a fresh page will work without internet.
A passing size check is not portal approval
Result checks compare actual file size, dimensions and format with your settings. They do not verify identity, photo composition, signatures, official portal rules or acceptance. Our generic photo presets are dimensions, not certified agency presets.