Plugins are coming to Figma | Figma Blog

Figma announced the beta of its plugin platform, inviting developers to build tools that extend and improve design workflows. The initiative follows the success of Figma’s HTTP API and aims to make plugins powerful while preserving platform stability, security, performance, and compatibility. Figma initially planned a limited beta, with broader access and community-created plugins to follow.

Opening the Figma Platform

• Figma had previously launched an HTTP-based API for exporting design data and connecting Figma with other tools.
• Customers used the API to:
  • Export icons through custom Slack commands.
  • Push design updates into development environments.
  • Maintain and distribute GitHub’s Octicons SVG library.
• Independent designers and developers had also begun creating spaces for sharing Figma-related functionality.

Designing a Stable Plugin System

Figma recognized that plugins can create compatibility, security, and performance challenges. Rather than exposing internal APIs—which may change frequently—it designed dedicated third-party APIs intended to remain stable as Figma evolves.

The company established several principles:

• Plugins should be intuitive for all designers.
• Anyone capable of building a website should be able to create a plugin.
• Developers should be able to use popular programming languages.
• Plugins should not harm Figma’s performance or user experience.
• Figma would fully support and maintain the APIs used by plugins.

What Plugins Could Do

During the beta, developers could create plugins to:

• Automate repetitive design tasks.
• Speed up design workflows.
• Import real-world data into Figma files.
• Share plugins with teammates.

Because Figma is web-based, the company expected plugins to be relatively easy to build and maintain for developers familiar with HTML and JavaScript.

Beta Access and Future Availability

• The beta was limited to a selected group of users.
• Applicants were prioritized based on the ideas they wanted to build.
• Figma intended to use the beta to stress-test and refine its plugin APIs.
• Broader access was planned for the future.
• Non-coders would eventually be able to use community-built plugins.

Developers with basic web-development skills and a plugin idea were encouraged to apply for the beta.