Favicon Extractor
Pricing
$0.50 / 1,000 favicon extracteds
Favicon Extractor
Extract website favicons in bulk from URLs or domains. Fast, lightweight, no proxies, no browser. Returns favicon URL, stored image link, content type, and size. Ideal for directories, CRMs, link previews, and domain enrichment.
Pricing
$0.50 / 1,000 favicon extracteds
Rating
0.0
(0)
Developer
DataScraperES
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
17 hours ago
Last modified
Categories
Share
Get website favicons in bulk from URLs or domains. This Actor returns one clean dataset item per successfully retrieved favicon, with the favicon URL, normalized domain, image metadata, and an optional public image URL stored in Apify Key-Value Store.
What This Actor Does
Favicon Extractor takes a list of websites and retrieves their favicons using a lightweight favicon lookup flow.
For each input URL or domain, the Actor:
- Normalizes the input to a clean domain.
- Looks up the favicon for the normalized domain.
- Optionally stores the downloaded image in Apify Key-Value Store.
- Saves the result metadata to the Apify Dataset.
It is built for fast, simple favicon enrichment. It does not crawl full websites, render pages, parse HTML, or use proxies.
Pricing
This Actor uses pay-per-result pricing.
| Event | Price | What is charged |
|---|---|---|
favicon | $0.50 / 1,000 results | Each favicon successfully retrieved and pushed to the dataset |
Equivalent event price:
$0.0005 per favicon result
You are charged only for successful favicon results. Invalid inputs, failed requests, and skipped domains are not pushed to the dataset and are not charged as favicon results.
Platform usage is included in the result price. You do not need to configure or pay for proxies for this Actor.
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 or tab interfaces.
- Add lightweight brand context to competitor dashboards.
Input
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
urls | string[] | Yes | - | URLs or bare domains to process. |
size | string | No | "64" | Requested favicon size in pixels. Select one of: "16", "32", "64", "128", "256". |
storeImage | boolean | No | true | If enabled, stores the favicon image in Key-Value Store and returns image_url. |
concurrency | integer | No | 10 | Number of favicons to fetch in parallel. Allowed range: 1 to 50. |
Example Input
{"urls": ["apify.com","https://www.stripe.com","github.com","https://stripe.com/pricing"],"size": "128","storeImage": true,"concurrency": 10}
Input Normalization
The Actor accepts both complete URLs and bare domains.
Examples:
| Input | Domain used |
|---|---|
https://www.apify.com/store | apify.com |
github.com/openai/codex | github.com |
https://stripe.com/pricing?plan=pro | stripe.com |
www.shopify.com | shopify.com |
Paths, query parameters, ports, protocols, and leading www. are removed before favicon lookup.
Duplicate domains are processed independently if they appear multiple times in the input.
Output
Each successful favicon produces one dataset item.
| Field | Type | Description |
|---|---|---|
input_url | string | Original URL or domain from the input. |
domain | string | Normalized domain used for favicon lookup. |
favicon_url | string | Resolved URL that can be used to fetch the favicon directly. |
image_url | string or null | Public URL to the stored favicon image when storeImage=true; otherwise null. |
content_type | string | MIME type returned for the favicon, such as image/png or image/x-icon. |
size_bytes | integer | Downloaded favicon size in bytes. |
Example Output
{"input_url": "apify.com","domain": "apify.com","favicon_url": "https://example.com/favicon.png","image_url": "https://api.apify.com/v2/key-value-stores/abc123/records/favicon_apify_com.png","content_type": "image/png","size_bytes": 1029}
Stored Images
When storeImage is enabled, the Actor stores each downloaded favicon in the run's default Key-Value Store.
The dataset item includes image_url, which can be used directly in applications, dashboards, CSV exports, or API integrations.
When storeImage is disabled, the Actor still returns favicon_url, content_type, and size_bytes, but image_url is null.
Run Summary
At the end of each run, the Actor stores a SUMMARY record in the default Key-Value Store. This record is not a Dataset result and is not charged as a favicon result.
Example summary:
{"total_inputs": 1000,"processed": 1000,"succeeded": 942,"failed": 58,"stored_images": 942,"requested_size": 64,"store_image": true,"concurrency": 50,"spending_limit_reached": false,"charged_event_name": "favicon"}
Use this summary to quickly check how many inputs were processed, how many produced favicon results, how many failed, and whether the run stopped because of the spending limit.
Favicon Size
The size input requests a preferred icon size. The Actor returns the best available favicon image up to that size.
For example:
- requesting
256does not guarantee a 256 px image; - if only a 32 px favicon is available, the Actor may return that smaller icon;
64is a good default for most dashboards and tables;128or256is better when the icon will be displayed larger.
Error Handling
Failed inputs are skipped and logged.
Common reasons for skipped inputs:
- empty or invalid input value;
- no favicon response available for the domain;
- non-image response;
- timeout or network error.
Skipped inputs do not appear in the dataset and are not charged as favicon results.
Important Notes
- This Actor does not use proxies.
- This Actor does not open websites in a browser.
- This Actor does not parse website HTML.
- A generic default icon may be returned when no specific favicon is available for a domain.
- The returned favicon depends on the icon data available for each domain.
- Results are available in Apify Dataset exports such as JSON, CSV, Excel, XML, RSS, and via API.
Recommended Settings
For small batches:
{"urls": ["apify.com", "github.com", "stripe.com"],"size": "64","storeImage": true,"concurrency": 10}
For larger batches:
{"urls": ["..."],"size": "64","storeImage": true,"concurrency": 50}
For metadata-only use:
{"urls": ["apify.com", "github.com"],"size": "64","storeImage": false}