500 KB JSON sample file
A JSON file of exactly 512,000 bytes. It is a valid JavaScript Object Notation file, generated for this site and checked with an independent parser.
Download
sample-json-500kb.json
500 KB512,000 bytes
Download 500 KB JSONDirect download. No sign-up and no waiting.
- Type
- application/json
- SHA-256
2c55ffa41abe09eff30f0a53f61c9f38f2c1499f7338adbb3c7f7f19dea62801- Direct URL
https://sampletestfiles.com/downloads/json/sample-json-500kb.json
What is in this file
An object with a "records" array of 1,483 fictional customer objects, each with nested objects, an array and a nullable field. A final "padding" string brings the file to the exact size.
| Records | 1,483 |
|---|---|
| Root type | Object |
| Value types used | string, number, boolean, null, array, object |
| Encoding | UTF-8 (ASCII characters only) |
| Indentation | 2 spaces, one record per line |
How the file begins
The opening lines of sample-json-500kb.json, exactly as they appear in the file.
{
"generator": "SampleTestFiles",
"description": "Sample JSON file (500 KB) for testing",
"records": [
{"id":1,"uuid":"a6cf3b6b-cd57-4173-a942-a2339c75f449","name":{"first":"Ethan","last":"Zeller"},"email":"ethan.zeller1@example.com","active":true,"…
{"id":2,"uuid":"e86fd25c-cc5a-44ae-a8ee-4439d8d6c68e","name":{"first":"Elena","last":"Underhill"},"email":"elena.underhill2@example.net","active":…Preview
Shows the first 64 KB of the file.
Where 500 KB matters
A 512,000-byte file: larger than most API body limits, smaller than most upload limits. These are the default limits a file of this size is useful for testing:
| System | Limit | Note |
|---|---|---|
| Amazon DynamoDB items | 400 KB per item | 500 KB cannot be stored as a single item. |
| Express body parsers | 100 KB by default | Rejected unless the limit is raised. |
| nginx request body | 1 MB by default (client_max_body_size) | Accepted with room to spare. |
Use this file for
- Testing that APIs return 413 for oversized bodies
- Load-testing endpoints with large payloads
- Seeding front-end components with data
Testing notes for JSON
- Most parsers read numbers as 64-bit floats, so integers above 2^53 silently lose precision. Send large identifiers as strings.
- Parsing a large document with a DOM-style parser needs several times its size in memory. Use a streaming parser or JSON Lines for big data.
Technical details
| File name | sample-json-500kb.json |
|---|---|
| Format | JSON (JavaScript Object Notation) |
| Extension | .json |
| MIME type | application/json |
| Size | 512,000 bytes (500 KB) |
| Kind | Text |
| SHA-256 | 2c55ffa41abe09eff30f0a53f61c9f38f2c1499f7338adbb3c7f7f19dea62801 |
| Created | 2026-10-10 |
| Validation | Exact size, signature bytes and structure checked when the file was generated |
| Preview | Available on this page |
| Source | Generated for this site; not copied from elsewhere |
| Licence | Free to use, modify and redistribute (terms) |
| Category | Data |
Validated for expected format and integrity. As with any download, scan the file with your own security tools before opening it. How files are made and checked
Download from the command line and verify
Fetch the file with curl, then compare its checksum with the SHA-256 value above.
curl -o sample-json-500kb.json 'https://sampletestfiles.com/downloads/json/sample-json-500kb.json'
sha256sum sample-json-500kb.json # Linux
shasum -a 256 sample-json-500kb.json # macOSOn Windows, run Get-FileHash sample-json-500kb.json -Algorithm SHA256 in PowerShell. A matching value proves that the download is complete and unaltered.
Related files
Questions about this file
- Is this file exactly 500 KB?
- Yes. It is 512,000 bytes, which is 500 KB in the binary units that operating systems and server limits use (1 KB = 1,024 bytes).
- What is inside the 500 KB JSON file?
- An object with a "records" array of 1,483 fictional customer objects, each with nested objects, an array and a nullable field. A final "padding" string brings the file to the exact size.
- What is the structure of the sample JSON?
- An object with a "records" array. Each record has strings, numbers, a boolean, a nullable field, a nested object and an array, so most deserialiser paths are exercised.