What should a rule correction include?
- The stable rule ID shown in the result.
- The expected outcome and the outcome you received.
- A current official source URL from the platform owner.
Contact Icon Checker
Email hello@iconchecker.com to report an incorrect icon rule, a reproducible checker bug, or a request for another icon target.
Maintained by Icon Checker
What should a bug report include?
- The checker URL, browser, and operating system.
- Exact dimensions, file size, and the displayed error.
- A minimal reproducible file when sharing it is safe.
Where should I send a report?
Send the report to hello@iconchecker.com. Use a concise subject that names the checker and problem. For file parsing bugs, a minimal PNG that reproduces the result is more useful than a screenshot alone. Do not attach a private or unreleased production asset when a reduced test file can demonstrate the same behavior.
Which sources help verify a rule correction?
Link the platform owner’s current documentation rather than a third-party checklist. Icon Checker primarily maps rules to Apple, Google Play Console, Android Developers, and Google Search Central.
What should I not email?
Do not email passwords, access tokens, customer data, private signing assets, or unpublished application source. App icon files are analyzed locally and never need to be emailed to use the checker. A website URL submitted to the favicon checker should already be publicly accessible; do not send private-network addresses or credentials.
Contact questions
Short answers for the most common rule-correction and bug-report questions.