Provides access to the standard interface that manages the editing and sending an email message

Downloads in past


0.10.12 years ago8 years agoMinified + gzip package size for cordova-plugin-email-composer in KB


Cordova Email Plugin
npm version Code Climate PayPayl donate button

The plugin provides access to the standard interface that manages the editing and sending an email message. You can use this view controller to display a standard email view inside your application and populate the fields of that view with initial values, such as the subject, email recipients, body text, and attachments. The user can edit the initial contents you specify and choose to send the email or cancel the operation.
Using this interface does not guarantee immediate delivery of the corresponding email message. The user may cancel the creation of the message, and if the user does choose to send the message, the message is only queued in the Mail application outbox. This allows you to generate emails even in situations where the user does not have network access, such as in airplane mode. This interface does not provide a way for you to verify whether emails were actually sent.

Supported Platforms

  • Android
  • Browser
  • iOS
  • OSX
  • Windows


The plugin can be installed via Cordova-CLICLI and is publicly available on NPMnpm.
Execute from the projects root folder:
$ cordova plugin add cordova-plugin-email-composer
Or install a specific version:
$ cordova plugin add cordova-plugin-email-composer@VERSION
Or install the latest master version:
$ cordova plugin add
Or install from local source:
$ cordova plugin add <path> --nofetch --nosave


The plugin creates the object and is accessible after the deviceready event has been fired.
document.addEventListener('deviceready', function () {
    // is now available
}, false);

All properties are optional. After opening the draft the user may have the possibilities to edit the draft from the UI. The callback comes without arguments.{
    from:       String, // sending email account (iOS only)
    to:          Array, // email addresses for TO field
    cc:          Array, // email addresses for CC field
    bcc:         Array, // email addresses for BCC field
    attachments: Array, // file paths or base64 data streams
    subject:    String, // subject of the email
    body:       String, // email body
    isHtml:    Boolean  // indicats if the body is HTML or plain text (primarily iOS)
}, callback, scope);

The following example shows how to create and show an email draft pre-filled with different kind of properties:{
    to:      '',
    cc:      '',
    bcc:     ['', ''],
    subject: 'Greetings',
    body:    'How are you? Nice greetings from Leipzig'

Of course its also possible to open a blank draft:;

Its possible to specify the email client. If the phone isn´t able to handle the specified scheme it will fallback to the system default:{ app: 'mailto', subject: 'Sent with mailto' });

On Android the app can be specified by either an alias or its package name. The alias gmail is available by default.
// Add app alias'gmail', '');

// Specify app by name or alias{ app: 'gmail', subject: 'Sent from Gmail' });

Issues with AndroidX

If you have issues with AndroidX, simply install the extra plugin
cordova plugin add cordova-plugin-androidx-adapter

For Ionic/Capacitor you can also try
npm install jetifier
npx jetify
npx cap sync android


Only the built-in email app for iOS does support HTML and CSS. Some Android clients support rich formatted text.
Use isHtml with caution! It's disabled by default.

Attach Base64 encoded content

The code below shows how to attach an base64 encoded image which will be added as a image with the name icon.png.{
    subject:     'Cordova Icon',
    attachments: ['base64:icon.png//iVBORw0KGgoAAAANSUhEUgAAADwAAAA8CAYAAAA6...']

Attach files from the device storage

The path to the files must be defined absolute from the root of the file system. On Android the user has to allow the app first to read from external storage!{
    attachments: 'file:///storage/sdcard/icon.png', //=> storage/sdcard/icon.png (Android)

Attach native app resources

Each app has a resource folder, e.g. the res folder for Android apps or the Resource folder for iOS apps. The following example shows how to attach the app icon from within the app's resource folder.{
    attachments: 'res://icon.png' //=> res/mipmap/icon (Android)

Attach assets from the www folder

The path to the files must be defined relative from the root of the mobile web app folder, which is located under the www folder.{
    attachments: [
        'file://img/logo.png', //=> assets/www/img/logo.png (Android)
        'file://css/index.css' //=> www/css/index.css (iOS)

Attach files from the internal app file system

The path must be defined relative from the directory holding application files.{
    attachments: [
        'app://databases/db.db3', //=> /data/data/<app.package>/databases/db.db3 (Android)
        'app://databases/db.db3', //=> /Applications/<>/databases/db.db3 (iOS, OSX)
        'app://databases/db.db3', //=> ms-appdata:///databases/db.db3 (Windows)

Device Configuration

The email service is only available on devices which have configured an email account. On Android the user has to allow the app first to access account informations.;

To check for a specific mail client, just pass its uri scheme on iOS, or the package name on Android as first parameter:'gmail', callbackFn);

For Android only, it's possible to get a list of all installed email clients: (apps) {{ app: apps[0] });    


Some functions require permissions on Android. The plugin itself does not add them to the manifest nor does it ask for by itself at runtime.
| Permission | Description | | ---------- | ----------- | | | Is needed to attach external files file:/// located outside of the app's own file system. | | | Without the permission the hasAccount() function wont be able to look for email accounts. |
To check if a permission has been granted:, callbackFn);

To request a permission:, callbackFn);

Note: The author of the app has to make sure that the permission is listed in the manifest.


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request


This software is released under the Apache 2.0 Licenseapache2license.
Made with :yum: from Leipzig
© 2013 appPlant GmbHappplant