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.

Web APIs

In addition to the chrome.* APIs, extensions can use all the APIs that the browser provides to web pages and apps. If the browser doesn't support an API you want to use, you can bundle additional API libraries into your extension.

Here's a sampling of the APIs that extensions can use:

Standard JavaScript APIs

These are the same core JavaScript and Document Object Model (DOM) APIs that you can use in ordinary web apps.

XMLHttpRequest

Use XMLHttpRequest to request data from one or more servers. The permissions field of the manifest specifies which hosts the extension can send requests to.

HTML5 and other emerging APIs

Google Chrome supports HTML5 features, along with other emerging APIs. Here are some of the APIs you can use:

• audio (tutorial)
• application cache (tutorial)
• canvas (articles)
• fullscreen (article)
  • In Chrome Apps, fullscreen is entered without prompting the user or providing exit instructions. HTML5 fullscreen requires the app.window.fullscreen permission in the manifest. In normal webpages, the browser intercepts the ESC key to exit pointer lock ensuring a consistent escape method for users. That is also the behavior in Chrome Apps unless the app.window.fullscreen.overrideEsc permission is used to enable the app to call preventDefault on keydown and keyup events.
• geolocation (tutorial)
• local storage (tutorial)
• notifications (tutorial)
• pointer lock (tutorial)
  • In Chrome Apps, pointer lock is entered without requiring a user gesture, prompting the user, or providing exit instructions. Pointer lock requires the pointerlock permission in the manifest. Also, there is no default exit behavior. In normal webpages, the browser intercepts the ESC key to exit pointer lock. This behavior is not present in Chrome Apps.
• video (tutorial)
• web database (tutorial)

See html5rocks.com for HTML5 information, tutorials, an interactive playground, and links to other resources.

WebKit APIs

Because Google Chrome is built upon WebKit, your extensions can use WebKit APIs. Especially useful are the experimental CSS features such as filters, animations, and transformations. Here's an example of using WebKit styles to make the UI spin:

<style>
  div:hover {
    transform: rotate(360deg);
    transition: all 1s ease-out;
  }
</style>

V8 APIs, such as JSON

Because JSON is in V8, you don't need to include a JSON library to use JSON functions.

APIs in bundled libraries

If you want to use a library that the browser doesn't provide (for example, jQuery), you can bundle that library's JavaScript files with your extension. Bundled libraries work in extensions just as they do in other web pages.