Favicondl API vs Icon Horse API

Two free Art & Design APIs compared on access, reliability and developer ratings, using data from our daily health checks.

The verdict

Choose Favicondl API if its data fits your use case better; on access and reliability it's level with Icon Horse API.
Choose Icon Horse API if its data fits your use case better; on access and reliability it's level with Favicondl API.

	Favicondl API	Icon Horse API
What it does	Get any website's favicon by URL (SVG/PNG/ICO), with JSON metadata and fallbacks.	Favicons for any website, with fallbacks.
Provider	favicondl	Icon Horse
API key	Not needed	Not needed
HTTPS	Yes	Yes
CORS (browser calls)	Yes	Yes
Status today	Online · 714 ms	Online · 994 ms
Uptime (30 days)	Up	Up
Developer rating	Not rated yet	Not rated yet
Price	Free / free tier	Free / free tier

Get any website's favicon by URL (SVG/PNG/ICO), with JSON metadata and fallbacks.

Free favicon API: get any website's icon by URL with one GET request, no API key. Redirect to the image or get JSON with the icon URL and its source.

Strengths

Favicons for any website, with fallbacks.

Get any site's icons on demand, with confidence

Strengths

Prototyping or a tutorial? Pick the one that needs no API key (both qualify).
Calling from a web page? You need CORS. Otherwise route requests through your own server or a serverless function.
Going to production? Favour HTTPS, a strong uptime record and a provider with clear rate limits and terms. Check each API's docs before you commit.
Still unsure? Both are free to try: send one request to each and compare the data you get back.

Neither needs an API key; you can call both straight away.