Desktop & open-source edition. Prefer your browser? Open this in the Spectersync webapp →subscribe now for 500 free credits.

Specter for Webflow Beta

Edit your whole Webflow CMS with any AI, in one pass.

Specter pulls every item in your Webflow CMS collections down to a folder of local markdown. Now Claude, ChatGPT, Gemini — or your own scripts — can read every blog post, case study, or collection item at once, rewrite at scale, and Specter streams the changes back through the Webflow Data API. CMS collections only — never the Designer, your site structure, or your e-commerce.

Any Webflow plan with the CMS · macOS 13+ · paid official app · free forever on GitHub.

Also for: Ghost →  ·  WordPress →  ·  Shopify →

Why Webflow operators reach for Specter

The Webflow Editor opens one CMS item at a time

Webflow's CMS is built for craft — a designer builds the template once, and the Editor lets a writer fill in one item at a time. That's fine for a launch and painful at scale. The Webflow AI Assist is fine for a paragraph, useless across a hundred posts. The Data API is honest and rate-limited. Specter takes a different angle. Your Webflow CMS items get pulled into a local folder as standard markdown. You edit them with whatever tool you want — including the AI subscription you already pay for — and Specter pushes them back through the Webflow Data API.

What you can do

The bridge between Webflow and everything else

Specter isn't an AI and it isn't a CMS. It keeps your live Webflow CMS and a folder of local markdown perfectly in sync — so every other tool you own can finally reach your content, all of it, at once.

Full-archive context for AI

Every item in every Webflow collection you choose lives in one folder of plain markdown. Point Claude, ChatGPT, or Cursor at that folder and the AI sees the whole archive at once — accurate internal links, consistent tone, no blind one-item rewrites.

Bulk SEO across every collection item

Run an AI pass across hundreds of CMS items — rewrite SEO titles, regenerate meta descriptions, swap CTAs, fix outdated product mentions. Specter streams the result back through the Webflow Data API in the background.

Migrate to or from Webflow

Specter speaks the same markdown to Webflow, Ghost, WordPress, and Shopify. Pull from Webflow and push to Ghost (or vice versa) by changing where the same folder syncs.

Any AI, no lock-in

Claude, ChatGPT, Gemini, Copilot, your own scripts — they all read the same markdown on disk. Specter is the bridge; you bring the intelligence.

Two-way sync

Edit locally → Specter pushes. Edit in the Webflow Editor → Specter pulls down. Each CMS item round-trips with its frontmatter: slug, name, published state, reference fields, plain-text rich-text body, and the SEO fields the collection exposes.

Dry-run preview

Preview Sync before you commit. See which Webflow items would be created, updated, or flagged as conflicts before any of it touches your live site.

OAuth, scoped to the CMS only

Specter requests sites:read cms:read cms:write. Your Designer, components, interactions, and e-commerce are not in the scope. Your OAuth token lives in the macOS Keychain on your Mac — never on our servers. Revoke from your Webflow dashboard any time.

Plain markdown, no lock-in

Standard YAML frontmatter. Your content stays yours on your disk. Cancel any time and keep every file.

How it works on Webflow

Three steps. No drama.

01

Step

Authorize Specter in Webflow

Click Connect Webflow site, sign in to Webflow, and approve the install. Webflow shows you exactly what Specter will access — your CMS, scoped to the sites you authorize, nothing else.

02

Step

Specter opens on your Mac

Your Mac launches Specter and finishes the OAuth handshake securely. No tokens travel through your browser URL.

03

Step

Pick collections, pick a folder, write

Choose which collections to sync (one site can have many — pick the ones with editorial content). Each CMS item becomes a markdown file in the folder you picked. Edit in Obsidian or VS Code, or hand the folder to Claude. Save. Specter pushes back.

What round-trips today

The Webflow capability map

Specter syncs the editorial text content of your Webflow CMS collections. The Designer, site structure, components, interactions, and Webflow Ecommerce are deliberately out of scope.

Pushes and pulls today

CMS collection items, name, slug, draft / published / archived state, rich-text body (markdown ↔ Webflow rich text), plain-text fields, number and date fields, reference and multi-reference fields by item id, image fields by URL, and the SEO fields each collection exposes (meta title, meta description, OG image, canonical).

Specter never touches

The Designer, page structure, components, interactions, custom code, site SEO outside CMS items, forms, Memberships, Webflow Ecommerce orders / products / inventory, redirects, hosting settings. CMS collections only — period. See the full capability matrix →.

Pricing

One annual subscription. Every platform.

Buy the signed, supported app, or use the open-source GitHub project for free forever.

Open source
$0
  • Free forever on GitHub
  • Inspect, fork, and build the source
  • Good fit for technical users
  • No signed installer or priority support
View on GitHub

FAQ

Webflow questions, answered

Which Webflow plans does Specter work with?
Any Webflow plan that exposes the CMS — Basic doesn’t include the CMS, so you’ll need CMS, Business, or Enterprise (Site plans) or a Workspace plan that publishes to a CMS-enabled site. Specter authenticates via standard Webflow OAuth, so if you can install a Webflow App on the site, you can install Specter.
Why is this called "beta"?
The OAuth handshake, the pull, and the push for the most common CMS field types (plain text, rich text, slug, switch, number, date, image URL, reference) are all working. We’re still expanding fidelity for the less common field types and edge cases — see the capability matrix for the current state. The beta label comes off when those last edges round-trip cleanly.
Can Specter edit my Designer pages or components?
No. Specter syncs the Webflow CMS — the items inside your collections. Designer pages, component instances, interactions, and custom code are not in scope and not visible to Specter. The Designer remains the Designer’s job.
Does Specter see my e-commerce orders or customers?
No. The OAuth scope Specter requests is sites:read cms:read cms:write. Webflow Ecommerce — products, variants, orders, customers, inventory — is not in the scope and not visible to Specter. You can verify the exact scopes during install — Webflow lists them on the approval screen.
Where does the access token live?
In the macOS Keychain on your Mac, not on our servers. No tokens travel through your browser URL during OAuth. You can revoke from your Webflow dashboard (Workspace → Apps & integrations → Authorized apps → Specter → Revoke) at any time.
What about Webflow’s rich-text editor and embedded components?
Specter converts the rich-text body between Webflow’s rich-text format and standard markdown in both directions, preserving headings, lists, code blocks, links, images (by URL), and inline formatting. Embedded components and custom HTML blocks inside rich text round-trip as opaque blocks you can keep, edit around, or rewrite — Specter won’t silently break them.
Does it work across multiple Webflow sites?
Yes. One Webflow account can authorize Specter for multiple sites — pick which sites and which collections per site to sync. Each gets its own connection and its own sync folder.
Does Specter publish to staging or to the live site?
Specter writes to the Webflow CMS, which is the same surface the Webflow Editor writes to. Your existing publish workflow (staging URL → publish to your live domain) keeps working — Specter doesn’t bypass it.

Bring AI to your whole Webflow CMS

Buy the official app, or build the free open-source version.