Framer | Plugins 4.1 Adds Branching and Publishing APIs
Framer Plugins 4.1 expands what plugins can automate inside a website project by introducing new Branching and Publishing APIs. Released on August 4, 2026, the update lets plugin developers create and manage project branches, publish site changes, track deployments, and deploy published versions to custom domains, opening the door to workflows that can move from experimentation to production without leaving the plugin environment.
Framer plugins can now move from experimentation to deployment
The biggest change in Plugins 4.1 is that plugins can participate in stages of a Framer project that previously required more direct user interaction. The new Branching API lets a plugin inspect existing branches, create new ones, switch between them, monitor changes, and work with branch objects programmatically.
At the same time, the Publishing API extends automation to the delivery side of the workflow. Plugins can publish project changes, inspect unpublished page changes, monitor deployments and deployment issues, and deploy a published version to a custom domain. Together, these APIs make it possible to build tools that handle a larger part of a site's production process.
Branching gives plugins a safer space for automated changes
The Branching API includes methods for retrieving, creating, and monitoring project branches. A plugin can use createBranch() to create and switch to a new branch, while additional APIs can locate branches by ID, retrieve the active branch, and react when branch information changes.
Branch objects can also switch, merge, delete, rename, join, leave, and inspect changes. For designers and site teams, this creates interesting possibilities for plugins that experiment with larger layout, CMS, or site modifications without immediately applying those changes to the main working version of a project.
Publishing APIs extend plugins into site deployment
Publishing is the other major part of the release. The new publish() API lets a plugin publish project changes, while deploy() can push a published version to a custom domain. Plugins can also retrieve deployments, list previous deployments, subscribe to deployment updates, and inspect issues that may affect a deployment.
Framer also supports publishing and tracking deployments independently on project branches. That combination could support plugins designed around controlled publishing workflows, automated site maintenance, staged updates, or tools that prepare changes on a branch before deciding how and when they should reach a live site.
Plugins also gain more CMS, vector, and asset data
Plugins 4.1 includes several smaller API additions beyond branching and deployment. CMS collection items now expose createdAt and updatedAt timestamps, while fonts include a url property that points to the source file used for rendering.
Plugin developers can also work with additional vector node types, including Path, Shape Group, Shape Container, and Boolean Shape nodes. Framer's first-party plugins received updates as well, including support for alt-text and option fields in Google Sheets, expanded Notion relation fields, and workflow improvements for Notion syncing and Tidy Up.
Daisuki's Take: What This Means for Web Designers
The important change in Plugins 4.1 is that Framer plugins are becoming capable of managing more than content or canvas operations. Branching and publishing place them much closer to the complete website lifecycle, from preparing an experimental change to delivering a finished version.
For web designers, that could lead to plugins built around safer automated redesigns, repeatable publishing processes, CMS maintenance, quality checks, or other workflows that need to modify a site without treating every change as immediately production-ready.
We would still keep human review around any workflow that can merge branches or publish to a live domain. The APIs provide powerful building blocks for automation, but their real value will depend on plugins using that access in predictable ways and making it clear what is changing before a site reaches production.
Sources and Recommended Links
- Branching and Publishing APIs | Framer Official Site
- Framer Plugin API Changelog | Framer Official Documentation
- Publishing | Framer Official Documentation
