Streaming sends parts of the response as the model generates them instead of waiting for the complete answer. HTTP APIs often deliver these updates through server-sent events.
Users see the first text sooner, which makes a slow generation feel responsive. The application can also display tool progress, usage updates, or status events when the provider exposes them. Total generation time may stay the same.
Streaming adds client work. Chunks may split words or JSON, event types must be assembled correctly, and errors can occur after partial output has been shown. Buffer structured data until it is complete, support cancellation, and mark an answer complete only after the final event and finish reason arrive.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓