Design
Web app manifest generator and checker
Build the manifest.webmanifest file that tells browsers your site's name, icons and colours, and how it opens from a home screen. Every field is explained, with notes on which browsers use it. Check the result, or an existing manifest, against Chrome's install requirements and Safari's behaviour, and preview it on a phone and a computer.
- Every manifest field
- Install checks
- Phone and desktop previews
Free, no sign-up. Everything stays in your browser.
Nothing you enter leaves your browser.
This tool runs in your browser and needs JavaScript. Turn JavaScript on and reload the page.
Favicon generator
Preview and download
In a browser tab
On a home screen
Approximate: each phone maker draws icons in its own shape and size.
Your files
Code for the <head> of your pages
For WordPress: functions.php code
Paste this below the first line (<?php) of your child theme's functions.php, or into a code snippets plugin. Only use it if you upload the files yourself: see the WordPress steps below.
manifest.webmanifest
Built from the settings above and your icons. To add a description, shortcuts, screenshots and more, and to check it, open the Web app manifest tab: what you set there is used here and in the ZIP.
Adding a favicon to WordPress
There are two ways. Pick one: using both prints two sets of icon tags.
The simple way: the Site Icon
- Download android-chrome-512x512.png. WordPress needs a square image at least 512 by 512 pixels.
- In WordPress 6.5 and later, go to Settings › General and choose Site Icon. In WordPress 4.3 to 6.4, go to Appearance › Customize › Site Identity. With a block theme you can also turn on Use as site icon in the Site Logo block's settings in the Site Editor.
- Save. WordPress makes 32, 180, 192 and 270 pixel copies and adds the icon tags to every page itself.
WordPress also answers requests for /favicon.ico by redirecting to the 32 pixel Site Icon, as long as there is no real favicon.ico file in the site's root. The Site Icon has no SVG, no maskable icon and no manifest, and it uses the same image everywhere, including as the iPhone home-screen icon, so a transparent logo gets no solid background there.
The full set: upload the files
- Download the ZIP and unzip it.
- Upload the files with SFTP or your host's file manager to the folder you entered above, except favicon.ico. For the root, that is the folder that holds wp-admin, wp-includes and wp-login.php (often public_html). Put favicon.ico in the root whatever folder you use: browsers ask for /favicon.ico on their own, and the code links it there.
- Remove the Site Icon in Settings › General (or the Customizer), so WordPress stops printing its own icon tags.
- Add the head code: paste the functions.php code into your child theme or a code snippets plugin, or the HTML into your theme's or SEO plugin's header code setting.
- Open your site in a private window to check. Browsers keep favicons for a long time, so an old icon can linger in your normal window.
Do not edit a parent theme's files: an update replaces them. Make a child theme first if you do not have one.
What each file is for
| File | Size | Used by |
|---|---|---|
favicon.ico | 16, 32 and 48 px | Every browser, and anything that asks for /favicon.ico without reading your page, such as feed readers. Each size is a PNG inside the icon file. |
favicon-16x16.png, favicon-32x32.png | 16 and 32 px | Browser tabs and bookmarks, on standard and high-resolution screens. |
favicon.svg | Any size | Chrome, Edge, Firefox and Safari 26 and later, which draw it sharp at every size. Made only from text: an uploaded SVG is turned into PNG files, never copied, because an SVG file can carry scripts. |
apple-touch-icon.png | 180 px | iPhone and iPad, when someone adds your site to the home screen. iPhone and iPad round the corners themselves, so this is a full square with a solid background. |
android-chrome-192x192.png, android-chrome-512x512.png | 192 and 512 px | Android home screens, install prompts and splash screens, through manifest.webmanifest. Chrome asks for at least these two sizes. |
maskable-icon-512x512.png | 512 px | Android launchers that cut icons to a shape. Listed in the manifest with "purpose": "maskable". |
manifest.webmanifest | Text | Your site's name, colours and icons for Android and installed web apps. |
Sources: web.dev: Add a web app manifest (opens in a new tab), web.dev: maskable icons (opens in a new tab), MDN: Define your app icons (opens in a new tab), Apple: Configuring Web Applications (opens in a new tab) and Google Search Central: favicons (opens in a new tab).
Preview and check
Approximate: each browser and system draws these its own way. Icons from the Favicon tab, or icons at a full https:// address, are shown; your browser loads such addresses directly.
manifest.webmanifest
Code for the <head> of your pages
If you also use the Favicon tab, its code already includes these lines: use one or the other.
For WordPress: functions.php code
Adding a manifest to WordPress
Upload the file and add the tags
- Download manifest.webmanifest and upload it with SFTP or your host's file manager to the folder you chose, with the icons it lists. For the root, that is the folder that holds wp-admin and wp-login.php.
- Add the head code: paste the functions.php code into your child theme or a code snippets plugin. It prints the tags with WordPress's esc_url() and esc_attr(), and builds addresses with home_url(), so they follow your WordPress address.
- Open the manifest's address in your browser to check it loads, then open your site in Chrome and look in DevTools › Application › Manifest for any warnings.
Some SEO and PWA plugins add their own manifest. Use only one: browsers read only the first manifest link on a page.
What a manifest does not do
A manifest describes the site; it does not make it work offline or send notifications. Those need a service worker, a script your site registers, which is separate from this file. Chrome's install criteria do not ask for one.
WordPress.org's PWA feature plugin, which added a service worker, has not been tested with the last three major WordPress releases, so check its status before relying on it.
Sources: MDN: Web app manifests (opens in a new tab), web.dev: install criteria (opens in a new tab), W3C: Web Application Manifest (opens in a new tab).
What you get
-
Name, description, addresses, display mode, orientation and colours
-
Icons from the Favicon tab, or your own maskable and monochrome icons
-
Screenshots, shortcuts, share target, protocol handlers and more
-
Checks for Chrome and Edge installs, Safari and every value
-
Home screen, splash screen and app window previews in light and dark
-
The JSON file, the head tags and WordPress code with escaping
How to make a web app manifest
-
Fill in your site's details
Enter your site's name, a short name for home screens and its colours, and choose how it opens. Make your icons on the Favicon tab, or list your own. Or paste an existing manifest to load it.
-
Fix what the checks find
The checks show what Chrome and Edge need before they promote installing the site, what Safari does on iPhone and iPad, and any value or address that is wrong, with the fix for each.
-
Upload it and add the tags
Download manifest.webmanifest, upload it to your site with its icons, and add the head tags, or the WordPress code for your child theme.
What a web app manifest does
A web app manifest is a small JSON file, linked from the head of every page, that describes your site to browsers and operating systems: its name, its icons, its colours and how it opens when someone installs it or adds it to a home screen. Chrome and Edge use it to decide whether to promote an install, Android uses it for the home-screen icon and the splash screen, and Safari reads its name, display mode and icons.
Not every field works everywhere
Browsers support different parts of the manifest. Name, icons, start URL, scope and display mode are widely read. Others, such as shortcuts, screenshots, share targets and protocol handlers, work only in some browsers, and a few are still experimental. The notes beside each field say where it works, based on MDN's browser compatibility data, so you can leave out what you do not need.
A manifest is not a service worker
The manifest describes your site; it does not make it work offline or send notifications. Those need a service worker, which is a separate script. Chrome's install requirements do not ask for one, so a manifest and icons are enough for an install.
Frequently asked questions
What does Chrome need before it offers to install a site?
The site must be served over https, and its manifest must have a name or short name, a 192 and a 512 pixel icon, a start URL, and a display mode of standalone, minimal-ui, fullscreen or window-controls-overlay. prefer_related_applications must be absent or false. Chrome also waits until the visitor has clicked or tapped the page and spent at least 30 seconds on it.
Should I call the file manifest.json or manifest.webmanifest?
Either works, because browsers read the file the link points to. The specification suggests the .webmanifest extension, so this tool uses manifest.webmanifest.
Does Safari use the web app manifest?
Yes, partly. Safari reads the name, short name, start URL, scope, display mode, id and theme colour, and uses the manifest's icons only when there is no apple-touch-icon. On iOS 26 and later, every site added to the Home Screen opens as a web app unless the person turns that off.
How long should the short name be?
Short enough to fit under an icon on a home screen: about 12 characters or fewer. Longer short names are often cut off, and if there is no short name, the full name is used and cut instead.
What is the difference between start_url, scope and id?
start_url is the page that opens from the icon. scope is the part of the site that belongs to the app; pages outside it open in the browser, and it must contain the start URL. id is the app's permanent identity, so you can change the start URL later without the installed app becoming a different one.
How do I add a web app manifest to WordPress?
Upload manifest.webmanifest and its icons to your site, then add the head tags. The easiest way is the functions.php code this tool writes, pasted into a child theme or a code snippets plugin; it prints the tags with WordPress's own escaping. Make sure no other plugin adds a second manifest.
Is anything I enter sent anywhere?
No. The manifest is built and checked in your browser, and a pasted manifest is read there too. Your site's address is used only for the checks and is never fetched. To count how the tool is used, this site is told only that it was used, copied or downloaded.
Related tools
-
Create a WordPress child theme with style.css, functions.php and a ZIP download.
-
Colour palette generator
New (added recently)Browse 240 colour palettes or build one from your brand colour, each with a dark mode version, contrast checks and code to copy.
-
SEO report
New (added recently)Check one page’s SEO basics and PageSpeed, then download the report as a PDF.
-
Email signature generator
New (added recently)Make an HTML email signature that works in Outlook, Gmail and Apple Mail, with a desktop, mobile and dark mode preview.