Data · JSON
A 50 KB JSON file, on demand.
Exactly 51,200 bytes of a valid JSON document with a records array, built on your machine the moment you press the button.
51,200 bytes, exactly.
Every byte above the 60 bytes structural minimum goes into a trailing string field, so the document still parses, which is why this file still behaves like one a real user would send.
Unit convention
50 KB on this page means exactly 51,200 bytes, using the binary (MiB) convention some systems label "MB" for short. 1 MB in the strict decimal sense is 1,000,000 bytes; 1 MiB is 1,048,576 bytes — the readout above always shows the exact count either way.
Approximate size equivalents
Roughly 28 pages of typed text, 3.2 seconds of 128 kbps audio. These figures compare file size only — the generated file does not contain this text, audio or image content.
Accepted by
PHP default upload_max_filesize, Discord free attachment, AWS API Gateway payload — all publish a limit at or above this size, based on commonly cited figures that can vary by plan and change over time.
Other JSON sizes
This is where avatar and thumbnail uploaders usually cap, making it the standard size for testing the happy path of an image or document form.
Questions.
Is this 50 KB JSON file valid?
Yes. It is a valid JSON document with a records array. The extra bytes sit in a trailing string field, so the document still parses, so it opens in jq, browser devtools, Python's json module and Node's JSON.parse.
Does 50 KB mean 51,200 bytes?
On this page, yes — 50 KB uses the binary (MiB) convention, so the file is exactly 51,200 bytes. 1 MB in the strict decimal sense would be a different, smaller byte count. Upload validators may use either convention, so the exact byte count is always shown to remove any ambiguity.
What is a 50 KB file used for?
This is where avatar and thumbnail uploaders usually cap, making it the standard size for testing the happy path of an image or document form. For JSON specifically, the usual job is testing API payload limits and request body caps.
Where is the file downloaded from?
Nowhere. It is assembled in a Web Worker on your own device and handed to the browser as a Blob, so nothing is uploaded, fetched or stored.