Plugin manifest

Describe your plugin, its entry points, and what it needs.

5 min readUpdated Sep 16, 2026

Every plugin ships a varial.design.extension-manifest.v1 manifest.

Required fields

  • id, name, and version
  • publisher with the key id you sign with
  • compatibility for the product, API, and document schema
  • entryPoints with a kind: worker, sandbox, or isolated-frame
  • capabilities, the exact list of what you need
  • package, the SHA-256 digest of every file

Capabilities

Ask for the least you need. Common ones:

  • design.document.read and design.document.write
  • design.selection.read
  • design.ui.command, design.ui.panel
  • design.export.write
  • design.network.declared-origins with networkOrigins

Changing the document

Plugins change documents through host commands such as object.set-opacity and object.translate. There is no raw property access.