Quick answer
Both packages were built from the same synthetic 512×512 two-color mark with maskable output enabled. The only changed variable was the Include legacy sizes setting.
- Last verified
- July 31, 2026
- Evidence
- Primary documentation plus transparent editorial analysis
- Primary sources
- 1
Controlled comparison
Both packages were built from the same synthetic 512×512 two-color mark with maskable output enabled. The only changed variable was the Include legacy sizes setting.
The modern-core archive contained the generated SVG, multi-frame ICO, browser PNGs, Apple icon, ordinary and maskable PWA icons, manifest, HTML, and README.
Connected next stepCase Study: A Transparent Mark Inside a Maskable Icon for the closest prerequisite or comparison.
Measured result
With legacy sizes disabled, the ZIP contained 14 files, including 9 PNGs, and weighed 8,447 bytes. With legacy sizes enabled, it contained 25 files, including 20 PNGs, and weighed 14,481 bytes.
For this unusually simple artwork, legacy output added 11 files and increased the compressed archive by 6,034 bytes—about 71%. Complex artwork will produce different absolute weights, which is why the dataset states its source conditions.
Connected next stepCase Study: Turning a Wordmark Into a 16px Favicon for the next connected implementation decision.
Practical conclusion
File weight is rarely the main reason to avoid historical sizes; operational clutter and unexplained assets are. Default to the modern core, then add legacy exports when a documented browser, installed-app, or enterprise-client requirement justifies them.
Connected next stepCompare the published package evidence and verify the decision with a working output.
Review the headings, sources, implementation artifact, and update record for this guide as structured JSON.
Download guide evidence ↓- Guide
- Case Study: Replacing Legacy Favicon Files With a Lean Set
- Coverage
- Client behavior can change by browser, operating system, platform version, cache state and deployment configuration. Unperformed manual observations are not claimed.
Questions, answered
Does a larger package slow every page?+
Only files actually requested affect a page load, but extra declarations and poorly cached candidates can create unnecessary requests.
Should favicon.ico still contain several frames?+
Yes. The modern core can keep a concise multi-frame ICO without exporting every historical standalone PNG.