FmtDev
Idioma

RSC Payload Decoder

Debugging complex server-client boundaries can be daunting when working directly with the raw React Flight Wire Format. When your application loads, the server streams these intricate string payloads over the network to hydrate your interface. Decoding these raw Next.js App Router streams is critical for understanding exactly what data is crossing the wire without relying on tedious server logs.

Our high-precision parser reconstructs the stream directly in your browser by accurately parsing hexadecimal row IDs and correctly handling the parsing quirks of binary-safe T chunks. It recursively maps definitions and properties, making it easy to trace $L lazy ref and Suspense boundaries back to their origin seamlessly.

Whether you are inspecting initial client renders, tracing emitModelChunk and emitImportChunk payloads, or debugging early resource hints, this offline tooling provides instant, visual clarity into your RSC responses, ensuring sensitive payloads never leave your browser.

100% Client-Side. Zero Server Logs. Your payload never leaves the browser.
Row type reference
(none)Model / JSON tree
IClient Component import
EError boundary
TLarge text (length-prefixed)
:HResource hint (no ID)
DComponent debug info
WConsole log (dev)
NTime origin (dev)
Decoded Output

Paste an RSC payload to begin

Copy from the Network tab in DevTools → select a request with text/x-component content-type