Browsers standardize out-of-order HTML streaming for faster page loads
Chrome, Edge and the HTML standard now support server-driven streaming so usable page sections can render before the full response arrives.
Browsers are standardizing a server-driven HTML streaming pattern that lets parts of a page become usable while other sections are still loading, without relying on framework-specific tricks. A new declarative mechanism uses the existing <template> tag with a for attribute and special processing-instruction markers (like <?start>, <?end>, and <?marker>) so servers can later stream in HTML chunks that patch specific DOM positions. The spec constrains where a <template for> can inject content to limit cross-component injection, but makes an exception for templates placed directly under <body>, which can update across the whole document. Matching JavaScript APIs add static and streaming DOM insertion methods such as setHTML, appendHTML, and streamHTMLUnsafe(), plus a Fetch helper response.textStream() that pipes streaming text into the browser’s HTML fragment parser. These markup features are now in the WHATWG HTML Living Standard, with Chrome and Edge 150 implementing them (and textStream() in 151), while WebKit has issued a supportive standards position and Mozilla has indicated interest.
Why it matters
This brings a pattern that once lived in custom server setups and JavaScript frameworks into the browser itself, making partial page rendering a built-in capability instead of an ad hoc trick. Pages can become interactive sooner as sections stream in, while servers and clients coordinate via standardized HTML primitives and JavaScript APIs. With support in the HTML Living Standard and current Chrome and Edge releases, this approach moves from experiment to baseline behavior across modern browsers.
Signal or noise?
Does this story matter, or is it hype? Decide before you see what everyone else thinks.