Introducing: Figma’s Platform | Figma Blog (opens in new tab)
Figma launched its Platform in 2018 to connect design files with external tools, scripts, and web applications. Its central innovation was a web API that made design data accessible across operating systems and workflows, enabling new forms of collaboration. Figma argued that this open, web-based foundation could replace outdated export-based processes with live, integrated design systems. ## A Web API for Design - Figma’s API was presented as a first for professional design tools, which had traditionally been siloed desktop applications. - Because Figma operates online, external software can access the current state of a design without depending on: - A particular operating system - Local file paths - Specific software versions - Companies could build custom tools around their own organizational needs. - Examples included: - Uber creating live displays and feeds of work in progress - GitHub automating parts of its icon-production workflow ## Core API Capabilities The initial Web API provided three main functions: - Reading design files in an open JSON format - Reading and writing comments - Rendering files or file sections as PNG, JPG, SVG, and other standard formats Using a file’s URL-based key, developers could retrieve a live representation of its design tree, including: - Shapes and text - Components - Prototype links and transitions - Constraints - Other structural information defining the design The API was designed for familiar web-development tools and programming frameworks rather than proprietary plugin languages, making integrations easier to create and maintain. ## Open-Source Demos and Integrations Figma announced demo projects illustrating possible uses of the platform, including: - A spell checker for Figma designs - A generative art tool - A way to place designs on the Ethereum blockchain It also highlighted integrations with Avocode, Haiku, Zeplin, and Pagedraw. ## Planned Platform Features Figma outlined several future additions: - **Webhooks:** Notifications for file or team events, including design updates. - **Write API:** Broader programmatic editing of Figma files beyond the existing Comment API. - **Extensions:** An in-app extension system, though Figma intended to prioritize robustness, predictability, and quality rather than release an unstable model quickly. ## Collaboration Problems in Traditional Design Workflows As design becomes relevant to engineers, researchers, marketers, executives, and other departments, desktop design tools create organizational friction: - Files must be exported and uploaded before sharing. - Shared files become outdated when the original changes. - Leaders lack an easy way to view and comment on live work. - Engineers spend time locating the correct assets. - Teams often recreate solutions that already exist elsewhere in the organization. Figma positioned its API as a way for enterprises to share, search, and monitor real-time designs across departments. ## Uber’s Internal Use Case Uber’s distributed design team worked across four cities and multiple products, including Uber Eats and Uber Freight. To improve visibility, the company planned to use Figma’s API to: - Broadcast in-progress designs on office TVs - Create a Dribbble-like internal repository - Make work easier to browse across the organization The example demonstrated how Figma’s API could turn design files into live organizational infrastructure rather than isolated project artifacts. Figma’s recommendation was to treat the Platform as a foundation for custom workflows and integrations. By exposing live design data through standard web technologies, it enabled companies to build collaboration tools suited to their own processes while reducing manual exports and duplicated work.