webmanifest1.5 KB

Web app manifest with form-factor screenshots

A manifest with the members that turn a bare install prompt into a rich one: four screenshots split across wide, narrow and unspecified form factors, labels, categories and two shortcuts (one with its own icon). For testing rich-install eligibility rules.

Web assets JSON parsing Schema validation

Preview — first 50 lineswebmanifest

{
  "name": "Example Rich Install",
  "short_name": "RichInstall",
  "id": "/?src=screens",
  "start_url": "/?src=screens",
  "scope": "/",
  "display": "standalone",
  "description": "Sample manifest whose screenshots drive a richer install dialog.",
  "categories": [
    "productivity",
    "utilities"
  ],
  "theme_color": "#059669",
  "background_color": "#0e1116",
  "icons": [
    {
      "src": "/icons/icon-192.png",
      "sizes": "192x192",
      "type": "image/png"
    },
    {
      "src": "/icons/icon-512.png",
      "sizes": "512x512",
      "type": "image/png"
    }
  ],
  "screenshots": [
    {
      "src": "/screens/wide-1.png",
      "sizes": "1280x800",
      "type": "image/png",
      "form_factor": "wide",
      "label": "Dashboard on desktop"
    },
    {
      "src": "/screens/wide-2.webp",
      "sizes": "1280x800",
      "type": "image/webp",
      "form_factor": "wide",
      "label": "Report view on desktop"
    },
    {
      "src": "/screens/narrow-1.png",
      "sizes": "750x1334",
      "type": "image/png",
      "form_factor": "narrow",
      "label": "Dashboard on mobile"
    },
    {
      "src": "/screens/no-form-factor.png",

… 73 lines total — download for the full file.

Specifications

Seed: 70400
Site: example.com (fictional)
Format: W3C Web App Manifest
Screenshots: 4
Form Factors: wide, narrow, unset
Shortcuts: 2

Testing contract

Expected to pass

Scenario: Evaluate rich-install eligibility on a desktop and on a phone.
Expected result: Desktop uses the two wide screenshots, mobile uses the single narrow one, the screenshot with no form_factor is treated as suitable for any surface, and both shortcuts appear in the app's context menu.

What is a .webmanifest file?

A web app manifest (.webmanifest) is a JSON file that describes a Progressive Web App to the browser, declaring its name, icons, theme colors, start URL, and display mode. It enables installation to a device home screen and standalone launching. It is linked from HTML via a manifest link element.

How to use this file

Use an example webmanifest to test PWA installability, manifest JSON parsing, icon and display-mode handling, and browser or auditing tools like Lighthouse.

How to use this file for testing

“Web app manifest with form-factor screenshots” is a deterministic Novus Examples fixture for Web assets, JSON parsing, Schema validation. Favicons, web app manifests, service workers, robots and sitemap files, Open Graph images, and .well-known resources — for testing web tooling, crawlers, PWA installers, and asset pipelines.

Documented properties for this file: seed 70400 · W3C Web App Manifest. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Web-platform fixtures are standards-compliant samples against fictional example.com data. Test crawlers, PWA installers and manifest validators, favicon/icon pipelines, service-worker registration, or .well-known parsers against the documented structure.