For a complete list of developer features in Chrome on Android,
refer to [chromestatus.com](http://chromestatus.com/). Download [Chrome on the Play Store](https://play.google.com/store/apps/details?id=com.android.chrome).

## A first-class browsing experience

When the user signs into Chrome on one device, the tabs and browsing history of
that session are available to the user when they sign into Chrome on another
device. The entire page content is synchronized between Chrome instances, not
just the URL, so the user doesn't have to resubmit credentials to see a boarding
pass or an article on a site that requires a login.

The address bar uses prefetching to fill in URLs and performs search queries
with suggestions based on browsing history and local bookmarks. This feature
only runs when the user is connected to WiFi.

## Performance

Chrome for Android brings to small devices the same multi-process architecture,
GPU-accelerated rendering, and the V8 JavaScript engine, optimized for mobile
architectures. Chrome for Android delivers fast graphics performance thanks to:

- GPU acceleration for the [`canvas` element](https://web.dev/articles/canvas-performance/)
- Fluid CSS transforms and transitions
- Support for `requestAnimationFrame` for more efficient animations

## Use DevTools to find and fix problems

You can debug mobile web sites with the full suite of [Chrome DevTools](https://developer.chrome.com/docs/devtools)
running on a desktop browser, connected to your phone with USB. Learn more
about [remote debugging](https://developer.chrome.com/docs/devtools/docs/remote-debugging).

In addition to DevTools, Chrome for Android provides more advanced
developer features for very specific use cases:

- GPU diagnostics: `chrome://gpu`
- AppCache debugging: `chrome://appcache-internals`
- Net stack debugging: `chrome://net-internals`

You can also use the [Resource Timing](https://developer.mozilla.org/docs/Web/API/Performance_API/Resource_timing) and [User Timing](https://web.dev/articles/usertiming) APIs to analyze
application performance.

## Work offline

Working online is convenient but connections sometimes fail when the signal is
blocked or nonexistent. To make this easier, Chrome for Android supports the
following storage APIs:

- [AppCache](https://developer.mozilla.org/docs/Web/HTML/Using_the_application_cache) or application cache.
- [FileSystem](https://developer.mozilla.org/docs/Web/API/FileSystem) and [File APIs](https://developer.mozilla.org/docs/Web/API/File) (File, FileList, FileReader, Blob)
- [localStorage](https://web.dev/articles/storage-for-the-web) for storing simple key-value pairs
- [IndexedDB](https://developer.mozilla.org/docs/IndexedDB), a standard indexed datastore

Learn more about [offline storage](https://web.dev/articles/storage-for-the-web).

## Standards and APIs

Chrome for Android supports modern web standards. For an updated view of
features per Chrome release, refer to [chromestatus.com](https://chromestatus.com).

### Device APIs

In a mobile world, it's important to be able to access your user's contextual surroundings, from
location and device orientation to camera access. Chrome for Android provides:

- [Geolocation API](https://developer.mozilla.org/docs/Web/API/Geolocation_API) for accessing location
- [HTML media capture](https://www.w3.org/TR/html-media-capture/) for camera access
- [Device orientation](https://web.dev/articles/device-orientation) for portrait vs. landscape orientation
- [Android Intent URIs](http://developer.android.com/guide/appendix/g-app-intents.html) such as `tel:` and `geo:` that give access to the dialer and Google maps

### Standard APIs

Chrome for Android supports many HTML5 APIs that are ready to use in your apps.

- [requestAnimationFrame](https://web.dev/articles/animations-guide) to achieve optimum animation performance
- Interactive communication between server and client with [WebSockets](https://developer.mozilla.org/docs/WebSockets).
- Multi-threading with [Web Workers](https://web.dev/articles/workers-basics) (dedicated only)
- [requestFullscreen](https://web.dev/articles/fullscreen) method (presently via the prefixed call, `webkitRequestFullScreen()`) to allow you to hide the browser UI (chrome)
- [WebRTC](https://developer.mozilla.org/docs/Web/API/WebRTC_API) for real-time communication without a plug-in
- [WebAudio](https://developer.mozilla.org/docs/Web/API/Web_Audio_API) to process and synthesize audio signals
- Experimental support (via `chrome://flags` in the Chrome address bar) for the following APIs:
  - [WebGL](https://developer.mozilla.org/docs/Web/API/WebGL_API) for creating three-dimensional graphics for web browsers

### Security

Chrome for Android supports [Content Security Policy](https://developer.mozilla.org/docs/Web/HTTP/CSP) to significantly
reduce the risk and impact of XSS attacks, using the standard (non-prefixed)
HTTP header, `Content-Security-Policy`.

## Known issues

For current issues, see the list at [crbug.com](https://crbug.com) and star the ones you need
the most. If you find a new issue, log it using [new.crbug.com](https://new.crbug.com).