Quick reference
| Setting | Value / behavior |
|---|---|
| Input | {"ok":true} |
| Output | two-space indentation |
| Validation | syntax only |
Input and conversion rules
JSON is a data format with strict syntax. Property names and string values need double quotes; comments, trailing commas, undefined and NaN are not valid JSON. This tool parses the entire input and serializes the result with two-space indentation. A successful parse establishes syntax validity, not compliance with a business schema. It does not infer required properties, validate email fields or prove that an API request is semantically correct.
Important edge cases
Numbers are parsed with JavaScript number semantics. Integers above 9,007,199,254,740,991 can lose precision, and duplicate object keys keep the last parsed value. Represent long identifiers and exact decimal quantities as strings before using browser JSON transformations. Object property ordering is not an equality guarantee. If preserving the exact original byte representation is necessary, keep the source and use a specialized lossless parser.
A reliable workflow
First run the built-in example to understand the output structure. Replace it with a small representative sample from your own workflow and inspect every field that has special meaning: identifiers, currency, dates, missing values and nested collections. Then process the complete input, up to two million characters. The result can be copied or downloaded. Keep a separate original because conversion is not always reversible, especially when the target format cannot represent all the distinctions in the source.
Privacy and verification
The transformation runs in your browser using local JavaScript. There is no data-upload request and no account requirement. The page does not save your input to browser storage or place it in a shareable URL. Clearing the form removes the displayed input and result; it does not delete the original file or erase your operating system’s clipboard. Check the receiving program with a small import before loading a complete dataset. If the input is untrusted, retain formula protection where available and avoid running exported commands without review.
Avoid accidental data normalization
Formatting parses and serializes the document, so whitespace and numeric spelling can change even when the represented value appears the same. Do not use the formatted copy to verify a digital signature over the original JSON bytes.
Frequently asked questions
Are my values uploaded?
No. The conversion is performed in the page.
Is the conversion lossless?
Not always. Review the edge cases above, especially missing values, nested data and number precision.
Why did validation fail?
Check syntax, expected input shape and the specific row or parser error shown by the tool.
About this tool
Built and maintained by Mihai at Void Fabric. This page documents the behavior of the current implementation. Found an error or an unclear assumption? Send a reproducible example with sensitive values removed.
Reference: Void Fabric field notes · Testing and editorial policy