# See the edit on the real page, before it ships.

> Not a mock-up and not a rendered approximation. Your deployed page loads in the editor with the pending change painted on top, using your CSS, your fonts and your images.

## Why this preview is worth trusting.

- **It is your real site:** The page in the frame is the one your host is serving right now. Nothing is re-rendered or approximated.
- **Works behind a password:** If the deployment sits behind a protection wall, paste one bypass secret and previews keep working.
- **No host account needed:** The preview address is read from the deploy signals your Git provider already receives, so there is no hosting token to hand over.
- **Served from its own domain:** Previews load on a separate domain, so a previewed page can never reach the session that holds your dashboard.

## From staged edit to confident publish.

1. **The client stages an edit** They type the change. Nothing is committed and nothing is live yet.
2. **The real page loads** The editor fetches your deployed page and shows it in a frame.
3. **The change is painted on** The pending value replaces the live one, with a short highlight so the client sees exactly what moved.
4. **They publish, or keep looking** Nothing has touched the repository until publish is clicked.

## Use cases

- **Checking a headline before it ships:** The client sees the new wording in the real typeface at the real width, not inside a text box.
  > A headline that fits neatly in the editor but wraps to three lines on the live page is caught here, not after publishing.
- **Approving a photo swap:** The new image lands in the same crop and position as the old one, so the client sees the actual result.
- **Walking a client through a change:** Pop the preview out to its own window with the editor toolbar attached, and share the screen.
- **A site that is not public yet:** A staging deployment behind a password wall previews the same way a live one does.

## FAQ

### Is the preview a simulation of my site?

No. It is your deployed page in a frame, with your CSS, your fonts and your images. The pending change is painted on top of the real thing.

### Does previewing publish anything?

No. Nothing reaches your repository until publish is clicked. A preview only reads your live site.

### My deployment sits behind a protection wall. Does preview still work?

Yes. The editor detects the wall and asks for a bypass secret. Paste it once per site and previews resolve normally.

### Do you need access to my hosting account?

No. The preview address comes from the deploy signals your Git provider already receives. There are adapters for Vercel, Netlify and Cloudflare, and none of them need a token from you.

---

- [All features](https://cmsbrew.com/features)
- [Chat editing](https://cmsbrew.com/features/chat-editing)
- [Publish and revert](https://cmsbrew.com/features/publish-and-revert)
- [Images](https://cmsbrew.com/features/images)