`“The file never leaves your browser” sounds simple, but it can describe only part of the data flow. A web app still downloads its HTML, JavaScript, and other assets. The useful question is what happens to the bytes a person selects.
For ZANCTA’s supported PDF and image workflows, processing happens in the current browser tab. That means the page should explain this boundary plainly: files are processed locally while the website itself still loads normally.
This distinction also keeps the claim honest. Local processing does not mean every operation is available offline, and it does not remove the need to explain browser permissions, file limits, or the behavior of each tool.
When you build a file utility, make the data path visible: which inputs are handled locally, which operations have limits, and what is transmitted to the service. Clear language helps users decide whether a tool fits their document and their threat model.`
Top comments (0)