One request turns any site's icon into a clean, compact SVG 0 times so far. It is sanitized or traced in a sandbox, fitted to its box, and cached, so your users never touch the site.
Icons and palettes come live from this server's API. Take the controls to try it yourself.
One GET per site, no key, CORS open. The SVG comes back with the colours to put around it, for light and dark themes. Everything below is this server answering live.
.svg get a cacheable 301 to the registrable domain.200 with a generated one, and the headers say why./light or /dark follows the viewer's system theme by itself.X-Icon-Fillbleed to draw it edge to edge, inset to pad it on the plateX-Icon-*-Platea badge fill that keeps the icon visible, never one that swallows a cut-out logoX-Icon-*-Textthe brand colour at 4.5:1 on the theme backgroundX-Icon-*-Monothe colour for the mono mask, at least 3:1, on its Mono-Platefavicons.page is a public service, not a demo. Point your app, browser extension, mail client, bookmark manager or dashboard at it: there is no account to create and no quota to request.
The URL is the whole integration. CORS is open and every header, palettes included, is readable from the browser.
Icons are cacheable for 30 days and served from a CDN, so a popular icon costs this server about one request a month.
/color/{domain} and /mono/{domain} are the contract. The 1.x line keeps them unchanged.
Per-network limits keep it fair for everyone. For millions of icons a day or anything critical, run your own copy from one compose file.
Leave the theme out of a badge URL and it switches with the viewer's system scheme. Pin /light or /dark when your app has its own toggle.
Ids and classes in every SVG are unique to that icon, so any number of them can share one page without clashing.
The 100,000 most popular sites answer instantly: their icons ship prerendered with this server, picked from Majestic Million (CC BY 3.0), the Cisco Umbrella list and the Chrome UX Report (CC BY-SA 4.0).
Start with the API or npm i favicons.page, with components for React, Vue, Svelte and plain HTML, read llms.txt or openapi.json, or host it yourself.
Optional icon catalogs are served by slug, with the same palettes and masks as domains.
Every byte from a site is hostile until it has been rebuilt by us.
HTML, manifests and images are handled in a throw-away seccomp process with no files, network or exec.
parser exploitsdecompression bombsAn allowlist writer emits paths and gradients. Scripts and embedded images cannot be expressed, and the only CSS is the server's own theme switch.
script injectiontracking pixelsPublic addresses over https on port 443 only, no links or redirects to raw IPs, and every foreign host vetted before connecting.
metadata endpointsinternal networksPer-recipient subdomains collapse to the site. Users' IPs never reach it and are never logged.
per-recipient trackingBlocklists, domain age via RDAP and a filtering DNS resolver. Blocked sites get a warning icon.
phishingfresh malware domainsPer-subnet limits and a round-robin queue keep honest clients served during a flood.
floodsnoisy neighbourswrk on the same machine as the service, asking for random cached icons from random client subnets with rate limiting on. No socket errors and no non-2xx responses in any run.
4 × 1.6 GHz · 3.5 GB · 8 GB eMMC
The CPU gave out first, and half of it went to the kernel moving packets rather than to favicons.
12 cores · 36 GB
wrk and favicons shared the six performance cores; the service itself was not short of CPU.
Every day a GitHub Action pulls each project's latest image on linux/amd64, starts it with default settings and reads its memory after it has sat idle. Stars and versions come from GitHub on the same run.
One docker compose up -d. The API fetches and caches; the renderer decodes untrusted images in seccomp-confined workers with no network, a read-only root and no capabilities. The image is about 9 MB.
loading…Save the file and run docker compose up -d.
Ask it for an icon: http://localhost:8080/color/github.com. Want this page too? Build with --features site.
Point a CDN at it. Icons are cacheable for 30 days, so the server sees about one request per icon per month.
Check the sandbox on your kernel: docker run --rm favicons/favicons sandbox-selftest net must exit with 159.
TLS with Let's Encrypt, S3, GCS or Azure caches, blocklists and every option: config.example.toml.
loading…Mount it with ./favicons.toml:/etc/favicons.toml:ro and set FAVICONS_CONFIG=/etc/favicons.toml. Any key also works as an environment variable, e.g. FAVICONS_POLICY__MIN_DOMAIN_AGE_DAYS=7.