# I Tested Webflow's New Pan & Zoom and MCP — My Honest Review Aug 16, 2026 · 5 min read · Webflow, Designer, Productivity, Figma, MCP, AI I've been testing Webflow's new Pan & Zoom canvas and Webflow MCP. Pan & Zoom is genuinely great. MCP depends on the task — ~20% on a from-scratch build, ~70% on CMS edits. My honest review of both. ## Key Takeaways - Pan & Zoom removes the biggest daily friction in the Designer — spacebar-drag to pan, Cmd/Ctrl + scroll to zoom - MCP is great for small edits but not ready for major builds — results vary a lot by model and task - My tests: DeepSeek V4 Pro got ~20% of a from-scratch build; Claude got ~70% accuracy on CMS edits in real client work - The result depends on the model, the task, and how clearly you prompt — not on MCP alone - Both features point toward Webflow's 'agentic canvas,' but it's not fully here yet Webflow has shipped two things worth talking about lately: the new Pan & Zoom canvas, and Webflow MCP. I've been using both, so here's my honest review — what's great, what's not, and where I think they're heading. One quick note before I start: this is my own experience, one developer testing things in my own workflow. I could be wrong, and your mileage may vary. But I'd rather share what actually happened than another "Webflow just released X!" hype post. ## Feature 1: Pan & Zoom for the Canvas The canvas used to only scroll top to bottom. Now you can pan and zoom the same way every modern design tool works. Here's [Webflow's official update](https://webflow.com/updates/page-pan-zoom) if you want the full detail. ### How to turn it on Click the arrow icon on the canvas bar — hover over it and the label "Expand Canvas" appears — and the canvas switches to pan-and-zoom mode. Click it again to go back to scrolling. ### The gestures - **Pan** — hold spacebar and drag, use middle-mouse drag, or scroll with two fingers on a trackpad. The cursor switches to a grab / grabbing state so you always know what mode you're in. - **Zoom** — Cmd/Ctrl + scroll, or pinch. There's also a zoom dropdown up top if you want to jump straight to 50%, 100%, or 200%. - **Resize the frame width** — drag the frame edge to widen or narrow the viewport you're designing in. If you've spent time in Figma, the zoom gesture is already muscle memory. That's the point — Webflow is finally matching how design tools already work. ### Why it matters If you don't build in Webflow every day, this looks like a small quality-of-life tweak. It isn't. Before this, moving around a big project meant reaching for the scrollbars, switching to the hand tool, or zooming out and back in just to find where you were. On an 18-page site — or even a single tall landing page — that's constant friction. > Navigation friction is a tax you pay every minute you're in the Designer. It's small, but it never stops charging. With pan and zoom, you just move. Spacebar-drag to slide around, Cmd-scroll to zoom in and out, and you never lose your place. I've been using it daily for a couple of weeks, and it's quietly saved me a ton of back-and-forth. One note: it works in Design, Build, and Edit modes, but not Preview or Comment — so don't go hunting for the icon in the wrong view. **Verdict:** use it. It removes the biggest daily friction in the tool, with no downside. ## Feature 2: Webflow MCP MCP is the bigger one — and this is where my honest take gets less glowing. For context, MCP (Model Context Protocol) is what lets an AI like Claude actually connect to your Webflow site and work inside it — reading collections, editing fields, applying fixes. Pan & Zoom is about how you move around the canvas. MCP is about an agent moving around it for you. Here's [Webflow's official MCP server docs](https://developers.webflow.com/mcp). ### What I actually tested I ran two very different tests, with two different models — so treat both numbers as my own experience, not a universal measurement of Webflow MCP. **Test one — a from-scratch build.** I connected Webflow MCP to OpenCode, using DeepSeek V4 Pro, and tried to build my own portfolio from scratch using Client-First — a larger build, not a small tweak. I gave it no images and no assets. Nothing. The result is [still live here](https://chabdullahdev.webflow.io/) if you want to judge for yourself. Honestly, it got further than I expected. It pulled my live site's design system — the gold accent, the dark background, the grain effect, the button and card styles — and built a complete homepage skeleton: navbar, hero, about, services, portfolio, FAQ, CTA, footer. It even found and pulled my real project screenshots on its own, without me uploading a single image. It wrote custom JavaScript for scroll effects and an FAQ accordion, and added SEO extras I never asked for — FAQ schema, meta descriptions, even my analytics tag. Then it quietly fell apart on the details. Around ten elements were left with Webflow's default placeholder text. The subpages it created were empty shells — just a heading and a footer. "View all projects" and every FAQ item were dead links. And some of the JavaScript it wrote targets elements that never got created, so interactions that look done do nothing when you click. So what's the honest verdict? Structure is maybe 65% there, content around 40%, working features barely 10%. As a finished, launch-ready site, that's roughly 20% — but it's a real foundation with the right design system already applied, not a blank canvas. **Test two — CMS edits on real client work.** At Jaryah, I've used Claude with Webflow MCP for actual CMS edits and changes on real client projects. This time the result was a lot better — roughly 70% accurate on the edits I tested. Two different models, two different kinds of task, two very different results. ### My honest review This is just my experience, and I could be wrong — but here's how I read it right now: - **MCP is great for edits.** CMS issues, fixing a broken link, small jobs — it clicks, it fixes, it's done. My Claude CMS work landed around 70% accurate. - **MCP is not great for major builds.** Building a full site from scratch is beyond where it's at today. My DeepSeek build test stalled out around 20%. - **The model and the task matter more than "MCP" itself.** The ~20% build result and the ~70% CMS result aren't the same thing — different models, different kinds of work, different outcomes. > MCP won't replace the developer. It replaces the small, tedious jobs so you can spend your time on the parts that actually need judgment. The ~70% also made me wonder how much further this could go with better prompting, clearer instructions, and a more structured workflow. Maybe it can get much closer to 100%, but that's something I still need to test. If you're using MCP, my advice is to give it small, well-scoped work. Don't hand it "build me a site from scratch" and expect a finished result. And don't judge the whole tool on one run — the result depends on the model, the task, how clearly you prompt it, how well it understands your site's existing structure, and how much you verify. ## The Bigger Picture Here's what connects both features. Webflow calls this the "agentic canvas" — a canvas rebuilt so AI agents can eventually move around it the same way you do. Pan & Zoom is the foundation. MCP is the agent. Today, both are useful but incomplete — Pan & Zoom is genuinely great, while MCP is great for small jobs but not ready for big ones. The direction is clear, though. Webflow is slowly turning the Designer into a space where you and an AI work side by side. We're not there yet, but you can see the shape of it. > The best tooling updates don't add features. They remove friction. ## Try It Yourself - Click the arrow icon on the canvas bar (hover to see "Expand Canvas") to enable pan and zoom - Spacebar + drag (or middle-mouse drag) to pan - Cmd/Ctrl + scroll to zoom in and out - Drag the frame edge to resize the viewport width And if you have MCP set up, hand it one small fix — not a full site — and see how it does.