Practical Tool Guides
What browser-only tools can and cannot keep private
A practical privacy guide for local file tools, browser permissions, and third-party browser services.
Local processing is useful
When a tool runs in the browser, selected files can often stay on your device instead of being uploaded to a remote conversion server.
- Image, canvas, and many text tools can run locally.
- Downloads can be generated from browser memory.
- No account is needed for the core workflow.
Browser APIs still matter
Some features rely on browser APIs or third-party browser services, especially speech recognition, translation, model files, and media recording.
- Microphone tools need explicit permission.
- Some models or runtimes may be loaded from a CDN.
- Browser vendors may define how speech or translation is processed.
Good habits
Treat important files carefully even when a tool is browser-only.
- Keep originals before converting.
- Avoid using files you do not have rights to process.
- Clear site data if you want to remove saved settings.