A JSON number is a sequence of characters governed by a grammar. JavaScript Number is a binary floating-point value with a limited exact integer range. Those ideas are related but not identical. When a formatter parses a long identifier into Number and serializes it again, digits can change even though the input was valid JSON. JSONClear avoids that conversion: it validates the number token, stores its original spelling and changes only structural whitespace around it.

The safe-integer boundary is not a JSON limit

The familiar boundary 9,007,199,254,740,991 belongs to exact integer representation in JavaScript Number, not to the JSON grammar. A producer may legally emit a longer integer token. A consumer may still have its own range or schema limit, so syntax validity never guarantees business acceptance. Lossless formatting has a narrower promise: the formatter will not introduce a numeric change while adding indentation or removing whitespace. The destination system remains responsible for interpreting the token.

Decimal and exponent spelling can carry operational evidence

Tokens `1.2300`, `1.23`, `123e-2` and `1.23E+0` may describe the same mathematical quantity, yet they are not the same source text. Trailing zeroes can reflect an upstream scale, and exponent case or sign may help compare logs. JSONClear preserves each spelling. Pretty printing inserts a space after a colon and line breaks between members; minification removes permitted JSON whitespace outside strings. Neither action normalizes a numeric token or claims that two spellings are semantically equal.

Lossless formatting is not schema validation

Preserving the token proves only that JSONClear did not rewrite it. It does not prove that an API expects the field, accepts its range, treats it as an identifier or stores it without loss. Duplicate object names also remain in place because strict JSON syntax does not require uniqueness, while consumers differ in behavior. Compare the output, read the duplicate-name count and validate the payload against the destination contract before replacing an authoritative copy.