Articles · Media workflow · 4 Aug 2026

Favicon sizes and export

If you are staring at search results for favicon size, you probably need one of three things: the pixel chart, a read on your file, or square PNGs ready to upload.

You search for “favicon size” because something small is blocking a launch: a blurry tab icon, a WordPress Site Icon warning, or a manifest that expects 512×512 while your logo is 800×200.

Favicon work splits into three jobs that people often mix up: know the numbers, check your file, and export the right squares. Toolcore keeps those as separate entry points so you land on the step you actually need.

When you only need the size chart

Start with Favicon sizes or the main Favicon size & dimensions page when the question is purely reference: what does 32×32 vs 180×180 vs 512×512 mean, and where does each one show up?

Browser tabs usually want 32×32 (with 16×16 as a legacy fallback). Apple home-screen icons expect 180×180. PWA manifests commonly ask for 192×192 and 512×512. Windows pinned tiles often reference 48×48 or larger squares.

You do not need to memorize every row. Bookmark the chart, pick the row that matches your HTML link tag or CMS field, then move to export.

When you need to read your image first

If the real question is “what size is my favicon image?”, open Favicon dimensions. Upload the file and read width×height in the browser—nothing is sent to a server.

The page tells you whether the image is square, whether it already matches a standard size, and which standard size is closest if it does not. That matters because a square 500×500 logo is valid geometry but still wrong if WordPress or your manifest expects exactly 512×512.

Non-square artwork gets center-cropped on export. If your mark sits near the edge, add padding in a graphics tool before you resize, or the 16×16 tab preview will clip text you care about.

WordPress Site Icon (512×512)

WordPress is a common reason people land on favicon size guides. Under Appearance → Customize → Site Icon, upload a square image at least 512×512 px. WordPress generates smaller variants for the front end and admin bar.

Upload your source logo to the dimensions checker, confirm it meets the minimum, then export 512×512 PNG from the same workflow. Modern WordPress uses PNG Site Icon—not a classic favicon.ico—though you may still want tab sizes for non-WordPress pages on the same domain.

Classic .ico files are multi-layer, not one size

A favicon .ico bundles several square bitmaps inside one binary—typically 16×16, 32×32, and 48×48 px. Browsers pick the best layer for the context. Searching for “favicon ico size” usually means learning that stack, not finding a single magic pixel count.

Toolcore exports PNG at one chosen size per download. For a legacy .ico, export 16, 32, and 48 px separately, then combine them with an ICO builder in your toolchain. Many new sites skip .ico entirely and ship PNG plus a web manifest instead.

Export every common size in one pass

When you already know the sizes and just want the files, use the Favicon generator. Upload once and download the usual square set for tabs, touch icons, and PWA surfaces.

Use the size checker when you are auditing an existing asset or exporting one specific pixel count. Use the generator when you are shipping a fresh icon pack after a rebrand.

Quick map: which page do I open?

Mistakes that survive “it looks fine on my laptop”

Shipping one tiny PNG everywhere is the most common slip. Tabs, iOS home screens, and PWA splash screens do not share one resolution. At minimum, most teams ship 32×32 for tabs, 180×180 for Apple touch, and 512×512 for manifests or WordPress.

Another is treating a wide logo as favicon-ready. Center crop helps, but it cannot invent margins you never designed. Leave breathing room around the mark before export.

All of the favicon tools above run in your browser. That keeps draft logos off a server when you are still iterating—handy before a public rebrand goes live.

Common use cases

  • Answer “what size should a favicon be?” before editing HTML link tags or a PWA manifest.
  • Prepare a WordPress Site Icon without guessing whether 512×512 is required.
  • Decide between the size checker (one export) and the favicon generator (full PNG set).

Common mistakes to avoid

  • Using one small PNG for every surface

    Tabs, Apple touch, and PWA splash screens need different squares. Ship at least 32, 180, and 512 px—or use the favicon generator for the set.

  • Skipping a dimension read on non-square logos

    Center crop is convenient but clips edge text. Add padding before export if the mark must stay intact at 16×16.

FAQ

What is the standard favicon size for browser tabs?

32×32 px is the common modern tab icon, with 16×16 as a legacy fallback. Many sites also ship 180×180 for Apple touch and 512×512 for PWA or WordPress.

Does Toolcore upload my logo?

No. Dimension checks and PNG export run on canvas in your browser only.

Should I use favicon-size or the favicon generator?

Use favicon-size when you need the chart, a dimension read, or one target export. Use the favicon generator when you want every common size in one pass.