JSON Formatter JavaScript, Beyond JSON.stringify

JSON.stringify() is JavaScript's built-in JSON serializer, defined in the ECMA-262 specification since ES5 in 2009. When called with a space argument, it produces human-readable indented output. JSON.stringify(obj, null, 2) produces 2-space indented JSON. JSON.stringify(obj, null, "\t") produces tab-indented JSON. The second argument is a replacer: null includes all enumerable own properties, an array of strings includes only those named properties, and a function is called for each key-value pair and can transform or exclude individual values. This flexibility makes JSON.stringify suitable for both full serialization and filtered output.

The core limitation of JSON.stringify as a formatting tool is that it requires a JavaScript data structure as input, not a JSON string. If you already have a serialized JSON string from an API response, a log file, or a config file, you need JSON.parse() first: JSON.stringify(JSON.parse(jsonString), null, 2). This two-step sequence requires either a browser console, a Node.js REPL, or a dedicated script. For developers who use the console daily this is fast. For non-developers, for people on restricted machines, or for anyone who simply wants a faster path, this is unnecessary friction.

FixTools wraps this two-step operation in a web interface accessible from any browser. The input accepts a raw JSON string. Under the hood, the tool calls JSON.parse() to validate and deserialize the input, then JSON.stringify() with the chosen indent to produce the formatted output. The browser engine provides syntax highlighting on the rendered result, distinguishing strings, numbers, booleans, null, keys, and structural characters by colour. The final output is equivalent to what you would get running the same commands in the browser console, with better readability and a one-click copy button.

JavaScript has several JSON quirks that catch developers off-guard. BigInt values are not serialisable by JSON.stringify and throw a TypeError, even though they parse cleanly with JSON.parse if presented as plain integers; use a toJSON method on a wrapper class or stringify them to plain strings first. Object key order rules in V8 list integer-like keys numerically first regardless of insertion order, then string keys in insertion order, then Symbol keys (which JSON skips entirely). The U+2028 line separator and U+2029 paragraph separator are valid in JSON strings under modern specs but break older JavaScript parsers that use eval-based JSON handling, so libraries like jsesc escape them defensively. Knowing these quirks turns mysterious cross-runtime drift into a one-line fix at the serialisation boundary.

JSON.stringify also intersects with JavaScript module boundaries in ways that bite during debugging. When logging an object that was loaded from a different realm or worker, properties may not appear because property descriptors mark them non-enumerable; JSON.stringify only walks enumerable own properties. Class instances with private fields lose the private state entirely because private fields are not enumerable own properties of the instance. Proxy objects appear normal but JSON.stringify invokes their ownKeys and getOwnPropertyDescriptor traps, which may return different data than direct property access. For thorough debugging of complex objects, combine JSON.stringify with Object.getOwnPropertyNames or Reflect.ownKeys to enumerate every property name, including non-enumerable ones, and inspect each value explicitly before deciding whether the omission from stringified output is correct or a missing case.

TypeScript adds another layer worth understanding. The TypeScript compiler types JSON.parse as returning any, which defeats type safety unless you assert the result. The common pattern const data = JSON.parse(text) as MyType is unsafe because TypeScript performs no runtime check that the parsed value actually matches the type. Libraries like zod, io-ts, and superstruct add schema validation at the parse boundary, producing a typed value or a clear validation error. For greenfield TypeScript projects, adopt one of these libraries at every API and storage boundary; the small runtime cost prevents an entire category of bugs where TypeScript believes a value is one shape but the runtime value is another. FixTools complements this approach by giving you a quick way to inspect the actual JSON shape before defining the schema.