# Output & Live View: What the output can see

> The projection, and why it exists.

Glider documentation · Playout & On Air · Web page: https://cgglider.com/docs/live-output/public-state/

Sections of this page: [Output tab](https://cgglider.com/docs/live-output.md) · [Live view](https://cgglider.com/docs/live-output/live-view.md) · [What the output can see](https://cgglider.com/docs/live-output/public-state.md) · [Going live](https://cgglider.com/docs/live-output/going-live.md) · [Integrating with a mixer](https://cgglider.com/docs/live-output/integration.md)

The output never receives the full page. It gets a public projection, because /view runs on a studio floor machine, in an encoder, or on someone else's network.

| Stripped | Why |
| --- | --- |
| Control-panel layers, their groups and widget nodes | Operator surfaces belong in the editor. |
| Poller URLs, headers, bodies and last payloads | They can contain secrets. |
| Server log lines | They can echo secrets. |
| Rundown items whose workflow no longer exists | They cannot be taken. |

> **Implicit bindings are materialised:** Because widgets are stripped, the control→graphic links they implied are written out explicitly first. An operator moving a slider still paints the graphic on air.