GUIDE · 3 min read
Where do your files go when conversion runs in a browser?
How local conversion, browser workers, and codec downloads fit together.
Tierify editorial · November 18, 2026
Selecting a file grants access to the page
Choosing a document in a file picker allows the page to read that selected file. Selection alone does not mean upload. Tierify passes the input to a dedicated browser worker and does not send it to a conversion API or a remote storage bucket.
A download link saves a Blob generated by the browser. Source files are not modified, and the site does not maintain a server-side archive of your results. Download anything you need before resetting the tool or closing the page.
What a Worker and WebAssembly do
A Web Worker runs JavaScript separately from the page rendering flow. Tierify uses workers for conversion so that you can interact with the page or cancel a job while it is processing. These browser workers are different from server products such as Cloudflare Workers.
WebAssembly is a binary code format executed by the browser. A WebP conversion downloads the libwebp-based codec from this website, then runs it on your device. Downloading the codec does not upload your image to its author or to a conversion service.
Network requests still happen
The page needs network access to retrieve HTML, scripts, styles, and codecs. The hosting provider may process request information such as your IP address and access time while serving these assets. Local file processing describes conversion input, not an absence of all network activity.
The current application does not run advertising or behavioral analytics scripts. Introducing them would require updated disclosures and any applicable consent mechanisms. Use a trusted device and an up-to-date browser when working with sensitive documents.