PNG to ICO favicon converter
Upload one PNG and download a real multi-resolution favicon.ico alongside the modern PNG, Apple touch, Android, and PWA files your site needs.
- 1Imagen base
- 2Opciones
- 3Descarga
Definir imagen base
Lo ideal es al menos 512×512 píxeles para un resultado nítido.
Traer el existente desde una URL
Sube una imagen para generar un kit.
Crear un favicon nuevo
Elige un emoji, un logo o un icono. En esta página se convierte en un kit.
Haz clic en un icono para usarlo como imagen base y generaremos el kit completo al instante. ¿Quieres un logo, una marca o más control? Abrir el constructor completo.
Comprobar la cobertura del sitio
Escanea una URL en busca de iconos que falten o estén desactualizados.
Ejemplo de análisis
Datos de ejemplo. Haz un análisis real en la página de comprobación.
One source, every icon surface
Renaming image.png to favicon.ico does not convert it. ICO is a container that can hold several raster sizes so older browsers, desktop shortcuts, and crawlers can choose the right layer. The generator encodes the ICO correctly and keeps the PNG source available for modern surfaces.
ICO layers
16, 32, and 48px
Best source
Square PNG, 512px+
Transparency
Preserved
Output
ICO + full web icon kit
How to get a production-ready result
1Upload the PNG
Choose square artwork, ideally 512×512 or larger. Transparency is preserved unless you select a background.
2Generate the layers
The resulting favicon.ico contains the small sizes that need pixel-level clarity rather than a renamed PNG payload.
3Keep the modern files too
Install the ICO fallback together with PNG, Apple touch, PWA, and manifest assets for complete coverage.
Common questions
Can I rename a PNG to favicon.ico?
No. The extension changes but the file remains PNG data. A real ICO must be encoded as an icon container, ideally with multiple embedded sizes.
Which sizes belong inside favicon.ico?
16×16 and 32×32 are the essential browser sizes; 48×48 is a useful desktop and legacy fallback.
Do modern sites still need favicon.ico?
Yes as a resilient root fallback for older browsers, crawlers, and clients that request /favicon.ico without reading your HTML.