Lite³
Ranked 6 of 9 serialization formats by recommenders
Fast zero-copy access to indexed, JSON-like data that can be edited in place, though critics say its wire format is not JSON-compatible.
Fast zero-copy access to indexed, JSON-like data that can be edited in place, though critics say its wire format is not JSON-compatible.
20 people gave an opinion
- recommend it
- 14
- criticize it
- 6
- approval share
- 70%
Recommended in 3 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 14 people recommend itNeeds 10 or more, met.
- 2.3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 3 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Much faster than JSON parsing
“It is like sending a mini-database that can be queried at speeds thousands of times faster than any JSON library is able to parse.”
Comment from 13 Dec 2025 in “SQLite JSON at full index speed using generated columns” “you don't need to do any parsing, since the document itself is already indexed”
Comment from 12 Dec 2025 in “SQLite JSON at full index speed using generated columns” “is able to outperform simdjson by 120x in some benchmarks as a result”
Comment from 6 Jan 2026 in “I/O is no longer the bottleneck? (2022)” Promising for databases and tools
“I think databases is where this technology will eventually have the greatest potential”
Comment from 19 Dec 2025 in “Lite^3, a JSON-compatible zero-copy serialization format” “Building a jq around something like Lite^3 or JSONB is a very appealing thought.”
Comment from 13 Dec 2025 in “SQLite JSON at full index speed using generated columns” “Why not add this approach to postgres as a "JSONL3" type?”
Comment from 14 Dec 2025 in “SQLite JSON at full index speed using generated columns” Edits single values in place
“Lite^3 is a clever encoding for JSON data that is indexed as-encoded and is mutable in place.”
Comment from 13 Dec 2025 in “Lite^3, a JSON-compatible zero-copy serialization format” “Lite³ supports replacing of individual values where ONLY the changed value needs updating.”
Comment from 13 Dec 2025 in “SQLite JSON at full index speed using generated columns” Schemaless, supports 64-bit ints
“Supports 64 bit ints, raw byte datatype, zero-copy parsing, does not require schema”
Comment from 3 Dec 2025 in “Why I stopped using JSON for my APIs” “It's nice that it also works in a schemaless mode though.”
Comment from 6 Jan 2026 in “I/O is no longer the bottleneck? (2022)”
What people warn about
Each mark is one comment
Wire format not JSON-compatible
“the headline makes it sound like the wire format is json compatible which is not the case”
Comment from 19 Dec 2025 in “Lite^3, a JSON-compatible zero-copy serialization format” “This is not JSON-compatible.”
Comment from 19 Dec 2025 in “Lite^3, a JSON-compatible zero-copy serialization format” “JSON compatable is very different from convertable.”
Comment from 19 Dec 2025 in “Lite^3, a JSON-compatible zero-copy serialization format” Tied to hash function, key collisions
“It's a bit unfortunate that the wire format is tied to a specific hash function.”
Comment from 19 Dec 2025 in “Lite^3, a JSON-compatible zero-copy serialization format” “hash collision limitation for keys is the most questionable part of design”
Comment from 19 Dec 2025 in “Lite^3, a JSON-compatible zero-copy serialization format”
Other serialization formats people recommend
The four most recommended other serialization formats, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Protocol Buffers (protobuf) | 77 | 66 | 54% | 10 | 10 yrs3 owners | — |
| Serde | 22 | 16 | 58% | 10 | — | — |
| Cap'n Proto | 20 | 5 | 80% | 7 | — | Approved |
| Protobuf | 19 | 25 | 43% | 8 | — | — |
| Lite³This page | 14 | 6 | 70% | 3 | — | — |
What people said
30 of the 35 comments that mention it, newest first. Each links to the original comment.
“Lite has no images and no paywall, and generally loads very quickly.”
“your library DIDN'T EXIST before November 2025”
“Why not use a zero copy format so that serialization is free”
“It's nice that it also works in a schemaless mode though.”
“is able to outperform simdjson by 120x in some benchmarks as a result”
“That's really impressive.”
“I think databases is where this technology will eventually have the greatest potential”
“Lite³ is a very timely and forward-looking format”
“TRON/Lite³ is designed to blur the line between memory and serialization format.”
“JSON compatable is very different from convertable.”
“This is not JSON-compatible.”
“the headline makes it sound like the wire format is json compatible which is not the case”
“It's a bit unfortunate that the wire format is tied to a specific hash function.”
“hash collision limitation for keys is the most questionable part of design”
“I think that needs fixing before this can be widely used.”
“it's misleading to call it "serialization"”
“This needs more attention than it's getting.”
“Why not add this approach to postgres as a "JSONL3" type?”
“I would very much love that. Areas where I'd want to use Lite³”
“I agree that Lite³ is almost certainly better than JSONB on every score except compressibility”
“Lite³ supports replacing of individual values where ONLY the changed value needs updating.”
“The overridden space is never recovered, causing buffer size to grow indefinitely.”
“no you just don't get to move data freely”
“Lite^3 is a clever encoding for JSON data that is indexed as-encoded and is mutable in place.”
“Building a jq around something like Lite^3 or JSONB is a very appealing thought.”
“It is like sending a mini-database that can be queried at speeds thousands of times faster than any JSON library is able to parse.”
“That second point is huge”
“B-trees are more cache and space efficient”
“you don't need to do any parsing, since the document itself is already indexed”
“Supports 64 bit ints, raw byte datatype, zero-copy parsing, does not require schema”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.