Is JSON safe to parse from untrusted sources?

JSON itself cannot execute code like JavaScript eval() can, making it safer than older exchange formats. However, deeply nested JSON can exhaust memory (a "billion laughs" variant) — use streaming parsers and limit recursion depth when processing untrusted input.

JSON vs TSV — Differences, File Size & When to Use Each

Q: What is a JSON file?

JSON (JavaScript Object Notation) is a lightweight text format for data exchange, popularized by Douglas Crockford around 2001. JSON represents nested objects, arrays, strings, numbers, booleans, and null values in a syntax derived from JavaScript. It is the default data format for modern web APIs.

Q: How do I open a JSON file?

JSON files are plain text — open them in any text editor (Notepad, VS Code, Sublime Text, TextEdit). For formatted reading, use JSON-aware editors (VS Code auto-indents) or online viewers like jsonformatter.org. Every web browser displays JSON directly if you open the file locally.

Q: How do I convert JSON to CSV?

Use KaijuConverter&#039;s JSON-to-CSV converter for nested data flattened into a tabular format. For simple flat JSON (array of objects), command-line tools like jq + csvkit give more control. Python&#039;s pandas and JavaScript&#039;s PapaParse also handle the conversion in one line of code.

Q: JSON vs YAML: which should I use?

JSON for machine-to-machine data exchange (APIs, config) — strict spec, fast parsers in every language. YAML for human-edited config files — supports comments, multi-line strings, and references. Kubernetes, Docker Compose, and GitHub Actions use YAML; REST APIs overwhelmingly use JSON.

Q: Why can&#039;t I add comments to JSON?

JSON&#039;s strict specification disallows comments to keep parsers simple and unambiguous. Workarounds include JSONC (JSON with Comments, used by VS Code config), JSON5 (relaxed syntax with comments), or a convention of adding a &quot;comment&quot; or &quot;_doc&quot; field in your data.

JSON vs TSV

Ein detaillierter Vergleich von JSON Data und TSV (Tab-Separated Values) — Dateigröße, Qualität, Kompatibilität und welches je nach Workflow zu wählen ist.

TSV → JSON umwandeln

JSON

JSON Data

Documents & Text

JSON (JavaScript Object Notation) is a lightweight data interchange format that is human-readable and easy for machines to parse and generate. It has become the dominant format for web APIs, configuration files, and structured data exchange.

Über JSON-Dateien

TSV

TSV (Tab-Separated Values)

Spreadsheets & Data

TSV uses tabs instead of commas to separate values in tabular data. It avoids quoting issues common in CSV when data contains commas, making it popular for scientific and linguistic data.

Über TSV-Dateien

Vorteilsvergleich

JSON Vorteile

Dead-simple — you can memorize the entire grammar on one page.
Native parsers in every programming language.
Human-readable and easy to debug.
Compact — much smaller than equivalent XML.
Frozen spec — a JSON parser written in 2010 still handles new JSON files from 2026.

TSV Vorteile

No quoting needed — tabs in data are astronomically rare.
Simpler parser than CSV.
Preferred by databases, bioinformatics, and scientific pipelines.
Opens cleanly in every spreadsheet app.
Plain text, grep-friendly, diffable.

Einschränkungen

JSON Einschränkungen

No comments allowed — config files feel verbose.
No trailing commas — a constant source of parse errors.
No native date, decimal, or binary types — everything is strings or numbers.
Easily bloated by repeated keys; large payloads compress poorly vs binary alternatives.
Streaming is awkward — JSON wants to be parsed whole.

TSV Einschränkungen

Tabs can be invisibly replaced with spaces by text editors.
Carriage returns inside fields require escaping conventions.
Less ubiquitous than CSV in business/consumer workflows.
No metadata, no schema, no type information.

Technische Spezifikationen

Spezifikation	JSON	TSV
MIME type	application/json	text/tab-separated-values
Extension	.json	—
Standard	ECMA-404, RFC 8259	IANA registration (1993), IETF RFC unofficial
Encoding	UTF-8, UTF-16, or UTF-32	UTF-8 (convention)
Allowed types	object, array, string, number, boolean, null	—
Extensions	—	.tsv, .tab
Delimiter	—	Tab (ASCII 9)

Typische Dateigrößen

JSON

Small config < 1 KB
REST API payload 1-100 KB
Database export 10 MB - 100 GB

TSV

Small data export 1-50 KB
Typical database dump 1-500 MB
Genome annotation file 100 MB - 50 GB

Bereit zum Umwandeln?

Wandle zwischen JSON und TSV online um, kostenlos und ohne Installation. Verschlüsselter Upload, automatische Löschung in 60 Minuten.

TSV zu JSON umwandeln

Häufig gestellte Fragen

JSON (JavaScript Object Notation) is a lightweight text format for data exchange, popularized by Douglas Crockford around 2001. JSON represents nested objects, arrays, strings, numbers, booleans, and null values in a syntax derived from JavaScript. It is the default data format for modern web APIs.

JSON files are plain text — open them in any text editor (Notepad, VS Code, Sublime Text, TextEdit). For formatted reading, use JSON-aware editors (VS Code auto-indents) or online viewers like jsonformatter.org. Every web browser displays JSON directly if you open the file locally.

Use KaijuConverter's JSON-to-CSV converter for nested data flattened into a tabular format. For simple flat JSON (array of objects), command-line tools like jq + csvkit give more control. Python's pandas and JavaScript's PapaParse also handle the conversion in one line of code.

JSON for machine-to-machine data exchange (APIs, config) — strict spec, fast parsers in every language. YAML for human-edited config files — supports comments, multi-line strings, and references. Kubernetes, Docker Compose, and GitHub Actions use YAML; REST APIs overwhelmingly use JSON.

JSON's strict specification disallows comments to keep parsers simple and unambiguous. Workarounds include JSONC (JSON with Comments, used by VS Code config), JSON5 (relaxed syntax with comments), or a convention of adding a "comment" or "_doc" field in your data.

JSON itself cannot execute code like JavaScript eval() can, making it safer than older exchange formats. However, deeply nested JSON can exhaust memory (a "billion laughs" variant) — use streaming parsers and limit recursion depth when processing untrusted input.