ZapPad’s JSON formatter preserves written number tokens, and its CSV/TSV tools keep field values such as IDs with leading zeros. This is useful when a formatting pass must not silently change an identifier, decimal representation, quoted field or embedded newline. It formats and transforms text; it does not calculate arbitrary-precision results.
Structured data tools · local processing
Clean CSV and JSON on Mac without losing values
Currently offered to US customers only · Apple Silicon (M1+) · macOS 12+
The embedded player loads only when you choose to play it. YouTube processes playback data under its own privacy policy. Watch on YouTube ↗
Why generic JSON and CSV handling can change values
Many general-purpose data tools parse JSON numbers into a floating-point representation. A later serialization can round integers above JavaScript’s safe-integer range or normalize a written decimal. CSV programs may also infer types, turning an identifier such as 00142 into 142. These behaviors depend on the tool and import settings, so inspect the actual output.
ZapPad treats formatting as a textual transformation for its JSON tool: object-key order and written number tokens remain unchanged. CSV and TSV parsing respects quoting, embedded newlines and empty cells, and CSV-to-JSON preserves fields as strings.
Preview a JSON or CSV cleanup safely
- Open or paste the JSON, CSV or TSV into ZapPad.
- Choose the relevant formatter or structured-data tool.
- Inspect the preview, including large numeric IDs, decimal zeros, leading-zero fields and quoted commas.
- Apply only after checking the representation that your downstream system expects.
Structured comparison can ignore JSON object-key order or match CSV rows by a selected key column. Array order remains meaningful; duplicate keys are rejected when they make a comparison ambiguous. SQL formatting is separate and does not execute queries.
Keep the precision claim in scope
Preserving a written numeric token while formatting does not make arithmetic exact. If you need calculations, choose software with the numeric semantics required by your data. ZapPad’s CSV-to-JSON conversion stores fields as strings to protect identifiers; it does not infer a numeric type for every field.
The tools process data locally. Review the current input limits and behavior in the ZapPad manual. The example 9007199254740993 demonstrates preserving text during formatting, not doing arithmetic on that value.