Web App Manifest Generator

Generate PWA manifest.json files with app name, icons, theme colors, and display mode configuration.

Tested tool guide Tested browser tools Checked August 16, 2026

What Web App Manifest Generator does and how it behaves

A web app manifest tells a browser how an installable web experience should be named, represented, colored, and displayed. This generator collects an app name, icon settings, theme color settings, and a display mode, then formats those choices as manifest JSON. Its output is a declaration, not a finished PWA: the site still has to serve the file and reference it from HTML, icon URLs must resolve, and each browser decides which manifest members it supports. A syntactically correct result therefore does not guarantee that an install prompt will appear.

How the result is produced

Manifest field mapping

The app-name control supplies the manifest's name member. Icon configuration becomes the icons array, the selected theme color becomes theme_color, and the display choice becomes display. The produced document is a JSON object, not an HTML tag or JavaScript object literal. Keep its JSON syntax intact when copying it: member names and string values require double quotes, and a trailing comma is invalid JSON.

Connecting the result

After generation, host the JSON at a stable site URL and connect it to pages with <link rel="manifest" href="/manifest.json"> inside the HTML head. A browser fetches that URL and interprets supported members. Relative icon URLs resolve against the manifest's own URL, not necessarily the page URL. Selecting standalone expresses a preferred installed-app display mode; it does not change an ordinary browser tab.

Good uses

Preparing the initial manifest for a small web app when you know the title, icon locations, brand color, and preferred display mode but want correctly structured JSON instead of hand-assembling nested icon objects.
Checking how a revised theme color or display selection changes the manifest before replacing a site's current manifest file.
Creating a manifest fixture for documentation, a prototype, or a local browser test where deterministic app metadata is more useful than a large production manifest.

Limits and checks

Valid JSON is not an installability verdict. Check separately that each page links to the served manifest, referenced resources return successfully, and the target browser's current install criteria are met. An install prompt may be absent even when the generated text parses.
Icon metadata is descriptive. A sizes value must describe the actual image dimensions, and purpose affects how a supporting browser may crop or present an icon. Supplying one icon or mislabeled dimensions can leave browsers without a suitable image; manifest generation does not create the underlying icon files.
The display member is a preference, not a command to hide browser controls everywhere. It matters when the app is launched in an installed context, and a browser can use a fallback when the requested mode is unsupported. Normal visits in a tab are still normal browser pages.

Common questions

Where should I put the generated JSON?

Save it as a JSON resource on the same site you are describing, commonly /manifest.json, then add a manifest link in the HTML head. The filename is conventional, not required; the link's href identifies the resource. No, merely downloading the file or pasting the object into a JavaScript block does not connect it to the site's pages.

Will standalone display mode remove the address bar?

Only when a browser launches an installed app using that supported display mode. It does not remove controls from a regular tab, and it does not force every browser to honor the preference. If the mode cannot be used, manifest processing applies display fallback behavior, so test the installed experience in each target browser.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.