Choose an Export
Web Assets vs Single-File Export — and when to use each format.
Pick the export that matches where the icon will live. Install steps live on each bundle page; exact file lists live on Export Specifications.
By destination
| Building… | Export |
|---|---|
| A website or PWA | Web Assets |
| One image for any other use | Single-File Export |
Web Assets is the common case: ICO, SVG, PWA PNGs (192/512 + maskable), Apple touch icon, manifest.webmanifest, and a ready-to-paste <head> snippet. Single-File Export is the escape hatch — one PNG, SVG, ICO, or ICNS at a size you pick.
Today, Favycons shows Web Assets and Single-File Export. Additional Export Targets such as iOS Export Bundle, Android Export Bundle, Desktop Export Bundle, and Raycast Extension Icon are not currently shown.
By format
| Format | Best for | Sized in export? |
|---|---|---|
| SVG | Modern browser tabs, scalable assets | No — inherently scalable |
| PNG | PWA icons, store uploads, spot checks | Yes |
| ICO | Windows favicons, legacy fallback | No — multi-size container |
| ICNS | macOS app icons | No — multi-size container |
From the export modal
Open Export and pick a target. Each available Export Target shows a What assets will be exported? link to the matching guide:
- Web Assets → Web Assets
- Single-File Export → Single-File Export
Other Export Targets will link to their matching guide pages when they become available.
After export
- Install files in the right folder for your framework — each bundle page covers placement.
- Validate in the browser or on-device — Troubleshooting for cache and manifest issues.
- Compare against Export Specifications if you need exact filenames and dimensions.