Product Changes and Deprecations

This content was generated with the assistance of AI and should be verified against the official Webflow documentation before being relied on in production.

This sub-section’s Webflow bibliography lists the reference material consulted while preparing these pages.

This page was checked on 2026-10-28. Webflow is a hosted service: there is no version to install, no release number to quote and no upgrade to schedule. The Designer, the CMS, the hosting layer and the Data API all change in place, usually without any action by the site owner. What does have version numbers is the developer tooling, and this page pins the versions that were current on the check date: webflow-api 3.3.4 (JavaScript and TypeScript SDK), webflow 2.0.0 (Python SDK on PyPI), @webflow/webflow-cli 2.15.0, @webflow/designer-extension-typings 2.2.2 and @webflow/react 2.8.0.

The page has three jobs. It explains where to look to follow change, it lists the changes that mattered between 2022 and 2026 in date order, and it translates them into practical advice for anyone following an older tutorial, video or book. Plans are named by tier only and never by price. The running example is Fernbrook Gardens, the fictitious botanical garden whose site is built progressively in this sub-section: its team inherited a 2022 build and needs to know which parts of it are stale.

There is no version number

A self-hosted CMS such as WordPress ships numbered releases that a site owner chooses to install. Webflow does not. The platform is released continuously, so a sentence such as "in Webflow 3" has no meaning, and the only reliable way to date a statement about the product is the day it was checked. Every page of this sub-section therefore opens with a check date.

Three consequences follow from that model:

  • Changes arrive unannounced to the individual site. A panel moves, a setting is renamed or a default changes, and the next time the Designer loads it is already different. Screenshots in any article are a snapshot of one day.

  • Some changes are migrations with a date. When Webflow retires a feature it publishes a deprecation schedule, and the work of moving off the old feature is the site owner’s. The legacy Editor, Logic, User Accounts and Data API v1 all followed this pattern.

  • Developer artefacts do have versions. The SDKs, the command line tool, the Designer typings and the React package are published to package registries with semantic version numbers, and they pin cleanly in a lockfile.

Where to follow change

Four official sources cover different audiences. A team that owns a Webflow site should subscribe to at least the first two.

Source What it covers Best for

Product updates (webflow.com/updates)

Dated entries for Designer, CMS, ecommerce, localization, interactions, AI and plan changes.

Designers, content editors and site owners.

Developer changelog (developers.webflow.com/home/changelog)

Data API, Designer API, webhooks, SDKs, the command line tool, DevLink, code components, Webflow Cloud and the MCP server.

Developers, who should read the entries for every product area their integration touches.

Help Center (help.webflow.com)

Articles that explain a change in depth, including plan-change and deprecation articles with their rollout dates.

Anyone planning a migration. Note that many articles still use older names, for example CMS and Business plan names that were merged in May 2026 (see below).

Status page (status.webflow.com)

Live and historical incidents for the Designer, hosting, the CMS and the APIs.

Operations: it separates a Webflow outage from a bug in the site.

Source: Webflow: Product updates

A small habit keeps developer work from drifting: record the check date next to every integration, and re-read the changelog entries between that date and today before touching it. The package.json of the Fernbrook Gardens tooling repository pins the exact versions that were verified on 2026-10-28, with no range operators, so an upgrade is always a deliberate commit.

{
  "name": "fernbrook-gardens-tooling",
  "private": true,
  "engines": { "node": ">=22.13" },
  "dependencies": {
    "webflow-api": "3.3.4"
  },
  "devDependencies": {
    "@webflow/webflow-cli": "2.15.0",
    "@webflow/designer-extension-typings": "2.2.2"
  }
}

Source: Webflow developer changelog

The Python equivalent pins the webflow package in requirements.txt:

webflow==2.0.0

Source: Webflow developer changelog

The command line tool needs Node.js 22.13 or later, which the engines field above records. Run any check of these tools against a Developer workspace site, the free sandbox with no production publishing, so that nothing touches a live site.

Timeline, 2022 to 2026

The diagram shows the changes that most often make an older tutorial wrong. The sections after it give the detail and the practical meaning of each one.

timeline title Webflow changes that outdate tutorials, 2022 to 2026 section 2022-2023 Nov 2022 : Symbols renamed Components 2023-10-05 : Designer redesign section 2024 2024-03-25 : Backups restored before this date reset CMS IDs 2024-07 : Fields per Collection raised from 30 to 60 2024-07-31 : AVIF and WebP conversion tool 2024-08-01 : Data API v1 apps de-listed Oct 2024 : Webflow acquires GSAP Dec 2024 : Seats replace per-plan user caps section 2025 Jan 2025 : Variable modes 2025-03-31 : Data API v1 unsupported 2025-04-30 : GSAP free for everyone 2025-06-27 : Logic sunset 2025-07 : Interactions with GSAP launch 2025-07-07 : isDraft true no longer unpublishes 2025-11-06 : Webflow Cloud storage GA 2025-11-24 : MCP SSE endpoint retired section 2026 2026-01-29 : User Accounts sunset 2026-02-02 : Client seats arrive 2026-05-13 : May 2026 plans for new purchases 2026-06-01 : Standalone Webflow Cloud apps 2026-06-29 : AI credit limits enforced 2026-08-04 : Legacy Editor unavailable 2026-09-21 : MCP server 2.1 2026-10-05 : Legacy Editor fully deprecated 2026-10-21 : Agent Presence GA

Source: Webflow: Product updates

2022 and 2023: Components and the new Designer

Symbols became Components (November 2022). Reusable page parts were first called Symbols. They were renamed Components and have since gained props (text, rich text, image, link, visibility, variant and slot), slots, style variants and the Component Canvas. A tutorial that says "create a Symbol" describes the same idea with a much smaller feature set: it knows nothing about props or variants, so it pushes you toward duplicated classes that a modern component would absorb.

The Designer redesign (2023-10-05). The Designer’s layout, panel names and vocabulary changed. Older material talks about "projects" and a "Project Settings" panel where the product now says "sites" and "Site settings". Any screenshot from before the redesign shows panels in places they no longer occupy.

2024: limits, images and GSAP

  • Backups before 2024-03-25. Restoring a backup made before this date resets CMS Collection and item IDs, which breaks any API integration that stored those IDs. The rule matters when you restore very old restore points.

  • Fields per Collection (July 2024). The limit went from 30 to 60 fields. A book or video that designs around 30 fields is describing a limit that no longer binds. The Enterprise next-gen CMS later raised it to 100.

  • Image conversion (2024-07-31). The Assets panel can convert images to AVIF or WebP. The conversion is manual and replaces the original irreversibly, so keep the originals elsewhere. Older performance advice that tells you to convert images outside Webflow before upload is incomplete rather than wrong.

  • Data API v1 apps de-listed (2024-08-01). Marketplace apps that still used the v1 API stopped being listed, ahead of the 2025 end of v1.

  • Webflow acquires GSAP (October 2024). The animation library behind most professional web motion became part of Webflow, which set up the changes in the Interactions section below.

  • Seats (December 2024). Per-plan user caps were replaced by seats: full, limited, free and client seats, with Guests for agency work in a client’s workspace. The 2021-era model of "collaborators on a plan" no longer exists.

2025: GSAP, API v2 and sunsets

  • Variable modes (January 2025). Variables gained modes, so one variable can hold different values for light and dark or per breakpoint, and function variables followed (calc, clamp, min, max and color-mix). Tutorials that keep a swatch list of colors predate this and should be rebuilt on variables.

  • Data API v1 is unsupported (2025-03-31). Calls to the v1 endpoints are no longer supported. Move to v2, which uses the https://api.webflow.com/v2 base URL and token scopes instead of the v1 version header. The Users and Access Groups APIs were removed later, with User Accounts.

  • GSAP is free (2025-04-30). Webflow made GSAP free for all uses, including the plugins that were previously paid. The licence still restricts use inside no-code animation tools that compete with Webflow.

  • Logic is sunset (2025-06-27). Logic flows were disabled and forms reverted to standard forms. A tutorial that builds a Logic automation cannot be reproduced. Zapier and Make are the usual neutral replacements, along with the Data API and webhooks for code-based flows.

  • Interactions with GSAP (July 2025). The new interactions engine uses the trigger, target and action model on a GSAP timeline and is the default for new sites. Classic Interactions remain for navbar, dropdown, tab and slider events, for pages on branches and for non-primary locales.

  • isDraft behaviour (2025-07-07). Setting isDraft: true on a live CMS item through the API no longer unpublishes it. Use the unpublish endpoints. Older example code that relied on isDraft to take an item offline now leaves it live.

  • Webflow Cloud storage is generally available (2025-11-06). SQLite, key-value and object storage became GA for apps on Webflow Cloud.

  • MCP /sse endpoint retired (2025-11-24). The remote MCP server is reached at https://mcp.webflow.com/mcp over streamable HTTP. A client configuration that still points at the /sse URL fails.

2026: accounts, plans and the Editor

  • User Accounts and Memberships are sunset (2026-01-29). The Users and Access Groups APIs and the user_account_* webhooks were removed with them. A site that needs logins now uses a third-party membership tool or its own authentication, chosen on its own merits.

  • Client seats (2026-02-02). Client seats, specific to a site and available only in Freelancer and Agency workspaces, replaced the old model of giving clients Editor access.

  • May 2026 plans. The plans for new purchases changed on 2026-05-13: CMS and Business were merged into Premium, Basic stayed static-only, a new annual Team tier arrived, and CMS item add-ons were removed. Existing sites migrate from 2026-06-29, and sites in Freelancer or Agency workspaces and on pricing from 2022 or earlier migrate from 2026-11-16. AI credits are part of every Workspace plan and their limits have been enforced since 2026-06-29. The tiers are explained in Plans, Workspaces, Seats and Roles.

  • Standalone Webflow Cloud apps (2026-06-01). Apps can run on their own instead of being mounted under a site path.

  • The legacy Editor is retired. Its path was staged: automatic migration began on 2026-05-04, the Editor became unavailable on 2026-08-04 and it was fully deprecated on 2026-10-05, when the ?edit URL stopped working. Content is now edited on the canvas by users with a seat. Every tutorial step that tells the reader to open /?edit is obsolete.

  • Mouse Move trigger (2026-07-20). Interactions with GSAP gained a Mouse Move trigger.

  • MCP server 2.1 (2026-09-21) and Agent Presence (generally available 2026-10-21), which shows AI agents working on the canvas next to people.

  • Webflow Conf 2026 (1-3 September). The announcements included Source by Webflow (a research preview), Releases and a breakpoint canvas.

Source: Webflow developer changelog

Command line renames and removals

Developer tooling changes are the ones most likely to break a script. Two renames affect DevLink and code components:

  • In CLI 2.0, library share was renamed devlink import. Scripts and READMEs that mention library share are older than that release.

  • In CLI 2.9.0, devlink sync was removed. Use devlink export.

A short audit over a repository catches both. It is a review aid and not a fix: it lists the lines to read.

#!/usr/bin/env bash
set -euo pipefail

# Lists scripts, docs and workflows that still mention removed or renamed commands.
grep -rnE 'devlink sync|library share|/sse|api\.webflow\.com/(sites|collections)' \
  --include='*.json' --include='*.md' --include='*.sh' --include='*.yml' \
  --exclude-dir=node_modules . || echo "No stale Webflow references found"

Source: Webflow developer changelog

What each change means for older tutorials

The table maps a stale phrase to what to do. Each row is a decision the Fernbrook Gardens team made while reading its 2022 build notes.

If the tutorial says Today See

Create a Symbol

Create a Component, then use props, slots and style variants.

Components, Props, Slots and Variants

Add a color swatch

Create a color variable, optionally with light and dark modes.

Variables and Modes

Build an interaction in the Interactions panel (IX2)

Use Interactions with GSAP, and Classic Interactions only for navbar, dropdown, tab and slider events.

Interactions with GSAP

Open /?edit to edit content

Edit on the canvas with a seat. The Editor is gone.

Content Editing on the Canvas

Use the CMS plan or Business plan

Premium, or Team for the all-in-one tier. The Help Center still uses the old names in many articles.

Plans, Workspaces, Seats and Roles

A Collection has at most 30 fields

60 fields, and 100 on the Enterprise next-gen CMS.

Collections and Field Types

Call api.webflow.com/collections

Use Data API v2 at https://api.webflow.com/v2.

Developer Platform Overview

Build a Logic flow or a Memberships site

Neither exists. Use an integration platform, a third-party membership tool or your own authentication.

Where Older Books and Tutorials Are Outdated

A sound rule is to treat any tutorial dated before October 2023 as a description of concepts rather than of the interface, and any tutorial before 2025 as incomplete for variables, interactions and the API. The detailed corrections of the book that this sub-section cross-checks are collected in that last page.

Practical guidance for a team

  • Write the check date into every runbook. A runbook with no date cannot be judged stale.

  • Read the product updates and developer changelog monthly. Set a calendar reminder rather than relying on memory.

  • Test integrations on a Developer workspace site first. It cannot publish to production, so a regression there costs nothing.

  • Treat a deprecation date as a deadline for the migration, not for noticing it. The Editor, Logic, User Accounts and Data API v1 each gave a schedule and each schedule was shorter than the migration looked at first.

  • Keep a list of the unofficial APIs a site relies on. A forum-documented call such as re-initialising interactions can disappear without a changelog entry, because it was never documented by Webflow.

References