The local path
You select a file, the browser reads it into temporary memory, a local processor creates a new Blob, and the page generates a temporary object URL for preview or download.
- File selected on your device
- Decoded by browser APIs
- Processed in the current tab
- Result held as a temporary Blob
- Downloaded through a local object URL
What does not happen
Released browser-local tools do not send the image to a PicConverters conversion server. There is no server request containing the selected file bytes, filename, EXIF, or generated output.
Temporary memory and object URLs
Object URLs are browser references to local in-memory data. PicConverters revokes them when results are cleared or the component closes. Refreshing or closing the page ends the current session and clears in-memory workflow transfers.
Browser-loaded codecs
Future specialist tools may download codec code and run it locally. Those tools will be labeled Browser + Codec. Loading a codec is different from uploading your image; the file still remains on the device unless a tool explicitly declares otherwise.
Your responsibilities
Keep originals, review results, avoid processing files on an untrusted device, and clear browser data when using a shared computer. Browser-local architecture reduces transfer risk but does not secure the device itself.