This is an experimental technology
Because this technology's specification has not stabilized, check the compatibility table for usage in various browsers. Also note that the syntax and behavior of an experimental technology is subject to change in future versions of browsers as the specification changes.

The web app manifest provides information about an application (such as name, author, icon, and description) in a JSON text file. The purpose of the manifest is to install web applications to the homescreen of a device, providing users with quicker access and a richer experience.

Web app manifests are part of a collection of web technologies called progressive web apps, which are web applications that can be installed to the homescreen of a device without needing the user to go through an app store, along with other capabilities such as  being available offline and receiving push notifications.

Web app manifests are deployed in your HTML pages using a link tag in the head of your document:

<link rel="manifest" href="/manifest.json">

Example manifest

  "name": "HackerWeb",
  "short_name": "HackerWeb",
  "start_url": ".",
  "display": "standalone",
  "background_color": "#fff",
  "description": "A simply readable Hacker News app.",
  "icons": [{
    "src": "images/touch/homescreen48.png",
    "sizes": "48x48",
    "type": "image/png"
  }, {
    "src": "images/touch/homescreen72.png",
    "sizes": "72x72",
    "type": "image/png"
  }, {
    "src": "images/touch/homescreen96.png",
    "sizes": "96x96",
    "type": "image/png"
  }, {
    "src": "images/touch/homescreen144.png",
    "sizes": "144x144",
    "type": "image/png"
  }, {
    "src": "images/touch/homescreen168.png",
    "sizes": "168x168",
    "type": "image/png"
  }, {
    "src": "images/touch/homescreen192.png",
    "sizes": "192x192",
    "type": "image/png"
  "related_applications": [{
    "platform": "web"
  }, {
    "platform": "play",
    "url": ""



Defines the expected background color for the web application. This value repeats what is already available in the application stylesheet, but can be used by browsers to draw the background color of a web application when the manifest is available before the style sheet has loaded. This creates a smooth transition between launching the web application and loading the application's content.

"background_color": "red"

Note: The background_color member is only meant to improve the user experience while a web application is loading and must not be used by the user agent as the background color when the web application's stylesheet is available.


Provides a general description of what the web application does.

"description": "The app that helps you find the best food in town!"


Specifies the primary text direction for the name, short_name, and description members. Together with the lang member, it can help provide the correct display of right-to-left languages.

"dir": "rtl",
"lang": "ar",
"short_name": "أنا من التطبيق!"

It may be one of the following values:

  • ltr (left-to-right)
  • rtl (right-to-left)
  • auto (hints to the browser to use the Unicode bidirectional algorithm to make a best guess about the text's direction.)

Note: When the value is omitted, it defaults to auto.


Defines the developer's preferred display mode for the web application.

"display": "standalone"

Valid values are:

Display Mode Description Fallback Display Mode
fullscreen All of the available display area is used and no user agent chrome is shown. standalone
standalone The application will look and feel like a standalone application. This can include the application having a different window, its own icon in the application launcher, etc. In this mode, the user agent will exclude UI elements for controlling navigation, but can include other UI elements such as a status bar. minimal-ui
minimal-ui The application will look and feel like a standalone application, but will have a minimal set of UI elements for controlling navigation. The elements will vary by browser. browser
browser The application opens in a conventional browser tab or new window, depending on the browser and platform. This is the default.  (None)

Note: You can selectively apply CSS to your app based on the display mode, using the display-mode media feature. This can be used to provide a consistent user experience between launching a site from an URL and launching it from a desktop icon.


Specifies an array of image objects that can serve as application icons in various contexts. For example, they can be used to represent the web application amongst a list of other applications, or to integrate the web application with an OS's task switcher and/or system preferences.

"icons": [
    "src": "icon/lowres.webp",
    "sizes": "48x48",
    "type": "image/webp"
    "src": "icon/lowres",
    "sizes": "48x48"
    "src": "icon/hd_hi.ico",
    "sizes": "72x72 96x96 128x128 256x256"
    "src": "icon/hd_hi.svg",
    "sizes": "72x72"

Image objects may contain the following values:

Member Description
sizes A string containing space-separated image dimensions. 
src The path to the image file. If src is a relative URL, the base URL will be the URL of the manifest.
type A hint as to the media type of the image.The purpose of this member is to allow a user agent to quickly ignore images of media types it does not support.


Specifies the primary language for the values in the name and short_name members. This value is a string containing a single language tag.

"lang": "en-US"


Provides a human-readable name for the application as it is intended to be displayed to the user, for example among a list of other applications or as a label for an icon.

"name": "Google I/O 2017" 


Defines the default orientation for all the web application's top level browsing contexts.

​​"orientation": "portrait-primary"

Orientation may be one of the following values:

  • any
  • natural
  • landscape
  • landscape-primary
  • landscape-secondary
  • portrait
  • portrait-primary
  • portrait-secondary

Specifies a boolean value that hints for the user agent to indicate to the user that the specified related applications (see below) are available, and recommended over the web application. This should only be used if the related native apps really do offer something that the web application can't do.

"prefer_related_applications": false

Note: If omitted, the value defaults to false.

Specifies an array of "application objects" representing native applications that are installable by, or accessible to, the underlying platform — for example a native Android application obtainable through the Google Play Store. Such applications are intended to be alternatives to the web application that provide similar or equivalent functionality — like the native app version of the web app.

"related_applications": [
    "platform": "play",
    "url": "",
    "id": "com.example.app1"
  }, {
    "platform": "itunes",
    "url": ""

Application objects may contain the following values:

Member Description
platform The platform on which the application can be found.
url The URL at which the application can be found.
id The ID used to represent the application on the specified platform.


Defines the navigation scope of this web application's application context. This basically restricts what web pages can be viewed while the manifest is applied. If the user navigates the application outside the scope, it returns to being a normal web page.

If the scope is a relative URL, the base URL will be the URL of the manifest.

"scope": "/myapp/"


Provides a short human-readable name for the application. This is intended for use where there is insufficient space to display the full name of the web application.

"short_name": "I/O 2017"


Specifies the URL that loads when a user launches the application from a device. If given as a relative URL, the base URL will be the URL of the manifest.

"start_url": "./?utm_source=web_app_manifest"


Defines the default theme color for an application. This sometimes affects how the application is displayed by the OS (e.g., on Android's task switcher, the theme color surrounds the application).  

"theme_color": "aliceblue"

Splash screens

In Chrome 47 and later, a splash screen is displayed for a web application launched from a home screen. This splashscreen is auto-generated using properties in the web app manifest, specifically: name, background_color, and the icon in the icons array that is closest to 128dpi for the device.

Mime type

Manifests should be served using the application/manifest+json MIME type. However, it is optional to do so.  


Specification Status Comment
Web App Manifest Working Draft Initial definition.

Browser compatibility

Feature Android Android Webview Firefox Mobile (Gecko) IE Mobile Opera Mobile Safari Mobile Chrome for Android
Basic support No support 39.0 ? ? 32.0 ? 39.0
background_color No support 46.0[1] ? ? (Yes) ? 46.0 [1]
theme_color No support 46.0[1] ? ? No support ? 46.0 [1]
icons, name, short_name, and theme_color used for Add to home screen feature. ? (Yes) 53.0 (53)[2] ? No support ? (Yes)
Feature Chrome Firefox (Gecko) Internet Explorer Opera Safari (WebKit)
Basic support No support No support No support No support No support

[1] Does not support lang or scope.

[2] The icons, name, short_name, and theme_color fields of the Web App Manifest (if present) can now be as the source of the homescreen/apps window icons, apps window title, homescreen icon title, and apps window color (respectively) for "Add to home screen" (Firefox Mobile only; see bug 1234558).

Document Tags and Contributors

 Last updated by: chrisdavidmills,