Favicon (multi-size ICO)
A multi-resolution favicon.ico bundling 16, 32, 48, and 64 px images of the brand mark — for testing favicon parsers, ICO decoders, and multi-image icon handling.
Specifications
- Sizes
- 16, 32, 48, 64 px
- Images
- 4
- Format
- ICO
- Use
- <link rel=icon>
What is a .ico file?
ICO is a Windows icon container that bundles multiple image sizes and bit depths in a single file so the system can pick the best resolution. Each entry is stored as a BMP-style bitmap or embedded PNG, commonly at sizes like 16, 32, and 48 pixels. It is the traditional format for application and website favicons.
How to use this file
Use an example ICO to test favicon and icon extraction, multi-resolution selection, and converters that build ICO files from PNG sources.
How to use this file for testing
“Favicon (multi-size ICO)” is a deterministic Novus Examples fixture for Web assets, Conversion testing. Favicons, web app manifests, service workers, robots and sitemap files, Open Graph images, and .well-known resources — for testing web tooling, crawlers, PWA installers, and asset pipelines.
Documented properties for this file: ICO. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Web-platform fixtures are standards-compliant samples against fictional example.com data. Test crawlers, PWA installers and manifest validators, favicon/icon pipelines, service-worker registration, or .well-known parsers against the documented structure.
Code examples
<img src="favicon.ico" alt="Example image" width="640" loading="lazy">Related files
- atomFeed twin - Atom 1.0The same four articles as Atom 1.0: tag: ids identical to the RSS twin, RFC 3339 published and updated timestamps, escaped HTML content, and both alternate and self links. For diffing an RSS-to-Atom converter against a known answer.
- jsonFeed twin - JSON Feed 1.1The third twin: the same four articles as JSON Feed 1.1, using the 1.1 `authors` array rather than the 1.0 singular form, with ids, URLs, summaries, HTML bodies and timestamps identical to the RSS and Atom files. The reference output for an XML-to-JSON feed converter.
- rssFeed twin - RSS 2.0Four articles of a fictional publication as RSS 2.0, with a self-referential atom:link, non-permalink tag: GUIDs, RFC 822 dates and full HTML bodies in content:encoded. One of three twins carrying identical content, so a feed converter can be diffed against a known answer.
- pngPNG icon sprite (5-icon strip)A 320×64 PNG icon sprite (five 64×64 cells) — the raster twin of the SVG sprite, for testing background-position sprite techniques and sprite slicers.
- svgSVG icon sprite (symbol sheet)An SVG sprite sheet defining five reusable icons as <symbol> elements referenced by <use href='#id'> — for testing SVG sprite pipelines and icon systems. Paired with a PNG sprite twin.
- otfOTF — CFF (Cubic) OutlinesThe same design in CFF outlines: cubic Type 2 charstrings with no glyf and no loca. The half of the pair that catches code assuming every OpenType font is TrueType-flavoured. Original typeface, free to use.
Generated by generation/web_assets.py. Free for any use, no attribution required — license.