Skip to content

Manifest member in Manifest

description manifest member

Published Updated

Limited availabilityNot supported in Firefox (Desktop), Firefox (Android), Safari (macOS), Safari (iOS)W3C draft

The description manifest member is a single string that says what the web app does. The W3C Application Information registry defines it as store-listing metadata; Chromium additionally shows it to the user in the richer install dialog, next to the screenshots, and exposes it as the accessible description of the installed app.

Chrome 88, Edge 88, Samsung Internet 15.0, and Android WebView 88 read the member (BCD manifests.webapp.description). The compat data records no support in Firefox and Safari; on Firefox for Android the property parses but has no effect.

Property Value
Type string. Plain text; HTML is not interpreted and line breaks are collapsed in the install dialog.
Default absent. With no description Chrome’s install dialog shows only the name, origin, and icon, and a store listing falls back to whatever text the packager asks for.
Example value "Track your habits and build streaks, even offline.".

A value that is not a string is dropped with the parser’s generic message, property 'description' ignored, type string expected.. There is no length limit in the format, but Chrome’s install surfaces truncate, and DevTools warns once the string passes 300 characters. Write the first sentence to stand alone.

The member is the default-language text. description_localized (see the localization entry) carries per-language variants keyed by BCP 47 tag; Chromium falls back to description when no variant matches the UI language.

Both examples ship the same text; they differ in where it is read.

Writing a description that survives truncation

Section titled “Writing a description that survives truncation”

Put the app’s distinguishing feature in the first clause and keep the whole string well under 300 characters. The second sentence is safe to lose.

{
"name": "Habit Ledger",
"short_name": "Habits",
"description": "Track daily habits and build streaks, fully offline. Export to CSV, sync when you are back online, no account needed.",
"screenshots": [
{ "src": "/shots/narrow-1.png", "sizes": "1080x1920", "type": "image/png", "form_factor": "narrow" }
]
}

Chrome 94 on Android and Chrome 108 on desktop render this text in the richer install dialog only when at least one screenshot is present; without screenshots the plain dialog omits the description.

Checking the shipped description from a deployment test

Section titled “Checking the shipped description from a deployment test”

No API reports whether the browser or a store used the text. What a test can do is assert that the deployed manifest carries a non-empty string within the truncation budget. The fallback branch handles contexts with no document (a Node test runner).

export async function describedManifest(manifestUrl = '/manifest.webmanifest') {
const manifest = await fetch(manifestUrl).then((r) => r.json());
const text = manifest.description;
if (typeof text !== 'string' || text.trim() === '') {
return { ok: false, reason: 'description missing' };
}
if (text.length > 300) {
return { ok: false, reason: `description is ${text.length} chars; Chrome truncates past 300` };
}
return { ok: true, text };
}

Run it against the production URL after each deploy; a CDN that strips or rewrites the manifest shows up here before it shows up in the install dialog.

Specifications

SpecificationStatus
Web App Manifest: descriptionW3C draft
  • Legend
  • Yes
  • Partial
  • Flag
  • No
  • Unknown
Browser / PlatformSupportVersionsConfidenceSourceNotes
Chrome (Desktop)#Yes88highsource—
Chrome (Android)#Yes88highsource1
Edge (Desktop)#Yes88highsource2
Firefox (Desktop)#No—highsource3
Firefox (Android)#No—highsource4
Safari (macOS)#No—highsource5
Safari (iOS)#No—highsource67
Samsung Internet#Yes15.0highsource8
WebView (Android)#Yes88highsource9
  1. Derived by browser-compat-data mirroring from Chrome.
  2. Derived by browser-compat-data mirroring from Chrome.
  3. No Firefox support is recorded in browser-compat-data.
  4. The property parses, but has no effect.
  5. No Safari support is recorded in browser-compat-data.
  6. No Safari on iOS support is recorded in browser-compat-data.
  7. Derived by browser-compat-data mirroring from Safari.
  8. Derived by browser-compat-data mirroring from Chrome Android.
  9. Derived by browser-compat-data mirroring from Chrome Android.

Source data: /compatibility/manifest-description.json · Global usage: 75 % (StatCounter 2026-09, CC BY-SA 4.0)

Source: spec · MDN · Last verified 2026-10-03 · Confidence: high (computed from sources)