Copilot Actions will take a folder on your PC and run a plain-English pass over every file in it. Your Webflow CMS is the kind of bulk job it is built for, except your content is not a folder. It lives in Webflow, where there is no diff to read first and no undo when a rewrite lands wrong.
Scratch pulls your collections down as exactly that folder. Copilot does 99% of the work, rewriting every item on your laptop. The last 1%, what actually publishes, stays a button only you press. Nothing reaches the live site until you have read the diff and approved it.
How it works
- Scratch pulls your collections into files. Every CMS item, page, and asset lands in a folder on your laptop, one file each. The Designer layout never moves.
- Copilot edits the items. Open the Copilot app on Windows and attach your Scratch folder to Copilot Actions. Describe the pass in plain English and it works through the collection in its own agent workspace while you watch. Rewrite every excerpt to one sentence and fix the title case. Copilot touches the files, never the live site.
- You review every diff and publish. Back in the Scratch app, each change sits next to the original, word by word. Approve what ships, and Scratch sends only those items through the Webflow CMS API.
What people use it for
The jobs that stall because the Webflow editor opens one item at a time:
- Collapse every blog excerpt to a single clean sentence and fix the title case.
- Backfill the SEO title and meta description on a collection that shipped without them.
- Carry a rename through a whole collection: body copy, headings, and SEO fields at once.
- Write alt text across an image-heavy gallery or case-study set.
- Localize a collection into a second language, where Webflow exposes locales.
Run it on a few items to feel the loop, then let it take the whole collection.
Why not an MCP server?
A Webflow MCP server wires an agent straight to your live CMS, publish button and all. One confident pass ships across the whole collection, and Webflow hands you nothing to roll it back with.
Scratch gives Copilot the same reach against a local copy instead. The publish step is lifted out and handed to you. Copilot can change anything in the folder; only you can ship it. On a live site with no undo, that gap is the whole point.
What Copilot edits in Webflow
- CMS collection items: rich-text, plain-text, slug, and custom fields
- Page metadata: title, slug, SEO and Open Graph
- Asset alt text
- Multi-locale content, where Webflow exposes it
The Designer layout, components, bindings, and reference targets are never exposed for editing. Validators check length caps, slug uniqueness, and any field you mark off-limits, so a rewrite cannot overrun an SEO limit or quietly break a binding. Ecommerce collections are out of scope. The full list lives on Scratch for Webflow.
Questions people ask
Is this a Copilot plugin or an MCP server?
Neither. A plugin or an MCP would hand the agent the publish button. Scratch keeps it. Copilot Actions only ever sees files in the Scratch folder, and publishing is a separate step you approve, one item at a time.
Will it touch my Designer layout?
No. Copilot only sees content fields. Layout, components, bindings, and reference targets are never pulled into the folder, and validators stop a rewrite from breaking a slug or blowing a length cap.
Webflow has no undo. Am I stuck if a change is wrong?
No. Scratch keeps the original beside the rewrite, so every published item rolls back per row, even though Webflow itself cannot. You decide which version stays.
How is this different from a CSV round-trip or a script?
A CSV re-import and a script both write straight to the live CMS with no diff and no per-item approval, and a find-and-replace does only what you spelled out. Copilot brings judgment to the items a rule misses, and Scratch still holds every change for review before it ships.
Can it sweep a whole collection from one brief?
Yes. Copilot Actions is built for folder-scale jobs. Run it on a few items first, then describe the pass for the whole collection.
Do I need to be technical?
No. Copilot Actions takes a plain-English instruction, so there is no terminal and no editor. You attach the Scratch folder, describe the change, and approve the diffs in the Scratch app. You do need the Copilot app on Windows.
See it on your own collection
The fastest way to trust it is to watch it run on your content. See it run on your Webflow CMS →, or download Scratch free and take the first pass yourself.