Figma’s standards support plans

Figma says it plans to support as many standards as possible, while recognising that different standards can create different levels of access to data. That distinction matters because standards are not simply interchangeable ways to connect software: some allow an application to retrieve more information than others. Figma’s approach is to assess standards in light of what they expose, rather than treating support for a standard as an automatic commitment to make every kind of information available through it.

The company’s stated aim is broad support, but it also intends to account for the risks associated with data access. Supporting a standard does not necessarily mean offering unrestricted access to all data. Instead, Figma is considering how each standard works and what information it makes available, as it determines how to support it. This reflects a plan to accommodate a wide range of standards while taking their capabilities into account.

In other words, Figma is seeking to support as many standards as it can, with the scope of access considered separately. The plan frames standards support as a continuing effort to balance compatibility with the amount of data that a standard permits applications to reach.

Limits on data exposure

Figma’s plans to support standards should not be read as a commitment to open up all of its data. The company has said it does not plan to expose everything, and its approach is intended to focus on the information needed to support standards. That distinction matters: making data available for standards-related use is not the same as offering unrestricted access to every dataset or detail held by the company.

Figma has not said that all of its data will be available, nor does its standards support plan mean that every aspect of its products or operations will be made public. The scope of access remains limited rather than universal. In practice, the company’s position leaves room to support standards while retaining limits on what information is exposed.

This boundary helps clarify what the plan does—and does not—promise. Figma is signaling support for standards, not a wholesale release of its data. Any discussion of access should therefore distinguish the information needed to advance standards from data outside that purpose.

Balancing standards and data access

Figma’s approach pairs broad support for established standards with limits on what information those standards make available. The plan is to support formats and protocols such as MCP, OpenAPI, and the Agent-to-Agent protocol, while keeping access to Figma data controlled. Supporting a standard does not mean giving an AI agent unrestricted access to everything in a Figma file.

Instead, the company describes a more selective model: agents should be able to work with relevant design information without exposing the full underlying file. This distinction matters because standards can make it easier for tools to connect, but the scope of the data they can retrieve remains a separate question. Figma’s stated balance is to make integrations more widely compatible while limiting exposure to the information needed for a given task.

The plan therefore treats interoperability and data access as related but distinct concerns. Standards support can provide a common way for systems to communicate; it does not, by itself, determine which content an agent can see. Figma’s position is that broader compatibility can coexist with boundaries around the data shared with AI tools.

What the plan establishes

Figma’s position combines broad support for established standards with limits on how much data it will expose. The company says it will support formats including SVG, CSS, and Web Components, while also making its design files available through APIs and MCP servers. These measures are intended to help AI tools work with Figma designs and connect them to development workflows.

At the same time, Figma does not plan to make every part of a design file available. It says some data will remain inaccessible, including information that could expose proprietary details or sensitive customer data. The approach therefore retains some information from exposure rather than opening all design data to outside tools.

Together, these choices define a selective approach: Figma is expanding compatibility and access through standards and interfaces, but preserving boundaries around certain data. The plan establishes neither unrestricted access nor a rejection of AI workflows. Instead, it pairs support for widely used formats and tools with limits on what can be retrieved. That balance is central to Figma’s stated position on enabling AI-assisted work while protecting information within design files.