Many aspects of an app's behavior can be controlled with a global
config.xml, that belongs in the top-level web
asset directory along with the app's home page. This
platform-agnostic XML file is arranged based on the W3C's Packaged
Web Apps (Widgets) specification, and
extended to specify core Cordova API features, plugins, and
For projects created with the Cordova CLI (described in The
Command-Line Interface), this file can be found in the top-level
When using the CLI to build a project, versions of this file are
passively copied along with other web-asset source files into various
platforms/*/www subdirectories, for example:
An exception is Android, whose path specifies an additional
If you use the CLI to create a project, but then shift your workflow to an SDK, you need to use an alternate set of source files for Android and iOS:
This section details global and cross-platform configuration options. See the following sections for platform-specific options:
In addition to the various configuration options detailed below, you can also configure an application's core set of images for each target platform. See Icons and Splash Screens for more information.
This example shows the default
config.xml generated by the CLI's
create command, described in The Command-Line Interface:
<widget id="com.example.hello" version="0.0.1"> <name>HelloWorld</name> <description> A sample Apache Cordova application that responds to the deviceready event. </description> <author email="firstname.lastname@example.org" href="http://phonegap.com"> Apache Cordova Team </author> <content src="index.html" /> <access origin="*" /> <preference name="Fullscreen" value="true" /> <preference name="WebViewBounce" value="true" /> </widget>
The following configuration elements appear in the top-level
config.xml file, and are supported across all supported Cordova
idattribute provides the app's reverse-domain identifier, and the
versionits full version number expressed in major/minor/patch notation.
<name>element specifies the app's formal name, as it appears on the device's home screen and within app-store interfaces.
<author>elements specify metadata and contact information that may appear within app-store listings.
<content>element defines the app's starting page in the top-level web assets directory. The default value is
index.html, which customarily appears in a project's top-level
<access>elements define the set of external domains the app is allowed to communicate with. The default value shown above allows it to access any server. See the Domain Whitelist Guide for details.
<preference>tag sets various options as pairs of
valueattributes. Each preference's
nameis case-insensitive. Many preferences are unique to specific platforms, as listed at the top of this page. The following sections detail preferences that apply to more than one platform.
The following global preferences apply to all platforms:
Fullscreenallows you to hide the status bar at the top of the screen. The default value is
<preference name="Fullscreen" value="true" />
Orientationallows you to lock orientation and prevent the interface from rotating in response to changes in orientation. Possible values are
<preference name="Orientation" value="landscape" />
defaultvalue means both landscape and portrait orientations are enabled. If you want to use each platform's default settings (usually portrait-only), leave this tag out of the
The following preferences apply to more than one platform, but not to all of them:
DisallowOverscroll(boolean, defaults to
false): set to
trueif you don't want the interface to display any feedback when users scroll past the beginning or end of content.
<preference name="DisallowOverscroll" value="true"/>
Applies to Android and iOS. On iOS, overscroll gestures cause content to bounce back to its original position. On Android, they produce a more subtle glowing effect along the top or bottom edge of the content.
BackgroundColor: Set the app's background color. Supports a four-byte hex value, with the first byte representing the alpha channel, and standard RGB values for the following three bytes. This example specifies blue:
<preference name="BackgroundColor" value="0xff0000ff"/>
Applies to Android and BlackBerry. Overrides CSS otherwise available across all platforms, for example:
HideKeyboardFormAccessoryBar(boolean, defaults to
false): set to
trueto hide the additional toolbar that appears above the keyboard, helping users navigate from one form input to another.
<preference name="HideKeyboardFormAccessoryBar" value="true"/>
Applies to iOS and BlackBerry.
If you use the CLI to build applications, you use the
to enable device APIs. This does not modify the top-level
file, so the
<feature> element does not apply to your workflow. If
you work directly in an SDK and using the platform-specific
config.xml file as source, you use the
<feature> tag to enable
device-level APIs and external plugins. They typically appear in this
<feature name="Plugin" value="PluginID" />
They often appear with custom values in platform-specific
files. For example, here is how to specify the Device API for Android
<feature name="Device"> <param name="android-package" value="org.apache.cordova.device.Device" /> </feature>
Here is how the element appears for iOS projects:
<feature name="Device"> <param name="ios-package" value="CDVDevice" /> </feature>