ZenovayTools

PWA Manifest Checker

Validates your Progressive Web App manifest.json for Chrome installability: name, icons (192×192 + 512×512), display mode, start_url, maskable icons, theme_color, screenshots. Installability grade A-F.

How to Use PWA Manifest Checker

  1. 1Enter your website URL — the tool finds your manifest.json automatically.
  2. 2The manifest is fetched and validated against Chrome PWA installability requirements.
  3. 3Icon sizes (192×192, 512×512, maskable) and required fields are checked.
  4. 4A grade A-F reflects how ready your site is for PWA installation.
Zenovay

Track your website performance

Real-time analytics, session replay, heatmaps, and AI insights. 2-minute setup, privacy-first.

Try Zenovay Analytics — Free

Frequently Asked Questions

What makes a PWA installable on Chrome?
Chrome requires all of these for the install prompt: (1) A web app manifest linked from HTML with <link rel="manifest">. (2) A name field in the manifest. (3) A start_url field. (4) A display value of "standalone", "fullscreen", or "minimal-ui". (5) Icons with at least 192×192 and 512×512 sizes. (6) The site served over HTTPS. Missing any of these will prevent Chrome from showing the install button in the address bar.
What is a maskable icon and why do I need one?
Maskable icons (purpose: "maskable") are designed to be safe to crop into any shape — circle, squircle, rounded square, etc. — depending on the device's launcher. Without a maskable icon, Android may add a white circle background behind your icon, which looks inconsistent. The "safe zone" for maskable icons is the central 80% of the image — keep your logo within this area. You need both a regular icon (purpose: "any") and a maskable icon for best results. Use maskable.app to check and create maskable icons.
What is the difference between display modes in the manifest?
display controls the browser UI shown when the app is launched: "standalone" — app-like, no browser address bar (most common choice). "fullscreen" — covers entire screen, no system UI (used for games). "minimal-ui" — shows some browser navigation but hides the address bar. "browser" — opens in the full browser (defeats the purpose of PWA). Use "standalone" for most apps. Note: Safari on iOS uses standalone display only when the user adds to home screen via share menu — the install banner works differently on iOS.
Why should I add screenshots to my manifest?
Screenshots (the screenshots array) are used by Chrome's enhanced install UI, which shows a rich install dialog with app name, description, and preview images. Without screenshots, Chrome uses a minimal install prompt. They're also used in the Chrome Web Store and some app store listings. Include at least 2 screenshots for the wide (desktop) form factor and 2 for narrow (mobile). Dimensions must be between 320×320 and 3840×2160 pixels with a consistent aspect ratio.
Does my PWA need a service worker for installability?
Yes — a service worker is required for the PWA install prompt on Chrome (though this validator only checks the manifest). The service worker must be registered on the page and be in a working state. A minimal service worker that just responds to fetch events is sufficient. The service worker enables offline functionality and is part of the three PWA pillars: manifest + service worker + HTTPS. Tools like Workbox (workbox-window) make service worker setup much simpler.