---
title: What the server sends
description: When a server renders the page, Markless sends HTML plus a state record, a view record, and a small inline resumer, all inside one container div.
sidebar: { label: The payload }
---
:::info[One environment's format]
This page covers the server environment: `renderToString()`, `renderToStream()`, and `@markless/router`. It is one way to deliver the compiled plan, not the core model. In the browser, `render()` builds the page directly and writes none of these scripts.
:::
Last page, the compiler planned the state and view records for `Counter.tsrx`. When a server renders the page, those records travel inside the HTML.
## HTML with notes taped inside
The *payload* is everything the server adds to your HTML so the browser can continue. The server runs the component body once. Then it writes two JSON notes: the state values, and which element does what. A small script waits beside them.
Think of a model house with the wiring diagram taped inside the door. That is an analogy. Nobody rebuilds the house to make the doorbell work.
Point at each part of the HTML.
Notice that the button carries no event attribute. The click lives only in the view note.
## The real response
I built `Counter.tsrx` with the Markless Vite plugin and called `renderToString()`. I cut the two inline scripts to `…`:
```html
```
- The `link` lets the browser fetch the resume module early. The resumer imports it only after the first event.
- The first script records events that fire before the page finishes loading. The resumer picks them up.
- In `"value":{"version":1,"root":0,"records":[]}`, `root` holds the number `0`. Objects and arrays go into `records`.
:::tip[Why does my static page have no scripts?]
I built the same component with `
Count {count}
` and no handler. The response was `
Count 0
`. No notes, no resumer.
:::
:::note[Why is the JSON readable?]
Both notes are plain `JSON.stringify` output. `@markless/serializer` escapes `