Content Editing on the Canvas

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 describes content editing in Webflow as it was on 2026-10-28, the date on which its facts were checked against the official Help Center, the Webflow blog and the Webflow updates page. Webflow is a software-as-a-service product, so everything below is dated rather than versioned. Plans are named by tier only; this page never quotes prices, and the Plans, Workspaces, Seats and Roles page explains which seat each tier provides.

The running example is Fernbrook Gardens, a fictitious botanical garden. Its designer builds the pages and the collections once; afterwards a part-time content editor keeps the Garden Journal and the Events calendar current, and a marketer adjusts landing pages and search-engine settings. Neither opens the Designer’s full toolset. This page follows their work, and then explains what happened to the separate tool that people used for the same job until 2026.

The idea: edit where the content is displayed

In a traditional CMS, an editor works in a form: a field for the title, a field for the body, a button to save. The person never sees the page that those fields produce. Webflow’s content editing takes the opposite approach. The editor opens the real page on the Webflow canvas, points at the heading or the photograph that needs to change, and changes it in place. The design cannot be damaged on the way, because the editing experience exposes only content and hides every design control.

Webflow’s own description of the experience is that the canvas-based content editor keeps site designs untouched while one or more team members edit static and dynamic content at the same time. Two ideas make that possible.

  • Static content and dynamic content. Text, links and images that a designer typed or placed directly on a page are static. Content that comes from CMS items and appears through Collection lists and template pages is dynamic. Both can be edited on the canvas; Webflow documents them as two separate workflows because the way you reach the content differs. See Collection Lists and Collection Template Pages for how the designer binds them.

  • Roles instead of a separate product. Who may edit is decided by the role assigned to a seat, not by a different application. A person with the Content editor role sees an editing experience; a person with the Marketer role sees a page-building experience that includes editing; a person with the Reviewer role may only look and comment.

Webflow’s names for the two experiences are Edit mode and Build mode. The announcement of the Editor’s retirement says that the Content editor role is the one formerly known as Edit mode and the Marketer role is the one formerly known as Build mode.

Who can edit: seats and roles

Editing rights come from a seat in a Workspace and a role on that seat. The seat decides how the person is billed and which sites they can reach; the role decides what they can do on those sites.

Role What the official documentation says it can do Typical Fernbrook person

Content editor

Update text, images and CMS content on the canvas (formerly Edit mode)

The part-time Journal editor

Marketer

Build pages using components and templates, plus update text, images and CMS content (formerly Build mode)

The marketing coordinator who assembles event landing pages from approved components

Reviewer

View and comment on sites

The garden’s director, who approves changes but does not make them

Three seat types matter for editing.

  • A full seat is a regular Workspace member, such as a designer or an owner, who can use the whole Designer.

  • A limited seat is available on the Workspace plans for in-house teams. It can be given the Marketer or the Content editor role. Assigning the Reviewer role to a person on a limited seat moves them to a free seat, which makes the limited seat available to someone else.

  • A client seat is available on the Workspace plans for freelancers and agencies, so that a client can contribute to a site without receiving design access. It can be given the Marketer, Content editor or Reviewer role.

The documentation also warns about one boundary. On the Core and Starter Workspace plans, a person with a limited seat can reach every site in the Workspace, because those plans have no site-specific access; restricting a seat to chosen sites needs the Growth Workspace plan. Fernbrook keeps its public site and its internal volunteer-rota site in one Workspace, so it is on a plan that supports site-specific access, and the Journal editor is invited to the public site only. Plans, tiers and custom roles are detailed on the Plans, Workspaces, Seats and Roles page.

Opening Edit mode

Webflow documents more than one way in, depending on who the person is.

  • From the Dashboard. A content editor signs in to Webflow, hovers over the site’s card in the Dashboard and chooses the action that opens the site in Webflow. The site opens on the canvas in the editing experience.

  • From the Designer. A person who can design switches into Edit mode with the mode selector in the top bar, the dropdown that is labelled Designing while the Designer is in its normal state. A person who is already in the Designer is placed in Edit mode automatically when they enter it with a content role.

  • As a marketer. A Marketer works in the Designer’s page-building experience and can switch to the editing view of the same page whenever they want to check how their changes look to a visitor.

The canvas shows the real page at the width of the selected breakpoint. Interactions and most custom code do not run on the canvas, which is the same constraint described for the Designer on the Designer Tour page; to see the page as a visitor does, publish to the staging domain and open it there.

Editing static content

Static content is the copy that lives in the page itself: the hero heading on Home, the opening-hours paragraph on Visit, the image of the glasshouse on About.

  1. Hover over the element. When an element is editable, a blue outline appears around it.

  2. Click the element to select it. For text, select the words and use the pencil icon to start editing on the canvas.

  3. Type the new text. Select a range of characters to open a small formatting menu that offers the usual inline formats, such as bold, italic and a link.

  4. For an image, select it and choose a replacement from the asset library or upload a new file. Alt text is part of the image’s settings; see Images and Assets.

  5. Changes are saved as a draft. They reach visitors only after publishing.

Static elements inside a component are generally not editable on the canvas unless the designer attached a property to them. A property is the designer’s way of saying "this heading, this image and this link may change on each instance". This is how a designer lets the marketing coordinator change the headline and the photograph of an event banner component on every page that uses it while the layout of the banner stays fixed. The mechanism is explained from the designer’s side in Components: Props, Slots and Variants. A frequent complaint from editors, "I cannot click the text", is therefore almost always a missing property, not a permission problem.

What the editor’s change produces

An editor never sees markup, but a change to static content ends up in the page that is published. Here is what the Visit page’s heading looks like in the generated HTML after the editor changes the sentence; the class names were chosen by the designer and are untouched by the edit.

<header class="section is-hero">
  <div class="container">
    <h1 class="heading-xl">Open daily, sunrise to dusk, all year</h1>
    <a href="/visit" class="button is-secondary w-button">Plan your visit</a>
  </div>
</header>

Source: Webflow: Edit content

Only the text node changed. The element, its classes and the link target are the designer’s, which is exactly the guarantee of the model: the editor edits what is in the elements, never what the elements are.

Restricting what can be edited

Designers do not have to leave everything open. In the Settings panel of an element there is an Editing permissions control that blocks editing of that element. Fernbrook’s designer uses it for the legal notice in the footer and for the ticket price block on Visit, which a content editor should never rewrite by accident. The documentation lists one limitation: the control does not work for elements inside a Collection list or for elements bound to CMS data. For those, the controls are the CMS-level ones, which are the roles, the collection’s own permissions and the publish rights described on Publishing and Scheduling.

Editing CMS content

Dynamic content is edited either on the canvas or in the CMS panel; both operate on the same items.

  • On the canvas. Open a template page, such as a Journal article, and edit the title, the body and the image where they are displayed. Each element that is bound to a CMS field edits the item’s field. The canvas is the quickest way to proofread, because the editor sees line breaks and image crops exactly as visitors will.

  • In the CMS panel. Open the panel to find an item, create a new one, change fields that are not displayed on the page, set the item’s status, or edit an item that no page currently shows. The panel is where the editor also manages the Fernbrook Events collection, whose items appear in a Collection list and have no canvas position of their own.

A new Journal entry is created in the panel by choosing the collection, adding an item and filling in its fields: a name, a slug, a summary, a cover image, the body in the rich text field and a reference to its author. The field types, and which ones are required, are covered in Collections and Field Types; the reference fields that link an entry to its author and to plants are covered in Reference and Multi-reference Fields.

Drafts, saving and publishing

Whichever way content is edited, changes are saved as drafts first. A draft is not visible to visitors. An editor publishes it, if their role allows publishing, or asks a colleague to; a full-site publish does not publish items that are still drafts. The item states, scheduling and single-item publishing are the subject of Publishing and Scheduling, and the approval steps that sit in front of production for larger teams are described in Page Branching, Releases and Approvals.

Two people, one item

Webflow lets several people edit the same site at the same time. The documentation is explicit about what happens when two people change the same content at once: the last edits win, and no merge is attempted. The practical rule at Fernbrook is to assign each Journal entry to one editor, to use comments for requests and questions, and to check the activity log when a field has unexpectedly changed. Comments and the log are covered in Collaboration, Comments and Activity Log.

Localized content

The Webflow University material for the Content editor role includes a workflow for localizing content, and the documentation notes that localization features were never supported in the legacy Editor. Translating a page or a CMS item as an editor is therefore one of the capabilities that the canvas-based experience added. How locales are created and which plans include them is explained in Localization.

Page settings for editors

Editors and marketers also need to change what is around the content: the page title, the description that a search engine shows, and the image that a social network displays.

The Pages panel is available in Edit mode. From it a person can browse for a page, open it on the canvas, view the live page, and open the settings of any page. The settings that matter to content roles are:

Setting What it controls

Page name and slug

The label in the Pages panel and the path that visitors see. Changing a slug of a published page changes its URL, so redirects matter; see Redirects and Site Migration.

SEO title and meta description

The title and description that search results may show for the page

Open Graph title, description and image

The preview that social networks and chat applications build when someone shares the link

Indexing

Whether the page asks search engines not to index it

On a CMS template page the same fields are usually bound to CMS fields, which means that an editor changes the SEO title of a Journal entry by changing a field of that entry, not by opening a page setting. That is why Fernbrook’s designer adds an SEO description field to the Journal collection: the editor writes the description once, in the item, and the template page uses it. See SEO and AEO for the patterns and Collection Template Pages for how the binding is set up.

The legacy Editor and why it was retired

Until 2026 there was a second way to edit content: the legacy Editor. It was a simplified interface, reached by adding /?edit to a page address and signing in, that allowed content to be edited, for example by changing text or replacing an image, and nothing else. It had its own list of Editor users, separate from the Workspace’s members, and it supported the whitelabeling of the interface for agencies. Webflow’s explanation for the change is that the legacy Editor was a one-size-fits-all tool that gave simple guardrails for content changes, and that seats, roles and permissions give the same safety with more flexibility.

The differences that matter, according to the Help Center comparison, are these.

Aspect Legacy Editor Content editing in Webflow

Where it ran

A separate interface reached through /?edit

The Webflow canvas itself, in the platform

Who got access

Editor users that a site owner invited; no new Editor users can be added any more

Members with a Content editor role on a limited seat or a client seat

What could be edited

Content only: text, images and some CMS items

Static and dynamic content on the canvas, assets, and, as a Marketer, pages built from components and templates

Localization

Not supported

Supported for the Content editor role

Whitelabeling

Available, for agencies

Ended together with the legacy Editor on 2026-08-04

Cost

Editor users were invited separately from Workspace seats

A limited seat or client seat, which has a cost beyond the free migration seats

The timeline

Webflow announced in December 2024 that the legacy Editor would be deprecated, and published the schedule on 2026-02-02. The dates that the official migration page and blog post give are as follows.

Date What happened

2026-02-02

Client seats became available on the Workspace plans for freelancers and agencies. Legacy Editor invitations continued to work on all plans.

2026-05-04

Automatic migration began. Each legacy Editor user who had not yet been given a seat received a free client seat (on the Agency, Freelancer and Starter plans for freelancers and agencies) or a free limited seat (on the Growth, Core and Starter plans for teams). Migration of the users took two weeks. From this date no new legacy Editor users could be invited, while existing ones kept working.

2026-08-04

The legacy Editor, and whitelabeling with it, was no longer available. From this date everyone needs the role on their seat to open and update a site.

2026-10-05

The deprecation FAQ lists this date as the full deprecation of the Editor, after which the /?edit address no longer opens it.

Every user that was migrated automatically received the Content editor role. A Workspace owner or admin could change it to Marketer or Reviewer. Users of whitelabeled sites were excluded from Webflow’s deprecation emails, so the Workspace owner or admin had to tell them themselves. Enterprise customers were told to contact their customer success manager, and the FAQ has an Enterprise section, because Enterprise Workspaces have their own seat arrangements. The announcement closes with the remark that scheduled dates are subject to change, and the page gives 2026-02-02 as the last update, so the Webflow updates page and the Product Changes and Deprecations page are the places to follow any later adjustment.

What to do on a site that still mentions the Editor

A site, and the process around it, can outlive the tool. Fernbrook’s older documentation still told volunteers to "add /?edit to the address". The cleanup is short:

  1. Replace every instruction that mentions /?edit or "the Editor" with the steps in this page.

  2. Make sure every person who used to be an Editor user has a seat and the right role, which for most is Content editor.

  3. Remove bookmarks to /?edit addresses and links in welcome emails.

  4. If the site was whitelabeled, tell the client that the whitelabeled editing interface has gone, and that clients now sign in to Webflow with a client seat.

  5. Re-test the publishing path: a Content editor can edit and save, but who publishes is a permission that the owner decides; see Publishing and Scheduling.

A migration checklist for a team

For a team that has to explain the change to others, the sequence of events suggests this order.

  1. List the people who ever edited content, from the old Editor list and from the Workspace.

  2. Decide for each person: Content editor, Marketer or Reviewer.

  3. Check the seat budget: the free migration seats covered the people who were Editor users on the migration date; new people need a seat of their own.

  4. Check which sites each seat can reach, since Core and Starter Workspace plans have no site-specific access.

  5. Record the new instructions in the team’s own handbook, with a screenshot taken from the current canvas.

Where the older book is out of date

The book Webflow by Example (Packt, 2021) devotes its Chapter 14 to the Editor. It describes adding /?edit to the address of the published site, signing in, and using a bottom toolbar to edit content and save. Every step of that chapter describes a tool that Webflow retired in 2026, so it is superseded by this page: editing is now done on the canvas with a role on a seat. The book’s earlier chapters on the CMS still explain the concepts of collections and items well, and the concepts survive, but the instructions to log in to the Editor do not. The full list of outdated claims is in Where Older Books and Tutorials Are Outdated.

Practical advice

  • Give people the lowest role that fits. Most editors need Content editor; give Marketer only to people who assemble pages, and Reviewer to people who only approve.

  • Design for editors. Attach properties to the text and images in components, give Collection lists a clear no items state, and use Editing permissions on legal and price blocks.

  • Keep copy in fields, not in pages, where it repeats. A phone number or an address that appears on many pages is easier to keep correct in one place.

  • Agree on who publishes. Edit rights and publish rights are not the same thing, and a draft that nobody publishes is a frequent reason for "my change is not live".

  • Check on the staging domain. Before announcing a change, look at it on the staging domain, because the canvas does not run interactions or most custom code.

Where to go next

References