Prepare Image for Favicon (32×32 or 512×512)
Modern favicons need 32×32 for tabs and 512×512 for high-DPI Apple touch icons.
Your images stay on your device. Nothing is uploaded.
The classic favicon.ico at 32×32 is still needed for Chrome, Firefox and Edge browser tabs. Modern setups also need a 512×512 PNG for Apple touch-icon and PWA manifest use. Start from a clean 512 PNG and downscale.
This preset produces a 512 px PNG — favicon-ready. Downscale further to 32 for the .ico file.
Related tools
Frequently asked questions
- How much can I shrink images for favicon?
- Typical reductions are 60–85% with no visible quality loss using the defaults on this page. The classic favicon.ico at 32×32 is still needed for Chrome, Firefox and Edge browser tabs. Modern setups also need a 512×512 PNG for Apple touch-icon and PWA manifest use. Start from a clean 512 PNG and downscale.
- What format is best for favicon?
- The default format for favicon is PNG at the preset above — chosen for the format's rendering compatibility and byte efficiency in this context.
- Will compression break transparency or animation?
- Transparency is preserved when the output format supports it (PNG, WebP, AVIF). Animation is preserved for animated WebP. JPEG output flattens transparency to white.
- Can I compress dozens of images at once?
- Yes — use the bulk compressor. Drop a folder or multi-select files; the queue processes them in order with progress per file, and you can download all results as a ZIP.
- Do my images get uploaded anywhere?
- No. The tool runs entirely in your browser — important for client work, internal assets, and anything not yet published.
Optimise the rest of your favicon assets.
Use the bulk compressor to process a folder in one go. Everything runs locally.
Start compressing