Web App Manifest Validator

Build a manifest from fields or review supplied JSON and a bounded local file.

On-device No sign-up Free to use

Validate manifest controls

Drop your file here

or choose one from your device

One UTF-8 file up to 1 MiB. Use either this or the pasted text, not both.

    ?

    Paste the file contents, or leave this empty and choose the file. Nothing is fetched from the addresses in the file.

    ?

    Used by Write. One icon per line as src,sizes and an optional purpose. The addresses are written into the file and never fetched.

    ?

    Check reads a manifest you paste or choose. Write builds one from the fields below.

    ?

    Used by Write. The full name a home screen shows under the icon.

    ?

    Used by Write. A short label for a home screen where the full name does not fit.

    ?

    Used by Write. The page that opens when the app launches, such as / or /app/.

    ?

    Used by Write. Declares the installed app’s navigation scope. It does not grant permissions, restrict visitor access or set service-worker control.

    ?

    Used by Write.

    ?

    Used by Write. A hex colour such as #0f172a.

    ?

    Used by Write. The colour shown while the app starts.

    ?

    Used by Write. A language tag such as en or en-GB.

    Result

    Showing an example.

    Inspect the provided manifest with explicit name/start/scope and two icon declarations: eight keys and no local failed/review checks.

    0 failed and 0 checks to review in 8 keys. This reads the file only, so it does not tell you whether a browser will offer to install the app.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/web-app-manifest-validator · 20 November 2026

    Was this helpful?

    How to use Web App Manifest Validator

    1. Choose Check a manifest and paste its JSON, or clear the text and select one UTF-8 file. Use Write a new manifest to build a draft from fields instead.
    2. For a new draft, enter name, start URL, optional scope, display/colors/language and icon rows as src,sizes[,purpose]. No icon URL is fetched.
    3. Select Validate manifest to run the selected Check or Write mode. Read the local results; normalized scope checks cover two root-relative paths or two absolute URLs. Other forms need the real manifest URL.
    4. Download or copy the draft after review. Test the linked manifest, icons and install/navigation behavior on the actual served site; this page does not install an app.

    Example: Web App Manifest Validator

    Inspect the provided manifest with explicit name/start/scope and two icon declarations: eight keys and no local failed/review checks.

    You add
    What to do: validate; manifest.json text: { "name": "Example App", "short_name": "Example", "start_url": "/", "scope": "/", "display": "standalone", "theme_color": "#0f172a", "background_color": "#ffffff", "icons": [ {"src": "/icons/icon-192.png", "sizes": "192x192", "type": "image/png"}, {"src": "/icons/icon-512.png", "sizes": "512x512", "type": "image/png", "purpose": "any maskable"} ] }; Application name: Example App; Short name: Example; Start URL: /; Scope: /; Display mode: standalone; Theme colour: #0f172a; Background colour: #ffffff; Language: en; Icons for a new manifest: /icons/icon-192.png,192x192,any /icons/icon-512.png,512x512,any maskable
    You get
    0 failed and 0 checks to review in 8 keys. This reads the file only, so it does not tell you whether a browser will offer to install the app.

    Options

    manifest.json text
    Paste the file contents, or leave this empty and choose the file. Nothing is fetched from the addresses in the file.
    manifest.json file (optional)
    One UTF-8 file up to 1 MiB. Use either this or the pasted text, not both.
    What to do
    Check reads a manifest you paste or choose. Write builds one from the fields below.
    Application name
    Used by Write. The full name a home screen shows under the icon.
    Short name
    Used by Write. A short label for a home screen where the full name does not fit.
    Start URL
    Used by Write. The page that opens when the app launches, such as / or /app/.
    Scope
    Used by Write. Declares the installed app’s navigation scope. It does not grant permissions, restrict visitor access or set service-worker control.
    Display mode
    Used by Write.
    Theme colour
    Used by Write. A hex colour such as #0f172a.
    Background colour
    Used by Write. The colour shown while the app starts.
    Language
    Used by Write. A language tag such as en or en-GB.
    Icons for a new manifest
    Used by Write. One icon per line as src,sizes and an optional purpose. The addresses are written into the file and never fetched.

    Supported inputs and limits

    • Pasted JSON is capped at 1,000,000 characters; file intake is bounded separately and decoded as UTF-8.
    • Up to 100 icon entries are inspected.
    • The local checklist requests explicit name/start values and is stricter than some browser fallback defaults; a failed local check is not a complete standards-conformance verdict.
    • Only known fields and supported URL/scope/color/icon syntax are reviewed.
    • No real manifest-base resolution, icon fetch/pixel/MIME check, service-worker test or installation eligibility determination.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Manifest scope describes navigation, not permissions

    A manifest describes presentation and launch behavior for an installed web app. Its navigation scope tells the browser which URLs belong to that app experience; it does not protect those URLs or grant service-worker control. Icon paths, size declarations and maskable purposes also need actual artwork and server checks. Keep the manifest linked from the page, verify how relative URLs resolve and test the resulting experience in the browsers your visitors use.

    Questions about Web App Manifest Validator

    Does a clean report mean my app can be installed?

    No. These are local checks of the supplied object. Actual installation depends on the browser, linked manifest, served page and other conditions. Some local checks request explicit values that a browser can otherwise obtain from defaults, so review their meaning rather than treating the count as a universal validity score.

    Why does the scope check fail?

    For two root-relative paths or two absolute URLs, the tool normalizes URLs and checks equal origin plus a start path beginning with the scope path. It cannot correctly resolve every relative/absolute mixture without the manifest’s real URL. A browser can ignore an unsuitable scope and use a default, so verify actual app navigation rather than treating this local result as access control.

    Can the checker look at my icons?

    It reads the src and sizes values as text and reports the sizes it understood. It does not request the files, so it cannot tell you that the addresses resolve, that a file really is PNG, or that the artwork has the safe area a maskable icon needs. Open the icon in an image viewer for that.

    What does it mean that no entry sets a purpose?

    A missing purpose is read as any, which is the normal default. A home screen that crops an icon to its own shape may then use a file with content near the edges, so pairing a maskable copy with a plain one lets each surface pick the file it can use.

    Why is a key listed as one this page does not check?

    The list of keys the page knows covers the ones that matter for a first check, such as name, start_url, scope, display, colours and icons. A shortcut, share target or protocol handler is reported as a key that is present and left to the browser, because its rules depend on the rest of the page.

    Page updated · Project managed by Tony Hines · Report a problem with Web App Manifest Validator