# Progressive JSON

DevFeed: [Progressive JSON](<https://devfeed.tech/articles/progressive-json-36190.md>)

Original publisher: [Read original article](<https://overreacted.io/progressive-json/>)

Published: 2025-05-31T00:00:00Z

Content type: article

Language: en

Sources: [Dan Abramov](<https://devfeed.tech/sources/dan-abramov.md>)

Topics: [JSON](<https://devfeed.tech/topics/json.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Parser](<https://devfeed.tech/topics/parser.md>), [client](<https://devfeed.tech/topics/client.md>), [Server](<https://devfeed.tech/topics/server.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [client](<https://devfeed.tech/tags/client.md>), [json](<https://devfeed.tech/tags/json.md>), [server](<https://devfeed.tech/tags/server.md>), [streaming](<https://devfeed.tech/tags/streaming.md>)

## AI overview

The article explains why conventional JSON transfer requires clients to wait for the complete payload before parsing and processing it. It examines streaming JSON parsers, noting that incomplete object trees create missing fields and uncertain completeness, which makes the resulting data difficult to use in application logic.

## Source excerpt

Why streaming isn't enough.