`Manifest file is invalid` when installing my chrome extension?

my chrome extensions
download chrome extension
chrome os extensions
chrome app
chrome web store mobile

This is my manifest.json


  "name": "Environment Quick Switch",

  "version": "1.0",

  "description": "Quick switch around develop environments.",

  "browser_action": {

    "default_icon": "icon.png",
    "popup": "action.html"


  "permissions": [

    "tabs", "http://*/*", "https://*/*"



I load it's folder in develop mode is OK, but after I packaged it and try to install the .crx file, comes the Manifest file is invalid problem .

Is anyone knows how to deal with this?

I got this error too when I updated my extension. I think it happens sometimes when your extension is propagating to various servers. I came and looked at this thread and then went back to the store and tried again and it was fine.

103281, I made some small changes and published a new version in the Chrome webstore. Then I uninstalled the previous version from my Chrome browser, and​  This problem appears when I try to install it via the plugin page on the Chrome Web Store, not locally. – Pedro Menezes Jul 10 '12 at 20:06 The manifest file is correct.

I finally fixed this problem, it's just because my develop folder's path contains Chinese characters, moved it to a English path can solve this.

Chrome web store error: "Manifest file is invalid" for extension , and now my users that try to install it get this error : Manifest file is invalid. So I tried to revert to the previous version of my extension that worked,  Chrome says my extension's manifest file is missing or unreadable. extension it said the manifest file was missing or unreadable. invalid` when installing my

I had the same problem. The zip-file was accepted in the developer dashboard, but I got an error message saying that my manifest-file was invalid when installing from the webstore.

No Chineese characters on my end, it seemed like the problem was with character encoding.

I saved the manifest.json-file as ANSI - not UTF8 - and the package was accepted by the chrome webstore.

So Chrome keeps telling me manifest file is invalid? : betterponymotes, As the title says, Chrome claims invalid manifest file when I try to install from the I dealt with something similar on one of my extensions previously, having to do​  So Chrome keeps telling me manifest file is invalid? As the title says, Chrome claims invalid manifest file when I try to install from the website. Any idea whats wrong and how I can fix it?

I got this error too , I think maybe your resources under a SkyDrive folder or some team code Management soft folder . Try to copy the resources to another path, such as desktop. package your plugin with the new path , then your may success !

Package is invalid because filenames starting with "_" are reserved , I'm using Chrome 27 and can't install the Google Hangouts extension. the manifest.json file lists the minimum version of Chrome required as (a bug,  Adware is known to cause problems with browser extensions, these browser extensions are known to throw errors such as failed to load extension, manifest is missing in several web browsers, including Chrome. Get rid of Malware with Malwarebytes. Malwarebytes is free to use, detect and remove malware from your PC.

I just had this problem with a version number. forgetting to prefix my pre-1.0 release with a 0 as in "0.95" allowed it to upload and pass to publish, but fail to install.

In summary: ".95" bad, "0.95" good

My mistake for forgetting to install locally (was a migration), but still should probably be caught by the uploader.

Invalid manifest file Chrome Web Store (crx file can't be updated , Non of that and a bunch of random reuploads. What we have: We can install app from a local folder, so we guess we have a valid manifest file Our attempts  Manifest File Format. Every extension has a JSON-formatted manifest file, named manifest.json, that provides important information. Field summary. The following code shows the supported manifest fields for Extensions, with links to the page that discusses each field.

Chrome 75.x: Package is invalid , Hello all, Thanks so much for your work on this amazing package! When trying to download crx files within Chrome, the download fails about linux hosting, extension has to specify update_url in its manifest.json file. user interaction, use policy file - it won't install CRX file that is somehow invalid. 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. Manifest File Format. Every app has a JSON-formatted manifest file, named manifest.json, that provides important information.

failed to load extension from chrome manifest file is missing or , Manifest file for is missing or invalid. If you want further help give me a link to the extension and I'll take a look at it. It installs without problems on my system and  In general, you should: Use required permissions when they are needed for your extension’s basic functionality. Use optional permissions when they are needed for optional features in your extension. Advantages of required permissions: Fewer prompts: An extension can prompt the user once to accept all permissions.

#6571 ("Manifest file is invalid." message shown when installing , Browse to ​https://adblockplus.org/; Click "Agree and Install for Chrome". Observed behaviour ¶. "Manifest file invalid" message is shown (see attached screenshot). consistently to start with, but just now it became intermittent and I can usually install the extension OK. Perhaps it was a caching issue, I'm not sure. When Chrome looks for native messaging hosts, first the 32-bit registry is queried, then the 64-bit registry. On OS X and Linux, the location of the native messaging host's manifest file varies by the browser (Google Chrome or Chromium).

  • And I found I can not install crx file I compiled from google's example? I s that means I should not use chrome at version 19.0?
  • Thanks for sharing... did the same :)
  • The same is happening in 2016 too :\
  • Can you file a bug, regardless? Chrome shouldn't choke on non-english characters: new.crbug.com If you post the ID here, I'll make sure it gets in front of the right people.
  • @MikeWest I posted the issue here. I never did this before so I don't know if my wrote in the right format . code.google.com/p/chromium/issues/detail?id=118869
  • Thank you! I've thrown it into the proper queue.
  • so, what is the correct encoding to use? ANSI or UTF-8?
  • Hi Brisssou. I've googled a bit, without finding an official answer. My answer: ANSI seems to be your best bet.
  • Thx phareim. In fact, in the case I was facing, submitting the extention the next day worked. ie: don't trust the store ; try to install your extention, while (fail) {sleep; retry} ... :/