A 100 KB JSON test file

About this file

A 100 KB test file in JSON format, sized to exactly 102,450 bytes. Free to download with no signup, for verifying upload limits and file-handling behaviour.

The MD5, SHA-1 and SHA-256 values listed above are the real digests of this file. Recomputing them after download confirms the transfer was not corrupted, and they double as known-good expected values when testing a hashing library.

What this size means in practice

100 KB sits at the boundary between "trivially small" and "realistic payload". It is close to the total transfer weight of a single lean web page and is a common target size for performance-conscious images.

It clears the sub-1 MB caps many applications impose, but it is still small enough that a naive load-everything-into-memory implementation works fine — so it is not the right size for proving that streaming is necessary. Pair it with 10 MB or larger to see the difference.

Getting a feel for this size

On a 10 Mbps link the transfer takes roughly 82 ms, and about 8 ms at 100 Mbps. Base64-encoded it grows to roughly 133 KB.

Treated as an array of records of roughly 180 bytes each including keys, this size holds about 569 records — enough to judge whether you can hold them all in memory or should switch to a streaming parser. It is a rough estimate; the real figure depends heavily on your structure.

What to check for this format

JSON is likewise plain text and is UTF-8 by specification. Syntactic validity cannot be judged without parsing the whole document, so the larger the file, the more the cost of "read everything just to validate" matters.

• Whether large JSON goes through a streaming parser or is expanded into memory all at once
• Whether nesting depth is capped — deeply nested JSON can exhaust a parser's stack
• Whether large integers keep their precision — JavaScript numbers lose accuracy beyond 2^53