Skip to main content

Icon Checker

Use this free icon checker to test size, format, and transparency before you publish. Each result shows the file facts and the official rule.

Maintained by Icon Checker

App icon files stay in your browser. No upload or sign-up required.

Checking a website? Open the Favicon Checker

Icon check

Drop a PNG here

Use a PNG for the selected iOS or Google Play target.

App icon files are analyzed in this browser and are not uploaded.

Check an icon file before you publish

Measure the file's size, format, and transparency, then compare the evidence with the rules for the release target you choose.

  • 1024 x 1024 dimensions
  • PNG structure and decode
  • Alpha channel and transparent pixels

What is Icon Checker?

Icon Checker keeps three separate audit paths, not one measurement reused everywhere. A public website URL goes through the favicon audit. Local PNG files are checked against the app icon target you choose, with each target using its own rules and evidence.

Use the icon checker that matches the asset you are releasing. A pass on one page does not apply to the others. Favicon, App Store, and Play listing files are different assets with different rules.

Separate favicon, iOS app icon, and Google Play icon audit paths

Choose the right icon checker

Choose where the icon will be used. Each icon checker applies a different set of rules.

Favicon

Check declarations, icon files, Google Search requirements, touch icons, and manifest coverage.

Open checker

iOS App Icon

Check a 1024 x 1024 PNG for dimensions, alpha, transparency, and small-size clarity.

Open checker

Google Play

Check a 512 x 512 RGBA PNG for file size, sRGB, and transparency.

Open checker

Checking share tags instead of an icon file? Open the Open Graph Checker.

How the icon checker works

This icon checker reads a local iOS or Play file, then compares the measurements with the selected platform rules. Every result shows what was measured, what was required, and where the rule came from. Favicon checks are a separate URL audit.

  1. Read the file

    Decode the PNG and inspect its real structure.

  2. Measure the image

    Record dimensions, bytes, alpha, color data, and pixels.

  3. Apply target rules

    Use only the rules for the selected platform.

  4. Show the evidence

    Show the value, requirement, fix, and source.

What automated checks cannot decide

A technical pass documents file facts. It cannot judge brand quality or predict store approval. Each checker also leaves a different remainder for people: iOS presentation and App Review, Play listing mask and launcher assets, or live browser and search display.

Common icon checker problems before release

An icon can look finished and still contain a measurable export error. Fix the file problem for the target platform instead of applying one generic rule to every icon.

The file has the wrong canvas size

Check the decoded width and height against the selected target. Use the original artwork when re-exporting instead of enlarging a small raster image and introducing soft edges.

Transparency is treated as one universal rule

Apply the platform-specific result. A Primary iOS icon can fail for alpha metadata, while a Google Play listing icon may contain transparency and a favicon follows another set of format and surface rules.

The filename says PNG but the bytes disagree

Trust the detected file signature and successful decode, not the extension. Re-export a standard PNG when the structure is invalid or the browser cannot decode the image completely.

The color profile is unknown

Convert artwork to sRGB when the target requires it and embed the profile during export. An untagged file should remain a warning when the original color intent cannot be proved.

A platform mask is baked into the source

Keep the underlying artwork square unless the official asset format says otherwise. Let the operating system or store apply its final corner mask and shadow treatment.

The icon works large but fails small

Use the Scale Rail or surface previews to inspect reduced sizes. Simplify tiny text, thin strokes, crowded detail, or weak contrast when the mark stops reading clearly.

Favicon, iOS, and Google Play rules are different

There is no universal pass for an icon file. Each checker uses a different input and keeps hard requirements separate from recommendations and manual design review.

TargetInput to checkKey evidence
Website faviconPublic page URLHTML declarations, reachable files, decoded sizes and formats, Google Search eligibility, Apple touch icon, and manifest coverage
iOS Primary / Any1024 x 1024 PNGExact square dimensions, PNG structure, alpha or tRNS metadata, decoded pixels, and small-size review
Google Play listing512 x 512 PNG32-bit RGBA, exact byte limit, sRGB metadata, transparency evidence, decode, and small-size review

A practical icon checker workflow

Run the icon checker on the final asset close to release, then keep the evidence with the export decision. This prevents a corrected file from being replaced by an older draft later in the workflow.

  1. 1

    Choose the real target

    Decide whether the asset is a website favicon, an iOS Primary icon, or a Google Play listing icon. Do not use one result to approve a different asset role.

  2. 2

    Check the final export

    Run the file or public URL that is actually scheduled for release. Read measured and expected values before changing artwork or export settings.

  3. 3

    Verify the real surface

    After deterministic failures are fixed, inspect the icon in the browser, built app, store workflow, and small-size previews relevant to the release.

  • Resolve hard failures

    Correct invalid bytes, dimensions, format, alpha, byte limits, or unreachable resources before reviewing visual polish.

  • Investigate warnings

    A warning means evidence is incomplete or a recommendation needs review; it is not a hidden pass.

  • Keep platform assets separate

    Do not confuse a touch icon with an App Store icon or a Play listing image with an adaptive launcher icon.

  • Check reduced sizes

    Make sure the mark, spacing, and contrast survive the smallest presentation that matters for the target.

  • Retest after export

    Every re-export can change metadata, file size, color profile, or alpha behavior, so run the corrected asset again.

  • Keep the result scoped

    A technical pass documents measured rules. It cannot guarantee search display, device rendering, or store approval.

Icon checker questions

Short answers about this free icon checker and which page to open next.