Visual Editing: Click-to-edit for headless content
Vercel is extending its frontend cloud's collaborative workflow with Visual Editing, a click-to-edit mechanism for headless CMS content that currently works with Sanity. The feature, now in limited private beta for Enterprise Teams, lets anyone on a project—developer or marketer—edit content directly on a Preview Deployment without opening a separate CMS dashboard.
The capability builds on Vercel's Preview Deployment comments, which brought Google Docs- and Figma-style collaboration to web development. Visual Editing now targets the next bottleneck: finding and updating content in decoupled, headless architecture. Rather than hunting through a separate CMS interface, authors can click on content in the UI and make changes in place.
From headless to hands-on
In monolithic setups, a WYSIWYG editor makes on-the-fly content changes straightforward. A headless stack breaks that coupling, and content editing becomes a separate workflow. Visual Editing reconnects the rendered website to the content source.
Editing happens in two modes. A click on content in the browser synchronizes changes back to the CMS. For more substantial edits, you get a direct link to where that content lives in the CMS, so you can drill into richer editing workflows. No code changes to the site are required; CMS providers enable this by passing an additional argument when calling the CMS API.
Collaboration at production speed
The broader context is Vercel's push to make collaborative workflows as fast as technical ones. ISR keeps modern sites dynamic, reflecting content updates instantly. Preview Deployments automatically spin up with every commit. Now those same artifacts host the editing discussion—reviewers can iterate on actual content, not just comment on mockups, bringing the entire team into the refinement loop.
Partner ecosystem and availability
The feature launches with Sanity, built on "content source-mapping" technology. Vercel is working on an open specification for this mapping, aiming for any CMS, ecommerce system, or content source to support Visual Editing later. Implement the spec, they argue, and content editing becomes available without touching your site's code.
As of May 18th, Visual Editing is also available for Enterprise customers using Builder.io as their CMS. The private beta currently spans a limited set of customers and content providers; CMS vendors interested in integrating can consult Vercel's docs for the implementation guide.
