A 10.1 KB JSON test file

About this file

A 10.1 KB test file in JSON format, sized to exactly 10,292 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

10 KB sits below virtually every upload limit, which makes it the baseline "happy path" case. Confirm this file goes through first, then move up in size to probe where your limits actually bite.

It also fits inside the AWS Lambda asynchronous invocation payload cap (256 KB) and typical API JSON body limits. The size is convenient for CI fixtures and unit-test data you commit to a repository.

Getting a feel for this size

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

Treated as an array of records of roughly 180 bytes each including keys, this size holds about 57 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