Short answer
A supported local-processing tool reads the selected file in the browser, processes it with browser APIs or vendored client-side libraries, and creates a downloadable result from the same tab.
Build boundary
The public site may load ads and analytics. The privacy build at privacy.convertunlimited.com is the no-ads, no-analytics review target.
Verification path
Use the verification page, browser DevTools, and repository privacy tests to inspect the behavior instead of relying on marketing language.
Processing path
A typical image workflow uses the File API to read the selected file, Canvas to decode or re-encode pixels, Blob or object URLs to hold the result, and a download link to save the new file.
PDF and developer utilities may use ArrayBuffer, Blob, Web Crypto, or vendored JavaScript libraries. The important distinction is that the file operation is performed by the browser runtime, not by a ConvertUnlimited upload service.
When uploads are not required
Uploads are not required when the browser can decode, transform, and write the required output format locally. Examples include supported image conversion, image compression, metadata cleanup by re-encoding, many PDF operations, JSON formatting, hashing, Base64 conversion, and QR generation.
If a browser cannot decode a format, runs out of memory, or lacks an encoder for the requested output, a local-processing tool may fail or need a different workflow.
FAQ
Does local processing mean no network requests at all?
No. The page must load static assets first. The privacy claim concerns supported processing flows after the page is loaded.
Can local processing handle every format?
No. It depends on browser support, available memory, and the client-side libraries included in the build.
Is local processing the same as a desktop sandbox?
No. The page still runs inside the browser and is affected by browser, extension, device, and host behavior.
Review note
Trust documentation reviewed: May 2026. These pages describe the current public and privacy-build architecture and should be updated when deployment, telemetry, or runtime dependencies change.