• Getting Started
• Overview
• What's New?
• Developer's Guide
  • Browser UI
    • Browser Actions
    • Context Menus
    • Desktop Notifications
    • Omnibox
    • Options Pages
    • Override Pages
    • Page Actions
  • Browser Interaction
    • Bookmarks
    • Cookies
    • Developer Tools
    • Events
    • History
    • Management
    • Tabs
    • Windows
  • Implementation
    • Accessibility
    • Event Pages
    • Content Security Policy
    • Content Scripts
    • Cross-Origin XHR
    • Internationalization
    • Message Passing
    • Optional Permissions
    • NPAPI Plugins
  • Finishing
    • Hosting
    • Other Deployment Options
• Tutorials
  • Manifest V2
  • Debugging
  • Google Analytics
  • OAuth
• Reference
  • Formats
    • Manifest Files
    • Match Patterns
  • Permission Warnings
  • chrome.* APIs
  • Other APIs
• More
  • Chrome Web Store
  • Hosted Apps
  • Themes

Hosting

This page tells you how to host .crx files on your own server. If you distribute your extension, app, or theme solely through the Chrome Web Store, you don't need this page. Instead, consult the store help and developer documentation.

By convention, extensions, installable web apps, and themes are served—whether by the Chrome Web Store or by a custom server—as .crx files. When you upload a ZIP file with the Chrome Developer Dashboard, the dashboard creates the .crx file for you.

If you aren't publishing using the dashboard, you need to create the .crx file yourself, as described in Packaging. You can also specify autoupdate information to ensure that your users will have the latest copy of the .crx file.

A server that hosts .crx files must use appropriate HTTP headers, so that users can install the file by clicking a link to it.

Google Chrome considers a file to be installable if either of the following is true:

• The file has the content type application/x-chrome-extension
• The file suffix is .crx and both of the following are true:
  • The file is not served with the HTTP header X-Content-Type-Options: nosniff
  • The file is served with one of the following content types:
    • empty string
    • "text/plain"
    • "application/octet-stream"
    • "unknown/unknown"
    • "application/unknown"
    • "*/*"

The most common reason for failing to recognize an installable file is that the server sends the header X-Content-Type-Options: no sniff. The second most common reason is that the server sends an unknown content type—one that isn't in the previous list. To fix an HTTP header issue, either change the configuration of the server or try hosting the .crx file at another server.