Security architecture
What the conversion code does with a file, and what else the page may request.
Converts in your browser. Your files aren't uploaded to a server. The repository has no active Cloud Function that receives image or PDF bytes.
File processing steps
The file stays in a browser File object. RAW previews are parsed in a Web Worker.
Canvas encodes JPG, PNG, and WebP. AVIF and HEIC use libraries shipped with the app. PDF tools use jsPDF, pdf-lib, or pdf.js. Upscale uses WebGL in a worker.
The result is a local blob. The download is started by the browser.
Encoders in this build
Canvas
JPG, PNG, and WebP use canvas.toBlob. JPG and WebP take the quality slider. The default is 80%, and both are lossy. PNG ignores that slider.
WebAssembly libraries
AVIF encoding and HEIC decoding use WebAssembly that ships with the app. WebP on this site does not use a separate WebAssembly encoder.
AI upscale
ESRGAN Thick 2× runs in a Web Worker. The first run downloads model weights from /models/esrgan-thick/x2/ on this site. Your image is not sent with that request.
Analytics
After consent, loadGtag.js loads googletagmanager.com/gtag/js. Events are limited to page path, a fixed acquisition label, tool name, file count, format, mode, and download type.
How to check the network panel
- Open developer tools and select the Network tab.
- Load a JPG, PNG, or WebP and convert it.
- Confirm the new requests are not an upload of that file. You may still see the page's own scripts.
- HEIC, AVIF, PDF to image, and the first AI upscale also download their library, font, or model files from this site. That download is not your file being uploaded.
- If you accepted analytics, you can see requests to Google. Those payloads are the counts described above.
- After the scripts you need are already loaded, JPG, PNG, and WebP conversion does not require another network call for the file. The first AI upscale still needs the model files.