void-manifest-checklist

Create a manifest.webmanifest file in your public directory with name, short_name, start_url, scope, display, theme_color, background_color, lang, dir, and icons. Reference it from your layout via metadata or a link tag, and verify it in Chrome DevTools under Application > Manifest.

You need at minimum four icons: 192x192 and 512x512 in both `any` and `maskable` purposes. Maskable icons need 20% padding around the logo so Android adaptive icons do not clip them. Generate them from one SVG with pwa-asset-generator.

The most common causes are a missing maskable icon, an invalid start_url or scope, or a manifest parse error. Open Chrome DevTools > Application > Manifest to read the installability warnings, then run a Lighthouse PWA audit for the full list.

Use manifest.webmanifest, which carries the correct MIME type, and never ship both files since duplicate manifests confuse browsers. In Next.js you can alternatively define a typed app/manifest.ts returning MetadataRoute.Manifest for typo-safe configuration.

Use `standalone`, which gives a full-screen app experience without browser UI and is the default for PWAs. The other modes — fullscreen, minimal-ui, and browser — are niche cases, with `browser` removing PWA behavior entirely.