$ apify call favicon-extractor
Favicon Extractor
Apify Actor for extracting favicons in bulk from URLs or domains, normalizing domains and returning image metadata.
platform
Apify
status
Public
pricing
$0.50 / 1,000 favicons
outputs
JSON, CSV, Excel, Dataset, Image URLs
What it does
Favicon Extractor retrieves favicons in bulk from lists of URLs or domains. It normalizes each input to a canonical domain and fetches the favicon through Google’s public faviconV2 service on gstatic.com.
The Actor is designed to enrich domain datasets with a lightweight visual signal: directories, CRMs, marketplaces, link previews, competitor dashboards or lead databases.
Main capabilities
- Accepts full URLs or bare domains.
- Normalizes inputs to canonical domains.
- Retrieves Google-cached favicons in configurable sizes.
- Returns one row per successfully extracted favicon.
- Includes source favicon URL, MIME type and byte size.
- Can save a public image copy in key-value store when enabled.
- Runs parallel requests for large domain batches.
- Does not require a browser, proxies or heavy page scraping.
Use cases
- Add icons to link previews.
- Enrich domain lists with visual brand identifiers.
- Build directories, marketplaces, CRMs or lead databases.
- Display favicons next to company websites.
- Create browser-style bookmark, tab or favorite interfaces.
- Add quick visual context to competitor dashboards.
Input
The main fields are:
urls: URLs or domains to process.size: requested favicon size.saveImages: saves public image copies in key-value store when enabled.maxConcurrency: controls parallelism for large batches.
Output
Each successfully extracted favicon is saved as one dataset item with fields such as:
inputdomainfaviconUrlstoredImageUrlcontentTypesizeBytes
Pricing
The Actor uses pay-per-event pricing. It charges for each successfully extracted favicon. The public Actor configuration lists $0.0005 per favicon, equivalent to $0.50 / 1,000 favicons.
Infrastructure and recovery
Users do not need to configure proxies or a browser. The Actor queries Google’s cached favicon endpoint, uses lightweight requests and skips failed inputs so large batches can complete without blocking the whole run.
Limits
- Results depend on Google’s public favicon cache.
- Some domains can return generic icons if Google does not have a specific favicon.
- If a domain has no favicon available in the cache, the Actor can skip it.
- The extracted favicon may not reflect very recent changes on the original website.