Capacitor Plugins

Plugins in Capacitor enable JavaScript to interface directly with Native APIs.

With Plugins, a web app can access the full power of the Native APIs, doing everything a traditional native app can. Plugins are especially great for wrapping common native operations that might use very different APIs across platforms, while exposing a consistent, cross-platform API to JavaScript.

Additionally, the Plugin capability in Capacitor makes it possible for teams with a mix of traditional native developers and web developers to work together on different parts of the app.

Capacitor auto generates JavaScript hooks on the client, so most plugins only need to build a native Swift/Obj-C plugin for iOS, and/or a Java one for Android. Of course, adding custom JavaScript for a plugin is possible, and is just like providing a JavaScript npm package.

Getting Started

Capacitor comes with a Plugin generator to start new plugins quickly. To use it, run

npx @capacitor/cli plugin:generate

This starts a wizard prompting you for information about your new plugin. For example:

max@Maxs-iMac:~ $ npx @capacitor/cli plugin:generate
✏️  Creating new Capacitor plugin
? Plugin NPM name (snake-case): my-plugin
? Plugin id (domain-style syntax. ex: com.example.plugin) com.ionicframework.myplugin
? Plugin class name (ex: AwesomePlugin) MyPlugin
? description:
? git repository:
? author:
? license: MIT
? package.json will be created, do you want to continue? (Y/n)
  • The Plugin NPM name is what will become the npm package, and should be a snake-case name of a package that is available on npm (not a strict requirement if your package will be on a private npm repo).
  • The Plugin ID is a domain-style identifier. Its primary use is the package name in Java.
  • Plugin Class Name is the initial name of the class used in Java and Swift. See the additional note about class names in the iOS Plugin section of this guide.
  • The description is a brief introduction about the plugin.
  • The git repository is the url to a git repository where the source code of the plugin will be hosted.

The rest of the fields are optional and will fill out your initial package.json

TypeScript Interface

Each plugin comes with some typescript files that simply export TypeScript interfaces. These interfaces can provide typing to TypeScript consumers of your plugin.

Starting with the TypeScript interface can be a good way to build out the API for your plugin. For example, here's the default interface for our Plugin:

declare global {
  interface PluginRegistry {
    Echo?: EchoPlugin;

export interface EchoPlugin {
  echo(options: { value: string }): Promise<{value: string}>;


Whenever you are ready to publish your plugin, just use:

npm publish

This will build the JS portion of your plugin and publish the rest of your plugin files to NPM.

Your package can now be installed using npm install your-plugin in any Capacitor app.

Next steps

Now it's up to you to make your plugin do something truly awesome!

Follow the iOS guide for information on using Swift (or Obj-C) to build an iOS plugin, the Android guide for building Android plugins with Java, the Web guide for implementing web and PWA functionality for your plugin, and the Custom JavaScript guide for information on how to build a custom JavaScript plugin (i.e. in addition to Capacitor's auto-JS plugin binding).