WordPress Favicon Generator: All Sizes From One Image
A modern favicon is a set of PNG sizes for tabs, iOS and Android plus a manifest. Generate them all from one 512×512 image in WordPress, tags included.
A favicon is a tiny thing—the little icon in a browser tab, a bookmark, a phone home screen—and it’s one of the first signals that a site is finished rather than half-built. But “add a favicon” quietly became a real chore. Dropping a 16×16 .ico in your root directory hasn’t been enough for years. Browsers, iOS and Android each want their own sizes, plus a manifest file to tie them together. Here’s how to produce the whole set from a single image—and never think about it again.
The essentials
- A complete favicon today means
favicon.ico+ PNGs at 16, 32, 48, 180, 192 and 512—not a single file. - It also needs a
site.webmanifest(Android/PWA) plus a set of<head>tags; the module still produces the legacy Windows tile andbrowserconfig.xml, which recent Windows no longer requires. - WordPress’s built-in Site Icon is incomplete—limited sizes, no manifest, no theme colour.
- The Favicon Generator builds all of it from one upload of a 512×512+ square image, with a theme colour and background colour.
- Rebrand in one step: upload a new image and every format, file and tag regenerates—no manual editing.
Which favicon formats do you actually need?
A complete favicon set today is a favicon.ico for browser tabs and bookmarks (16, 32 and 48 pixels inside one file), a 180×180 PNG Apple Touch icon for iPhone and iPad home screens, 192×192 and 512×512 PNGs for Android and installable web apps, and a site.webmanifest file pointing at them. The Windows tile and browserconfig.xml are legacy extras.
Here’s the full set a modern site should serve:
| File / format | Size | Used for |
|---|---|---|
favicon.ico | 16×16, 32×32, 48×48 | Browser tabs, bookmarks, anything requesting /favicon.ico directly |
| Apple Touch icon | 180×180 PNG | iOS home screens |
| Android Chrome icons | 192×192 and 512×512 PNG | Android home screens and Progressive Web Apps |
site.webmanifest | JSON file | Tells Android browsers about your icons and theme colour |
Windows tile + browserconfig.xml | 150×150 PNG + XML | Legacy: pinned sites in older Microsoft Edge—no longer required on recent Windows, still generated for compatibility |
That’s a lot of files and <head> tags for something that ought to be simple—which is exactly why doing it by hand is a chore you don’t want to repeat every rebrand.
Why isn’t one .ico (or the Site Icon) enough?
One .ico covers browser tabs and nothing else: iOS ignores it and Android wants PNGs listed in a manifest. WordPress’s Site Icon fills part of the gap, but it produces a limited set of sizes, no manifest and no theme colour—and once the Favicon Generator is active it takes over from the Site Icon, so the two never conflict.
The manual route is: use an online generator, download a ZIP, upload the files to your server, and paste the HTML tags into your theme’s header—then repeat the entire dance every time your logo changes, hoping you don’t miss a format.
WordPress’s built-in Site Icon in the Customizer helps, but it’s partial: it generates a limited set of sizes and doesn’t create the manifest files, so PWA icons and theme colours simply aren’t covered. You end up back at the manual generator for the rest.
How do you generate every format automatically?
Activate the Favicon Generator module in Blaminhor Essentials, upload one square image of at least 512×512 pixels, and pick a theme and background colour. On save it generates every format—favicon.ico, the PNG set, Apple Touch and Android icons, plus the legacy Windows tile—serves site.webmanifest and browserconfig.xml, and injects the <head> tags itself. Three steps:
One square image and two colours in—every favicon format, manifest and head tag out.
- Upload one image. A single high-resolution square image, at least 512×512. A logo or symbol on a transparent or solid background works best. Already have a WordPress Site Icon, or files left by the “Favicon by RealFaviconGenerator” plugin? The module’s Import tab reuses that image as the source.
- Set your colours. Pick a theme colour (the browser bar tint on Android, also written as the tile colour for legacy Windows) and a background colour (for the Android splash screen).
- Save. The module generates every format—
favicon.ico(and copies it to your site root when that folder is writable and no other favicon.ico is already there), the full PNG set, the Apple Touch icon, Android icons and the Windows tile—servessite.webmanifestandbrowserconfig.xml, and injects the<head>tags into your site.
One image in, a complete favicon everywhere out.
How do you update your favicon later?
Upload a new image in the Favicon Generator and save: every size, the manifest and browserconfig it serves, and all the head tags regenerate in one action, and the new set only replaces the old one once it has been fully generated. Rebranding stops being a generator-and-upload ritual—no files to manage, no code to touch, no meta tags to hand-edit.
One precision on the tags: the module prints them only once a set has been generated and its 32×32 file is on disk. It does not check each file individually, which is why the source image must be large enough for every size to exist (see the warning above).
A crisp favicon is a small part of a site feeling finished—it pairs naturally with tidy image handling across the rest of your media.
Favicon Generator is one of the 26 modules in Blaminhor Essentials—free and open-source on WordPress.org.
– blaminhor
FAQ
What size should my source favicon image be?
At least 512×512 pixels and square. The generator never upscales: from a smaller image it only creates the sizes your image is big enough for—a 300-pixel logo gets no 512×512 Android icon, for instance—while the tags and manifest still point to the missing files. A logo or symbol on a transparent or solid background works best—fine detail and text tend to disappear at 16×16, so simpler marks read far better as a favicon.
Why is my favicon not showing up in WordPress?
Usually your browser is showing a cached version, or the head tags point at files that aren't actually there. The Favicon Generator injects the tags and copies favicon.ico to your site root when that folder is writable and no other favicon.ico is already there—then a hard refresh clears the stale icon your browser held onto. If your source image was smaller than 512×512, some sizes were never generated: upload a larger image and regenerate.
How do I force browsers to refresh a cached favicon?
Favicons are cached aggressively. A hard refresh—Ctrl+F5, or Cmd+Shift+R on a Mac—usually does it; failing that, open the icon's URL directly, or check in a private window. Regenerating the favicon replaces the files behind the same URLs, so a hard refresh is still the reliable way to see the new one.
Can a favicon be an SVG, or must it be PNG/ICO?
Modern browsers do accept an SVG favicon for tabs, but iOS home screens and Android still expect PNG at fixed sizes (180×180, 192×192, 512×512)—so an SVG alone won't cover every surface. That's why the generator builds the full raster set from your one image rather than leaning on a single scalable file.
Can I add a favicon without a plugin?
Yes—generate the files with an online tool, upload them to your server, and paste the head tags into your theme by hand. It works, but you repeat the whole ritual on every rebrand and risk missing a format. A generator module does the same job from one upload and updates everything in a click.
Comments