Visual editing

Click the text on your site.
Watch the Studio jump to that field.

Type, and the page updates as you go; no save, no reload, no separate preview URL. Sanity's Presentation tool, wired straight into the pages you already built. See all your custom blocks come to life instantly with Visual Editing from Sanity

Already server-rendered on Vercel & Netlify Or any Node PlatformOff by default, only one Viewer token needed
Nuxion Studio
yoursite.com drafts
click any highlighted text to edit it
Ship faster with a starter that thinks like a product
A component-driven Nuxt starter, wired to Sanity with every block editable in place.
Get startedSee pricing
Hero Image

Where this runs

Vercel, Netlify, or a Node server you run yourself

Presentation reads drafts through a server route, so it needs one. Vercel and Netlify are server-rendered as shipped — the only thing missing is a token.

  • Vercel — already server-rendered
  • Netlify — already server-rendered
  • A Node server you run yourself
  • Static host — Apache, cPanelsee Static Preview →

Built to stay safe

Editing overlays can't break your logic

Presentation marks rendered text invisibly so a click can trace it back to its field. Anything your code actually branches on — a layout choice, a style key — is kept clean of that marking automatically, so an editor's cursor can never confuse the page it's sitting in.

Stated plainly

The token stays behind the server. Always.

Presentation's overlays run through a server-side route built for exactly this, so the trust model never changes for the sake of convenience. A broader live-content channel that would need a token in the browser is deliberately left off — inside Presentation you already get live draft updates on a channel that never leaves the server.

A read token that can see drafts is never inlined into anything a visitor's browser downloads.

Opt-in

Off until you turn it on

Visual editing ships disabled. Turning it on is one token and one flag — and the Studio and the site both have to agree before anything changes, so it can't switch itself on by accident.

  • 1Click-to-edit, on the real pageOverlays sit on the rendered site itself, not a lookalike preview.
  • 2The token never reaches the browserA server-side proxy reads the draft; nothing readable ships to a visitor.
  • 3Works where you already deployVercel and Netlify qualify as shipped — no infrastructure change, one token.
  • 4Never a stale renderTurning this on retires the page cache automatically. Editors always see live changes

Stop customizing templates.
Start shipping brands.

Everything above just ran live on this page. Now picture it running yours.