Toolsky

Free Online Tools & Utilities for Every Task.

PWA Manifest Generator

Create a fully compliant Web App Manifest (manifest.json) for your Progressive Web App in seconds.

Please solve the captcha first.
Live Preview
9:41

Get Started

Every installable web app starts with one small JSON file. The Web App Manifest tells the browser your app's name, the colours of its splash screen, which page to open when someone taps the home-screen icon, and where the icon files live. The tricky part is not the concept — it is the syntax. One trailing comma, one wrong display value, and the browser silently ignores the whole file. A PWA manifest generator removes that risk: you fill in your app's details in plain form fields, and it produces a valid manifest.json you can drop straight into your project. If you want the underlying rules, the W3C Web App Manifest specification defines every member described below.

What the Web App Manifest Does

When a browser finds a link to a manifest in your page's head, it reads the file to decide how the site should behave once installed. The manifest controls the name shown under the home-screen icon, the start URL that opens on launch, whether the app runs in a browser tab or a standalone window, the background colour shown while the app loads, and the theme colour that tints the system UI around it. Without a valid manifest, browsers will not offer installation at all — the file is small, but it is the gatekeeper for the entire PWA experience.

Fields the Generator Helps You Set

  • name — the full app name, used on install dialogs and splash screens.
  • short_name — a compact version for the home screen, where space under the icon is limited.
  • description — a plain-language summary of what the app does.
  • start_url — the page that opens when the installed app launches, often the homepage with a tracking parameter.
  • display — standalone, fullscreen, minimal-ui or browser, deciding how much browser chrome surrounds your app.
  • theme_color and background_color — the colours for the top bar and the loading splash screen.
  • icons — the set of icon files and sizes the browser can choose from, including 192×192 and 512×512 pixel versions.

How to Create Your manifest.json

  1. Enter your app's full name and a short name that still makes sense at a glance.
  2. Add a one-sentence description of the app.
  3. Set the start URL — usually your homepage or the main app screen.
  4. Choose a display mode; standalone suits most apps because it hides the address bar.
  5. Pick a theme colour that matches your site's header and a background colour for the splash screen.
  6. List your icon files with their sizes, making sure the paths point at images that actually exist on your server.
  7. Copy or download the generated JSON, save it as manifest.json, upload it to your site, and link it from every page's head.

A Manifest in Practice

Say you run a recipe blog called Fork & Flame and want readers to install it. Your generated manifest might declare the name "Fork & Flame Recipes", the short name "Fork&Flame", a start URL of "/?source=pwa" so your analytics can tell installed-app visits apart, display set to standalone, a theme colour of deep tomato red (#b3402a) matching your header, a white background colour, and two icons: a 192×192 PNG for the home screen and a 512×512 PNG for high-resolution splash screens. Prepare the icons first — an image resizer can produce the exact pixel sizes from your logo — then reference their real paths in the manifest. Once the file is live, run the site through a PWA compatibility check to confirm the browser can read everything.

Mistakes That Stop a Manifest Working

The most common failure is a manifest that exists but cannot be fetched: the link tag points at /manifest.json while the file actually sits in a subfolder, so the browser gets a 404 page instead of JSON. Close behind are invalid JSON (hand-edited files with trailing commas or unquoted keys), icon entries whose files were renamed later, a start URL that falls outside the manifest's scope, and forgetting that icon sizes must be honest — declaring a 512×512 icon that is really 256×256 can fail install checks. Another quiet trap: editing the manifest but keeping an aggressive cache, so visitors' browsers keep reading last month's version. Generate the file cleanly, then verify the live copy, not just the one on your laptop.

Frequently Asked Questions About the Web App Manifest

Where should manifest.json live on my server?

Anywhere reachable by URL — the site root is conventional. What matters is that the link tag in your HTML points at its real location and that it is served without errors.

Which icon sizes are actually required?

Chrome's install criteria expect at least a 192×192 and a 512×512 pixel icon. Adding intermediate sizes and a maskable version gives browsers better material for different devices and icon shapes.

Is the theme-color meta tag the same as theme_color in the manifest?

They set the same colour in different places: the meta tag applies while browsing in a tab, the manifest value applies to the installed app. Keep them identical for a consistent look.

Can one website have more than one manifest?

Only one manifest is used per page — the browser takes the first valid link it finds. Sites sometimes generate a different manifest per section, but each page still ends up with exactly one.

What display mode should I choose?

Standalone is the safe default: your app gets its own window and task-switcher entry without the browser address bar. Fullscreen suits games and media; browser is for when you deliberately want normal tab behaviour.

Does changing the manifest update already-installed apps?

Browsers periodically re-fetch the manifest, so name and icon changes eventually reach installed users, though the timing is platform-dependent and not instant.

Is a manifest enough to make my site a PWA on its own?

No. You also need HTTPS and a registered service worker. The manifest handles identity and appearance; the service worker handles caching and offline behaviour.

One Small File, a Much More App-Like Site

Treat the manifest as part of your site's identity rather than an afterthought: generate it carefully, keep its paths accurate after every redesign, and your visitors get an app that looks deliberate from the first tap.