Everything you need to know about JSON Tools — grouped by tool.
Yes. All processing happens in your browser. No data is ever sent to a server.
No. All tools are free and require no sign-up.
All modern browsers — Chrome, Firefox, Safari, and Edge.
Yes. The interface is fully responsive and works on phones and tablets.
Files up to 10MB are supported. Very large files may be slow in the browser.
JSON formatting (pretty-printing) adds indentation and line breaks to make JSON data human-readable.
Minifying removes all unnecessary whitespace to reduce file size — useful for production APIs and configs.
The validator parses your JSON and reports the exact position of any syntax errors like missing commas, brackets, or quotes.
The input must be a JSON array of objects, e.g. [{"key":"value"}, ...]. Nested objects are flattened using dot notation.
Standard comma-separated values with the first row as headers. Quoted fields and commas within quotes are handled correctly.
Yes. Drag & drop a file onto the drop zone, or click it to browse. Supports .json and .csv files up to 10MB.
Attributes become JSON keys prefixed with @ (e.g., @id). When converting back, keys starting with @ become XML attributes.
Yes. If an XML element appears multiple times, it becomes a JSON array automatically.
If your JSON has a single top-level key, that key becomes the root element. Otherwise, a <root> wrapper is added.
Array items are wrapped in repeated elements using the parent key name.
XML namespaces are preserved as-is in element names.
YAML (YAML Ain't Markup Language) is a human-readable data serialization format commonly used for configuration files (Docker, Kubernetes, CI/CD pipelines, etc.).
Yes. Nested JSON objects are converted to indented YAML blocks, and nested YAML is parsed back into JSON objects correctly.
Yes. JSON arrays become YAML lists with dash (-) notation, and YAML lists are converted back to JSON arrays.
Strings that could be misinterpreted as numbers, booleans, or contain special YAML characters are automatically quoted to preserve their original type.
Yes. Drag & drop or click to browse for .yaml, .yml, .json, or .txt files up to 10MB.
The input must be a JSON array of objects. Nested objects are flattened using dot notation (e.g., address.city).
No. The .xlsx file can be opened in Excel, Google Sheets, LibreOffice, or any spreadsheet app.
Excel supports up to ~1 million rows. For browser performance, we recommend keeping it under 50,000 rows.
The tool detects added keys (present only in right), removed keys (present only in left), and changed values (same key, different value).
Yes. Nested objects are compared recursively, and differences at any depth are highlighted.
Yes. Arrays are compared element-by-element. If lengths differ, extra elements are shown as added or removed.
Missing commas between values, unquoted keys, single quotes, trailing commas, smart/curly quotes, unmatched brackets and braces, and BOM characters.
In most cases, yes. For severely malformed input, the tool will apply as many fixes as possible and report if the result is still invalid.
No. The fixer only repairs structural issues. Your actual data values remain unchanged.
JSON Lint only validates. This tool goes further by actually repairing the broken JSON automatically.
Yes. Type in the search box to highlight matching keys and values. The match count is shown in real-time.
There's no depth limit. Deeply nested JSON is fully supported with expand/collapse at every level.
Yes. Use the "Expand All" and "Collapse All" buttons above the tree.