Why local favicon tools matter (Network-tab privacy FAQ)
Logos often encode unreleased product names, client marks, or internal tooling. Upload-based generators must receive those bytes. A local tool never needs that hop.
What “no upload” means here
- Files are selected with the browser file picker or drag-and-drop.
- Resize and ZIP packing happen in page memory (canvas / ICO encoder / JSZip).
- You can open DevTools → Network during generate and confirm no document or image POST of your logo.
Network-tab privacy FAQ
I still see requests to localfavicon.pages.dev — is that an upload?
Those are normal page/asset fetches (HTML, CSS, JS). Your logo bytes should not appear as a request payload. Filter by Fetch/XHR and watch for unexpected POSTs while generating.
What about Cloudflare analytics?
Optional Cloudflare Web Analytics is aggregate and cookie-free. It does not receive your image payloads. See the privacy policy.
How is this different from favicon.io?
Leaders and clones may be fine for public logos. LocalFavicon’s wedge is: complete ZIP, SVG-in when feasible, no account, and an explicit Network-tab check so you can verify privacy yourself.
Local tools are not magic anonymity. Shoulder surfing, malware, and shared devices still matter. They do remove one common leak: sending brand assets to a random converter backend.