CutCopy

Design tokens do not travel well between Webflow sites. Paste a class into a second site and a color that was saved as a variable arrives as a plain color value, so the token has to be created again by hand. Shared Libraries cover part of this, sharing components and variables across sites inside one Workspace on a paid Workspace plan, but they do not reach a client site that sits in someone else's Workspace.

CutCopy is a Webflow App from Flowcraft that exports a variable collection out of one project and imports it into another, with a review step before anything in the destination is overwritten. It also copies element attributes from one element to another inside a project.

It earns its place for freelancers and agency teams who rebuild the same token set on every new client project, and for anyone holding several sites on one design language across separate Workspaces.

How to integrate CutCopy with Webflow

What is CutCopy? CutCopy is a variable and attribute manager for Webflow, built as a Designer Extension by Flowcraft. It saves variable collections and themes to a CutCopy account so you can pull them into a later project, and it carries element attributes between elements on the canvas.

Teams reach for it at the point where a second site needs the first site's tokens and a native copy and paste has already lost them. Two routes are worth knowing. The CutCopy app moves existing variables between projects from inside Webflow. Webflow's MCP server writes variables and styles from an agent, which suits a token set you want generated or reworked rather than duplicated.

Install the CutCopy app

Installing the app adds a variable and attribute panel inside Webflow, so nothing is embedded in your published site and no script has to be maintained.

The app covers the following:

• Variable export and import: Export a collection from one project and import it into another, rather than retyping every token in the destination.
• Smart Import: Highlights what an incoming collection changes or adds against the site's active variable collection before you accept it.
• Variable cherry-pick: Select single variables or one folder, such as typography, instead of taking a whole collection across.
• Variable themes and collections: Save themes, collections and subsets to a CutCopy account and retrieve them on a later project.
• Attribute Clipboard: Copy one attribute or a whole attribute set from an element and paste it onto another element.
• Attribute templates: Save an attribute configuration and reuse it, which helps when a script expects the same attributes on many elements.

The marketplace listing notes that saving variable themes and collections requires a CutCopy account. The attribute side of the app works on elements already in your project.

To set up the integration:

1. Open the CutCopy listing in the Webflow Marketplace and click Add to site.
2. Select the sites or Workspaces you want it on, then click Authorize app.
3. Open the site in Webflow, find CutCopy in the Apps panel and click Launch.
4. Create a CutCopy account if you plan to save collections or themes for reuse.
5. Export the collection from the source project, then open the destination project and import it.

Authorizing at the Workspace level grants the app access to every current and future site in that Workspace, which is worth knowing before you pick that option for a client account. You can see what a site has authorized at Site settings > Integrations > Authorized apps, and revoking happens on a different tab, at Site settings > Apps and integrations. Workspace-level access is removed at Workspace settings > Apps and integrations > Uninstall app, and that takes the app off every site in the Workspace, as Webflow's Apps overview sets out. Variables and attributes the app already wrote stay in the site, because they are ordinary site data rather than anything injected at publish.

Two limits here belong to Webflow rather than to CutCopy. Pasting a whole Collection list into another site produces an empty one, because Webflow CMS data stays with the source site; the documented workaround is to nest the Collection item's contents in a Div block and copy that, which brings the classes over. A color saved as a variable also arrives as a plain color when you paste a class between sites, and has to be added back as a variable. Both are described in Webflow's guide to copying between sites.

Move design tokens with Webflow's MCP server

Webflow's own MCP server reaches variables directly, which matters when the destination needs a token set built or reworked rather than duplicated. Its design system tools define variables, color schemes, typography scales and spacing systems, and its style tools can migrate older classes onto variables. So it fits "rebuild these tokens with different values" better than it fits a straight transfer, and the two approaches sit alongside each other rather than competing.

One documented MCP limit is directly relevant to cross-project work: each authorization reaches a single Workspace, and using a different Workspace means re-authenticating. Agents also work inside your existing Webflow permissions and roles, and their changes land in the site activity log, so a token rewrite driven from an agent is reviewable after the fact.

What you can build with CutCopy Webflow integration

The value shows up when one design system has to hold across projects that Webflow treats as unrelated, which is the normal shape of agency and freelance work.

Common uses of the pairing include:

• Token handoff across Workspaces: Export a master collection from your own project and import it into a client site in their Workspace, where a Shared Library cannot reach.
• Project starter kits: Keep one project as the token source, then import its themes into each new build instead of restyling from a blank slate.
• Partial token adoption: Cherry-pick a typography folder or a spacing scale into a site that already has its own colors, without overwriting a live collection.
• Attribute-heavy builds: Copy attribute sets between elements when a third-party script expects identical attributes on many elements.
• Design system restore points: Save a collection to your CutCopy account before a large restyle, so there is something to import back if the new values do not hold up.

Review what an import changed before you publish, because renaming a variable ripples through every style that references it. For the same work driven from an agent instead of a panel, connect the MCP server and have it read and write your site's variables directly.