What Shipped on April 21

Framer’s CMS 3.0 release, announced on April 21, 2026, reworks how teams interact with structured content inside the Framer canvas. The headline feature is full inline editing: content editors can now click directly into a CMS table and edit values in place, without opening a separate item panel or leaving the collection view. Paired with that is multi-cell selection, which lets editors highlight a block of cells across rows and columns much like a spreadsheet, and apply bulk actions — updating a status field, clearing values, or duplicating entries across dozens of items in one pass instead of one at a time.

The update also reworks keyboard navigation inside collections, so editors can move between fields, confirm edits, and jump between rows without reaching for the mouse. Columns are now draggable and resizable directly in the table view, making it easier to prioritize the fields a team actually works with day to day. Perhaps the most requested change is a folder structure for collections: teams managing large CMS setups — blogs with dozens of authors, multi-market product catalogs, resource libraries — can now group collections into folders instead of scrolling through a flat, unsorted list.

Why This Release Matters More Than It Looks

On the surface, these are table-stakes productivity features — the kind of thing spreadsheet tools have offered for years. But in the context of a website CMS, they mark a real shift in who a site is built for. A collection that requires opening an item, editing a field, saving, and repeating for every row is a workflow designed around occasional updates by whoever built the site. A collection with inline editing and bulk actions is a workflow designed around a content team that touches the site every day.

That distinction has direct business value. Marketing teams that previously had to file a ticket, wait for a developer’s availability, or carefully avoid breaking a template just to update ten product prices or refresh a batch of blog dates can now do it themselves, in minutes, inside the same interface they use to preview the live page. For agencies and in-house teams alike, that translates into fewer hours billed for routine content maintenance and far less lag between “we need to change this” and it actually being live.

Part of a Broader Pattern, Not a One-Off

Framer’s own product direction has been pointing here for a while. Back on January 8, 2026, the company shipped On-Page Editing 2.0, which let editors reorder content directly on the live page and swap icon or component variants with a single click — a clear precursor to the deeper table-level control CMS 3.0 now delivers. Taken together, the two releases describe a consistent strategy: reduce the number of steps between “I want to change this” and “it’s changed,” and keep non-technical editors working in context rather than in an abstracted backend.

Framer isn’t alone in this shift. Elementor 4.0, released March 19, 2026, made its new Atomic Editor the default experience for new WordPress sites, a parallel bet on more direct, less template-locked editing. Webflow moved in a similar direction with Real-Time Collaboration, announced January 22, 2026, and rolled out to all paid and multi-user plans by February 25, 2026, enabling multiple editors to work on a site simultaneously rather than checking a project in and out. None of these platforms coordinated with each other, which is exactly what makes the pattern worth noting: independently, the major no-code and page-builder tools are converging on the same conclusion. Website content management is maturing away from developer-mediated workflows and toward direct, collaborative, spreadsheet-fast editing for the people who actually own the content.

An Agency Perspective on What Changes in Practice

We build and maintain client sites in Framer, and the gap CMS 3.0 closes is one we’ve felt directly. Historically, even a well-structured Framer CMS setup meant that large content updates — a seasonal catalog refresh, a batch of new case studies, a re-tagging of an entire blog archive — went through us, because editing dozens of items one-by-one in a side panel wasn’t something we wanted to hand off to a client’s marketing team. Inline editing and multi-cell bulk actions change that calculus. It’s now realistic to train a client’s own team to handle that kind of update independently, which frees up our time for the work that actually needs a builder’s judgment: new sections, new templates, new functionality.

The folder structure for collections matters more than it might sound like on a feature list, too. Sites with several CMS collections — team members, locations, case studies, FAQs, product lines — tend to get harder to navigate as they grow, and that friction is exactly what causes teams to stop maintaining content regularly. Being able to organize collections the way you’d organize files on a desktop removes a small but real barrier to teams keeping their own site current.

If your team is evaluating Framer as a platform, CMS 3.0 is a meaningful reason to take a second look, particularly if past hesitation was about handing content control to non-technical staff. And if the broader goal is treating your website as something you update continuously rather than rebuild every few years, tighter content workflows like this are what make that kind of ongoing agility actually practical, not just aspirational.