Plugin Bundles

A Plugin is a collection of one or more scripts. Each script defines one or more commands which extend Sketch in some way.

On disk, a Plugin is a folder with the .sketchplugin file extension, containing files and sub-folders.

Strictly speaking, a Plugin is actually an OS X package, arranged as an OS X bundle.

A package is any directory that the Finder presents to the user as if it were a single file (you can use the Reveal Package Contents command in the Finder to look inside).

A bundle is a directory with a standardized hierarchical structure that holds executable code and the resources used by that code.

Sketch Plugins don’t allow native compiled code, but we do use the standard bundle layout (resources, for example, live in the Resources/ folder in the bundle), with the plugin-specific files located in a Sketch/ directory.

Plugin Bundle Folder Structure

Bundles contain a manifest.json file, one or more .cocoascript files (containing scripts written in CocoaScript or JavaScript) which implement commands shown in the Plugins menu, and any number of shared library scripts and resource files.

Here’s an example:

      Select Circles.cocoascript
      Select Rectangles.cocoascript

The most critical file is the manifest.json file, which tells Sketch where everything else lives.


The manifest is a JSON file containing metadata about the Plugin, its commands and resources.

It describes such things as the full name, a description, and the name of the author. It lists the names of any commands defined by the Plugin, and tells Sketch what to call the corresponding menu items and which menus to put them in.

Here’s an example:

  "name": "Select Shapes",
  "description": "Plugins to select and deselect shapes",
  "author": "Joe Bloggs",
  "homepage": "",
  "version": "1.0",
  "identifier": "com.example.sketch.shape-plugins",
  "appcast": "",
  "compatibleVersion": "3",
  "bundleVersion": 1,
  "commands": [
      "name": "All",
      "identifier": "all",
      "shortcut": "ctrl shift a",
      "script": "shared.js",
      "handler": "selectAll"
      "name": "Circles",
      "identifier": "circles",
      "script": "Select Circles.cocoascript"
      "name": "Rectangles",
      "identifier": "rectangles",
      "script": "Select Rectangles.cocoascript"
  "menu": {
    "items": [

This Plugin is called “Select Shapes”. It defines three commands “All”, “Circles”, and “Rectangles”, which will be placed in a “Select Shapes” menu.

This plugin can be updated by Sketch. Sketch will download the file at the location specified by appcast and use it to determine if an update is available or not.

Unpacking this file a bit further, here are the supported keys and what they are for:


The name for this Plugin. This is used by default as the name of the sub-menu in which the Plugin’s menu commands will appear.


A string describing what this Plugin’s command (or commands) do.


A string specifying the author of the Plugin.


An optional string specifying how to contact the Plugin author by email.


An optional string specifying an online resource for the user to find out more information or provide feedback for the Plugin.


A string specifying the semantic version for the Plugin, for example 1.0, 1.1.1.


A string specifying a unique identifier for the Plugin.

Reverse-domain syntax is strongly encouraged, for example com.example.sketch.shape-plugins.

Sketch uses this string internally to track the Plugin, store settings for it, etc.


A string specifying a URL to the appcast file. The appcast file contains information about updates to the plugin, like the versions of available updates and where the updates can be downloaded from. Sketch downloads this file to determine if there are plugin updates available.

Compatible Version

A string specifying the version of Sketch in which the author has tested the Plugin, for example 3, 3.1, 3.2.2.

At the moment (Sketch 3.4) this is an optional key, but we could use it as a filtering option in the Plugins page at some point.

Internally it uses the BCCompareVersions function, which splits the string by ., then compares the integer value of each component.

Bundle Version

The version for the layout of the bundle an metadata. If excluded it is assumed the value is 1.

This is just a future-proofing mechanism for us. If, in the future, we see a plugin with a bundleVersion > 1, we’d know that we could treat the other values in the metadata differently.

For now it’s fine to omit it.


This is an advanced setting, and it defaults to false. When set to true, it will disable CocoaScript’s own preprocessor. This way, you’ll be able to use build systems like browserify or ES6 module syntax to develop your plugins.

Setting this option to true does the following:

  • disables @import support, you’ll have to take care of your imports manually
  • disables bracket syntax (i.e: [obj msg:]), you’ll have to use dot-syntax only


An array of commands that the Plugin defines.

Each item within the array is a dictionary specifying the name, shortcut and other properties of the command. See Plugin Commands for more details.

A dictionary describing the menu layout for the commands in this Plugin.

See Plugins Menu for more details on the contents of this dictionary, and how the menu for each Plugin is built.

Plugin Commands

A Plugin defines one or more commands for the user to execute.

The commands array in the manifest describes these. Each entry in the array is a dictionary, with the following properties:


The display name for the command. This value is used in the Plugins menu.


A string specifying a unique identifier for the command within the Plugin bundle. This is used to consistently map commands to actions, irrespective of command name changes.


An optional string specifying a default keyboard shortcut for this command, for example: ctrl t, cmd t, ctrl shift t.


The relative path within the Plugin bundle’s Sketch folder for the script that implements this command.


The name of the function with the script to call this command. The function must take a single context parameter, which is a dictionary with keys for things like the current document and selection. If unspecified the command is expected to be onRun:

var onRun = function (context) {
  var doc = context.document;
  var selection = context.selection;

Plugins Menu

When it loads a Plugin, Sketch creates a menu for it, and populates that menu using information from the “menu” dictionary in the manifest file.

This dictionary can contain the following keys.


A string specifying the title to use for the submenu.


This is an array which lists the items to include in the menu.

It can contain items of two types:

  • a string giving the identifier of a command
  • a dictionary describing a sub-menu (containing “title” and “items”)


By default, the menu items listed in this dictionary will appear in a menu with the name specified by the title key.

If the isRoot key is specified, with a value of true, the items will instead be inserted at the root level of the Plugins menu, rather than in a subfolder. In this case, the title key will be ignored.

This key is ignored in sub-menus.

Here’s an example. It defines three commands in a menu called “My Plugin Menu”. The first two items of the menu correspond to two of the Plugin’s commands, but the third item is a submenu called “My Plugin Submenu”. This submenu has a single item in it (the third of the Plugin’s commands):

  "menu": {
    "title": "My Plugin Menu",
    "items": [
        "title": "My Plugin Submenu",
        "items": [


Plugin commands are implemented by handlers.

These are simply JavaScript functions which live in a .cocoascript file in the Plugin bundle, and which take a single parameter containing some context.

Here’s a simple example:

var doMyCommand = function(context) {

In the manifest file, you specify a dictionary describing each command that the Plugin defines.

In this dictionary, script and handler keys tell Sketch which script file to look in, and which handler to run.

You are free to put each command implementation into its own script file, or to put them all in a single file.

You must specify the script key for each command.

If you put each command in its own script file, you can omit the handler key. In this case, Sketch will default to calling the onRun handler.

If you put multiple command handlers into the same script file, you need to use the handler key for each one, since they can’t all use the onRun handler!.

See something wrong or incomplete? Improve this page.