Get Inspired
Docs
Blog
Articles
Chrome Apps
Transitioning from Chrome Apps
What Are Chrome Apps? Chrome Apps Architecture Chrome App Lifecycle
Create Your First App
Build a Todo Chrome App Step 1: Create and Run a Chrome App Step 2: Import an Existing Web App Step 3: Add Alarms and Notifications Step 4: Open External Links With a Webview Step 5: Add Images From the Web Step 6: Export Todos to the Filesystem Step 7: Publish Your App
Samples
Content Security Policy Run Chrome Apps on Mobile Using Apache Cordova Offline First External Content Storage APIs Managing HTML5 Offline Storage Native Messaging User Authentication USB Devices Serial Devices Network Communications Bluetooth MVC Architecture Build Apps with AngularJS Build Apps with Sencha Ext JS Game Engines Publish Your App Analytics Autoupdating
Disabled Web Features Web APIs
Chrome Apps
Transitioning from Chrome Apps
What Are Chrome Apps? Chrome Apps Architecture Chrome App Lifecycle
Create Your First App
Build a Todo Chrome App Step 1: Create and Run a Chrome App Step 2: Import an Existing Web App Step 3: Add Alarms and Notifications Step 4: Open External Links With a Webview Step 5: Add Images From the Web Step 6: Export Todos to the Filesystem Step 7: Publish Your App
Samples
Content Security Policy Run Chrome Apps on Mobile Using Apache Cordova Offline First External Content Storage APIs Managing HTML5 Offline Storage Native Messaging User Authentication USB Devices Serial Devices Network Communications Bluetooth MVC Architecture Build Apps with AngularJS Build Apps with Sencha Ext JS Game Engines Publish Your App Analytics Autoupdating
Disabled Web Features Web APIs

Manifest Version

Caution

Important: Chrome will be removing support for Chrome Apps on all platforms. Chrome browser and the Chrome Web Store will continue to support extensions. Read the announcement and learn more about migrating your app.

One integer specifying the version of the manifest file format your package requires. As of Chrome 18, developers should specify 2 (without quotes) to use the format as described by this document:

"manifest_version": 2

Consider manifest version 1 deprecated as of Chrome 18. Version 2 is not yet required, but we will, at some point in the not-too-distant future, stop supporting packages using deprecated manifest versions. Extensions, applications, and themes that aren't ready to make the jump to the new manifest version in Chrome 18 can either explicitly specify version 1, or leave the key off entirely.

The changes between version 1 and version 2 of the manifest file format are described in detail in the manifest_version documentation.

Caution

Setting manifest_version 2 in Chrome 17 or lower is not recommended. If your extension needs to work in older versions of Chrome, stick with version 1 for the moment. We'll give you ample warning before version 1 stops working.

Improve article

This site uses cookies to deliver and enhance the quality of its services and to analyze traffic. If you agree, cookies are also used to serve advertising and to personalize the content and advertisements that you see. Learn more about our use of cookies.