Can clients still edit a Framer site after export?

Yes, but not with Framer's own tools. Framer's client editing (Content Editor seats, on-page editing and the CMS) works on the Framer project and the site Framer hosts, so once you export a published Framer site and host the copy somewhere else, edits made in Framer never reach it: the export is a snapshot. After export, a client edits through something attached to the copy instead: a visual editor such as FNJ's, an AI app connected over MCP, a headless CMS that a developer wires in, or the code itself.

How clients edit a Framer site today

Framer sells a cheaper seat for people who only change content. Its roles and permissions article lists a Content Editor workspace role that "can manage CMS content, localization, and on-page editing across the workspace." Full editors can also get design and publishing access, depending on their permissions.

The main tool for that role is on-page editing. After you publish, an Edit button appears on the right side of the live site. Site owners and collaborators with Content permission click it and change "text and rich text, images, component properties, content on static pages and CMS content" in place, without opening the Framer canvas. New pages can be added this way only when they're CMS items, and on-page editing doesn't support layout templates or overlay content.

Edits don't go live on their own. When the client clicks Finish Editing, Framer emails the collaborators who can publish, and Framer's help center says "changes must be reviewed and published by a collaborator with publishing permissions before they become visible on the live site." With staging turned on, only members with Deploy permission can promote changes to the live site.

What it costs, from Framer's pricing page as of November 2026:

• Content editors: $10 per editor per month on Basic and Pro, billed yearly ($15 billed monthly).
• Additional full editors: $20 per editor per month, billed yearly ($30 billed monthly).
• Viewers (view and comment only): free.
• The workspace owner: free on Basic and Pro.
• Edit access: up to 10 users on Basic and Pro, unlimited on Enterprise.

Framer's help center adds that "workspaces without a subscription can collaborate with up to three editors," and that Pro Experts get free edit access to client projects. For a typical agency setup, client editing on Framer costs a Content Editor seat for each person on the client side who edits, on top of the site plan, unless the client is the workspace owner.

How other builders handle client editing

All five builders below have some version of the same thing: a restricted role for content, sometimes with its own seat. Each row comes from the vendor's own pages, checked in November 2026.

Builder	How a client edits	Separate seat or role?	Plan notes
Framer	On-page editing on the live site, plus the CMS	Content Editor seat, $10 per editor per month billed yearly ($15 billed monthly)	Basic and Pro allow up to 10 users with edit access. Edits wait for someone with publishing permission.
Webflow	Content editor role inside Webflow; adding ?update to a live page's URL opens it for editing	A client seat (included per site) or a limited seat ($15 a month per seat billed yearly, $19 billed monthly)	Client seats only on Workspace plans for freelancers and agencies: 1 per paid site on Starter, 1 per site on Freelancer, 3 per site on Agency. Extra client seats can't be bought.
WordPress	Block editor in the WordPress admin	Role: Editor, Author or Contributor	Roles are built into WordPress, which is open source software.
Wix	Site editor and dashboard, limited by role	Collaborator seat with a role such as Content Writer, Blog Writer or a custom role	1 collaborator seat by default (5 on a Wix Studio account). Light 2, Core 5, Business 10, Business Elite 100.
Squarespace	Edits existing pages with the Website editor permission	Contributor with permission roles	Basic: one contributor besides the owner. Core, Plus and Advanced: unlimited.

A few details matter for client work:

• Webflow retired its old Editor. The deprecation FAQ says that as of October 5, 2026 the legacy Editor "is fully deprecated and can no longer be accessed," so every editor now needs a Webflow account with a seat. Client seats are site-specific. A content editor "can update site copy, media, and CMS content without changing design," and can publish only if "Can publish" is switched on.
• Wix has a Content Writer role that "can edit text, links, and media sources in the site editor" and add or edit items in existing CMS collections. Collaborators need a Wix account.
• Squarespace's Website editor permission can add content to existing pages but can't add new pages or make style changes. Contributor limits are on the invite page.
• WordPress separates writing from publishing. An Editor "can publish and manage posts including the posts of other users," while a Contributor "can write and manage their own posts but cannot publish them" (Roles and Capabilities). The block editor has been the default since WordPress 5.0 in December 2018.

The pattern: client editing is part of the platform the site runs on. Even Webflow, which offers code export on paid Workspace plans, says on its pricing page that "if you export your code, it can't be reimported." Once files leave a builder, the builder's editor no longer touches them.

What stops working when you export a Framer site

Framer's help center says "Framer does not offer HTML export for self-hosting" (Framer Help). FNJ works from the published site's public URL instead and turns it into code you own: a Next.js project, static HTML or an Astro project.

Once that copy runs on your own host:

• On-page editing doesn't reach it. The Edit button and the review-and-publish flow belong to the site Framer publishes. A client who edits there changes the Framer-hosted site, not your copy.
• The Framer CMS stops feeding it. CMS items are captured as pages as they were on the day of export. A post added in Framer later won't appear in the copy. FNJ's post on what happens to Framer CMS collections covers this in detail.
• Content Editor seats don't help. They grant access to the Framer project, so paying for one does nothing for a site hosted elsewhere.
• Some requests still go to Framer. In an FNJ export, pages and images are copied into the project, but Framer's runtime script (which runs animations and interactions) and the fonts still load from Framer's CDN.

So the real question isn't whether the client can keep using Framer's editor. It's which editing tool you attach to the copy, and who holds the login.

One step to take before you export: save the CMS data. Framer's own CMS Export plugin exports "any CMS collection as a CSV file," which you'll want if the content later moves into a headless CMS.

Four ways to let a client edit after export

1. FNJ's visual editor

FNJ's visual editor works on sites converted with FNJ. In it you can edit text, links, images and videos; hide or show elements; adjust element sizes; set each page's title and meta description and the site's social preview image; add sections and pages; and manage collections and items in FNJ's own CMS, which publish as pages (it doesn't import or sync Framer's CMS collections, which arrive as static pages). Edits are applied on top of the converted site. Publishing sends the result to your own host, and you can download the code with the edits applied.

The limit to plan around: FNJ has no separate client logins, seats or team invites today. The FNJ account that owns the site does the editing. For an agency, that means either making changes on the client's behalf or handing that account to the client at the end of the project. Our handoff guide covers which accounts the client should own. Converting needs a paid FNJ plan (pricing).

2. An AI app over FNJ's MCP server

FNJ's MCP server lets AI apps such as Claude, Cursor and Codex edit a converted site's text, styles, sections, pages and CMS items, and publish it. A client who already works in one of those apps can ask for a change in plain language, such as "replace the headline on the pricing page" or "add a new page for the spring offer", instead of learning an editor.

Two caveats. It doesn't add client logins: FNJ has none today, so the AI app works through the FNJ account that owns the site. And ChatGPT isn't a general option: OpenAI's help center says custom MCP server connections and full MCP support are available for ChatGPT Business and Enterprise/Edu customers on ChatGPT web. The MCP website editing guide explains how this kind of editing works and what to check before letting an AI agent publish.

3. A headless CMS wired into the Next.js project

For a site that publishes often, the lasting answer is to move the content into a CMS and have the exported Next.js project read from it. The usual choices each document a Next.js setup:

• Sanity. Its docs say next-sanity "is the official integration package for Next.js," and Sanity Studio can be mounted as a route inside the app. With Visual Editing, editors click rendered content to open the matching field (Sanity docs).
• Contentful. Contentful's App Router guide walks through a content model, fetching with React Server Components, webhook-triggered revalidation and Draft Mode previews. Its prerequisites include "Intermediate knowledge of JavaScript and React.js."
• Git-based CMSs. These keep content as files in your repository. Decap CMS calls itself "an open source content management system for your Git workflow" (Decap docs), and its Next.js guide adds an admin page under public/admin, using Netlify's Identity and Git Gateway services for logins. Netlify now marks Git Gateway as deprecated, so check Decap's other backends first. TinaCMS is "an open-source, Git-backed headless content management system"; editors work at /admin, and each save is committed back to the repository.

Be straight with the client about what this is: developer work. The exported pages aren't connected to any CMS, so someone has to model the content, import it (the Framer CSV export helps), and change the page components to fetch it. After that, each editor gets their own login and a publishing flow, under the CMS's own plans and user limits, so check those first.

4. Edit the code directly

The exported project is yours, so a developer can open it, change the text and redeploy, often the quickest route to a one-line fix. For most clients it isn't realistic: it means a code editor, a deploy step and some care not to break the layout. Don't mix this with FNJ's editor on one site: changes made in the downloaded code don't carry into it.

Which option fits which situation

Situation	Best fit	Why
Agency with a non-technical client who makes occasional text and image changes	FNJ's visual editor	Point-and-click edits that publish to the client's own host. There are no separate client logins, so agree who holds the account.
Client who already works in Claude, Cursor or Codex	FNJ's MCP server	Changes by request in plain language, through the FNJ account that owns the site.
Solo or in-house developer	The code	You already have the project and the deploy step.
Content-heavy blog with several writers	A headless CMS (Sanity, Contentful, Decap, TinaCMS)	Each writer gets their own login and drafts. Needs a developer to set up.
Client who specifically wants Framer's editor	Don't export: stay on Framer with a Content Editor seat	Framer's editing tools only work on the site Framer hosts.

The last row is a real answer. If the client's main need is updating the site in Framer, exporting takes that away. Export when the reason to move is hosting cost, owning the code or a developer taking over, and pick the editing route before the handoff.

Frequently asked questions

Can my client edit the site after I export it from Framer?

Yes, but not in Framer. Framer's on-page editing and CMS work on the site Framer hosts, and edits made there don't reach an exported copy. After export, the client edits through a tool attached to the copy: FNJ's visual editor, an AI app over FNJ's MCP server, a headless CMS that a developer adds, or the code.

Does the Framer CMS still work after export?

Not for the exported copy. CMS items become static pages as they were on the day of export, and items added in Framer afterwards don't appear. FNJ's editor doesn't import or sync Framer's collections, but it has its own CMS, where new collections and items publish as pages. To keep the existing content as structured data, save each collection as a CSV with Framer's CMS Export plugin and move it into a headless CMS.

What is the easiest way for a client to edit a static site?

A visual editor that publishes straight to the site's host, so the client clicks on text and images instead of touching files. For a Framer site converted with FNJ, FNJ's visual editor does this. Git-based CMSs such as Decap and TinaCMS add an admin page where editors log in, but a developer has to set them up first.

Do I need a developer to update an exported Framer site?

Not for routine changes. On a site converted with FNJ, text, links, images, videos, page titles and descriptions, sections and pages can be changed in FNJ's visual editor and published to your own host, and new collection content can go into FNJ's own CMS. The Framer CMS items you exported are static pages, not entries in that CMS. You need a developer for changes the editor doesn't cover, such as connecting a headless CMS or editing the code itself.

Can clients edit a Webflow site without a paid seat?

Yes, if the site sits in a Workspace on a plan for freelancers or agencies. Webflow includes client seats per site at no extra cost: 1 per paid site on Starter, 1 per site on Freelancer and 3 per site on Agency, and more can't be bought. Otherwise the client needs a limited seat, listed at $15 a month per seat billed yearly ($19 billed monthly) as of November 2026.

How much does a Framer content editor seat cost?

As of November 2026, Framer's pricing page lists content editors at $10 per editor per month on Basic and Pro with yearly billing, or $15 with monthly billing. A full editor is $20 or $30, viewers are free, and the workspace owner is free on Basic and Pro. The seat only gives access to the Framer project, so it doesn't help with a site you've already exported.

If you're planning an export for a client site, FNJ's Framer export page explains what the conversion produces and what still loads from Framer, so you can settle the editing route before the handoff.