What are sample files used for?

Sample files are used by developers, testers, and designers to test file upload functionality, validate parsers, prototype applications, and verify format support. They provide well-formed examples of real file formats without sensitive data.

Are the sample files free to download?

Yes, all sample files on File Examples are completely free to download. No registration, no limits, and no hidden fees. You can use them for testing, development, and educational purposes.

What file formats are available?

File Examples offers 1000+ sample files in 700+ formats across 50 categories including documents, images, audio, video, code, scripting, AI/ML, blockchain, gaming, firmware, security, science, IoT, DevOps, medical, accessibility, automation, education, legal, API, localization, and many more.

Can I use these files for testing my application?

Absolutely. All files are well-formed, valid examples designed specifically for testing. They contain proper headers, metadata, and realistic content structures — ideal for automated testing, CI/CD pipelines, and development workflows.

How do I download a sample file?

Browse categories or search for a specific format, click on the file you need, and hit the Download button. The file downloads instantly — no signup or email required.

JSON.json · Invalid

Invalid JSON File

Download a free invalid JSON file designed to test how your application handles malformed JSON input. This file contains intentional JSON syntax errors that are commonly encountered in real-world development — trailing commas, unquoted keys, single-quoted strings, and inline comments. Use it to verify that your JSON parser fails gracefully, returns meaningful error messages, and does not crash or expose sensitive information.

Download Invalid File Download Valid Counterpart

What Is Broken

This file contains multiple intentional JSON specification violations: trailing commas after the last element in arrays and objects, single-quoted strings instead of required double quotes, JavaScript-style comments (// and /* */), unquoted property keys, NaN and Infinity literal values, and hexadecimal number notation. Each of these is valid in JavaScript but violates the JSON specification (RFC 8259).

Broken Example

{
  // This is an invalid JSON file
  'name': 'Alice',
  "age": 30,
  "tags": ["developer", "writer",],
  "score": NaN,
  "hex": 0xFF,
}

Why It Matters

Malformed JSON is one of the most common causes of API failures, data pipeline crashes, and frontend rendering bugs. Testing with intentionally broken JSON ensures your application provides clear error messages, maintains data integrity, and does not expose stack traces or internal details to end users.

Expected Parser / Validator Behavior

JSON.parse() should throw SyntaxError with a descriptive message and position indicator. Python json.loads() should raise json.decoder.JSONDecodeError. Java Jackson should throw JsonParseException. Well-behaved applications should return a 400 Bad Request with a user-friendly error message.

Related Invalid Files

Invalid Json File Trailing Comma Invalid Json File Missing Brace Malformed Xml File

Related Validators & Tools

Json Validator

Valid Sample Files

Sample Json File 1kb Sample Api Response Json

Frequently Asked Questions

What makes this JSON invalid?

It violates RFC 8259 with trailing commas, single quotes, comments, NaN values, and hex notation — all valid in JavaScript but illegal in JSON.

How should my app handle invalid JSON?

Catch the parse error, log it for debugging, and return a clear 400 response to the client with a description of what went wrong. Never expose raw stack traces.

Is there a valid version available?

Yes. Download the valid counterpart file alongside the invalid one to test both success and failure paths.