JSON vs JSON with Comments: Which Should You Use?
Side-by-side comparison of JSON and JSON with Comments data formats — features, pros, cons, and conversion options.
JSON is best for Web APIs, configuration files, and structured data interchange. JSON with Comments is best for VS Code settings, TypeScript configs, and annotated JSON files.
Quick Verdict
- ✓ Native to JavaScript and web APIs
- ✓ Supports nested and typed data
- ✓ Universally supported across all languages
- ✗ No comments allowed
- ✓ Comments in JSON for documentation
- ✓ VS Code native config format
- ✓ Backwards compatible with JSON strippers
- ✗ Not a formal standard
Specs Comparison
Side-by-side technical comparison of JSON and JSON with Comments
| Feature | JSON | JSON with Comments |
|---|---|---|
| Category | Data | Data |
| Year Introduced | 2001 | 2015 |
| MIME Type | application/json | application/json |
| Extensions | .json | .jsonc |
| Plain Text | ✓ | ✓ |
| Typed | ✓ | ✓ |
| Nested | ✓ | ✓ |
| Human Readable | ✓ | ✓ |
| Schema Support | ✓ | ✗ |
| Streaming | ✗ | ✗ |
| Binary Efficient | ✗ | ✗ |
Pros & Cons
JSON
- ✓ Native to JavaScript and web APIs
- ✓ Supports nested and typed data
- ✓ Universally supported across all languages
- ✗ No comments allowed
- ✗ Verbose for large datasets
- ✗ No date or binary type
JSON with Comments
- ✓ Comments in JSON for documentation
- ✓ VS Code native config format
- ✓ Backwards compatible with JSON strippers
- ✗ Not a formal standard
- ✗ Requires pre-processing to parse as JSON
- ✗ Limited tool support outside VS Code
When to Use Each
Choose JSON when...
- You need files optimized for Web APIs, configuration files, and structured data interchange
- Native to JavaScript and web APIs
- Supports nested and typed data
Choose JSON with Comments when...
- You need files optimized for VS Code settings, TypeScript configs, and annotated JSON files
- Comments in JSON for documentation
- VS Code native config format
How to Convert
Convert between JSON and JSON with Comments for free on ChangeThisFile
Frequently Asked Questions
JSON is best for Web APIs, configuration files, and structured data interchange, while JSON with Comments is best for VS Code settings, TypeScript configs, and annotated JSON files. Both are data formats but they differ in compression, compatibility, and intended use cases.
It depends on your use case. JSON is better for Web APIs, configuration files, and structured data interchange. JSON with Comments is better for VS Code settings, TypeScript configs, and annotated JSON files. Consider your specific requirements when choosing between them.
Go to the JSON to JSON with Comments converter on ChangeThisFile. Upload your file and the conversion processes on the server, then auto-deletes. It's free with no signup required.
Yes. ChangeThisFile supports JSON with Comments to JSON conversion. Upload your file for server-side conversion — files are auto-deleted after processing.
File size varies depending on the content, compression method, and quality settings of each format. In general, lossy formats produce smaller files than lossless ones. Test with your specific files to compare actual sizes.
Yes, JSON supports schema support, but JSON with Comments does not. This may be important depending on your use case.
Both JSON and JSON with Comments are supported file formats that are free to use. You can convert between them for free on ChangeThisFile — server-side conversions are free with no signup required.
JSON with Comments is newer — it was introduced in 2015, while JSON dates back to 2001. Newer formats often offer better compression and features, but older formats tend to have wider compatibility.
Related Comparisons
Related Guides
Ready to convert?
Convert between JSON and JSON with Comments instantly — free, no signup required.
Start Converting