Fantasy video game environment, stone (ico multisize)
The same 512x512 photograph written as ico multisize. One file holding four resolutions; a reader that takes the first gets 16 pixels. Every member of this group is identical pixels, so a decoder returning different dimensions or a different pixel count has lost something rather than simply produced a different file; the 24-bit PNG in this group is lossless and is the reference the lossy members are measured against Source plate g-fantasy-keep.
Specifications
- Sizes
- 16, 32, 48, 256
- Lossless
- true
- Width
- 512
- Height
- 512
- Variant
- ico-multisize
- Source Plate
- g-fantasy-keep.png
- Synthetic
- true
- Disclosure
- AI-generated / synthetic. Not a photograph of a real person, place or event.
- Schema Version
- 1
- Alt Text
- Fantasy video game environment, stone keep on a cliff at sunset
- Alt Text Source
- prompt
Testing contract
Expected to pass- Scenario
- Decode this file and the 24-bit PNG in the same group, compare dimensions and pixel count, then check the decoded properties against the ones declared in its specs.
- Expected result
- It decodes to 512x512 with the properties in its specs. The encode is lossless, so it must decode to the reference pixel for pixel. Every member of this group is the same source image, so a reader that returns different dimensions has demonstrably lost something rather than read a different file.
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
“Fantasy video game environment, stone (ico multisize)” is a deterministic Novus Examples fixture for Media handling. Generated stills, clips and audio published in several encodings of identical content, so a media pipeline can be tested on format handling, quality loss and frame or sample extraction against a reference that is known rather than assumed.
Documented properties for this file: 512×512. 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.
For image AI or enhancement tools, run the model or filter on this file and diff against the clean or ground-truth companion in the same group when available. Keep seeds and documented damage parameters in your evaluation notes so regressions are attributable.
Code examples
<img src="g-fantasy-keep-ico-multisize.ico" alt="Example image" width="640" loading="lazy">Related files
- webpA barista in her twenties (WebP q85)The same plate as WebP at quality 85, for format-handling coverage beside the PNG and JPEG encodings of identical pixels Plate owner-cafe.
- webpA Black man in his seventies (WebP q85)The same plate as WebP at quality 85, for format-handling coverage beside the PNG and JPEG encodings of identical pixels Plate p-market-sen.
- avifA Black man in his seventies with grey (avif lossy)The same 512x350 photograph written as avif lossy. AV1 still image: modern, small, and unsupported by a surprising amount of tooling. Every member of this group is identical pixels, so a decoder returning different dimensions or a different pixel count has lost something rather than simply produced a different file; the 24-bit PNG in this group is lossless and is the reference the lossy members are measured against Source plate p-market-sen.
- bmpA Black man in his seventies with grey (bmp 24bit)The same 512x350 photograph written as bmp 24bit. BMP stores rows bottom-up, so a reader that ignores that returns the image flipped. Every member of this group is identical pixels, so a decoder returning different dimensions or a different pixel count has lost something rather than simply produced a different file; the 24-bit PNG in this group is lossless and is the reference the lossy members are measured against Source plate p-market-sen.
- gifA Black man in his seventies with grey (gif 256)The same 512x350 photograph written as gif 256. GIF cannot hold more than 256 colours, so this is quantised by the format itself. Every member of this group is identical pixels, so a decoder returning different dimensions or a different pixel count has lost something rather than simply produced a different file; the 24-bit PNG in this group is lossless and is the reference the lossy members are measured against Source plate p-market-sen.
- heicA Black man in his seventies with grey (heic)The same 512x350 photograph written as heic. What an iPhone produces by default, and what a lot of pipelines still cannot read. Every member of this group is identical pixels, so a decoder returning different dimensions or a different pixel count has lost something rather than simply produced a different file; the 24-bit PNG in this group is lossless and is the reference the lossy members are measured against Source plate p-market-sen.
Generated by generation/image_format_wave.py. Free for any use, no attribution required, license.