Base64 Encoder / Decoder
Encode or decode Unicode text as Base64.
Check JSON syntax, add readable indentation or produce a compact version. Your input stays in your browser and is never sent to a formatting service.
Preparing your tool…
Formatting makes nested data readable; minifying removes unnecessary JSON whitespace. Neither operation validates a custom API schema or confirms that values have the right business meaning. Comments, unquoted names and trailing commas are invalid JSON rather than formatting preferences.
JavaScript parsing can lose precision for very large numeric identifiers and keeps the later occurrence of duplicate object names. Use strings or a suitable specialized parser when exact preservation matters. Keep the original payload and compare before replacing it with serialized output.
Practical check: Use {"id":"9007199254740993","active":true} when the data contract permits a string identifier requiring exact digits.
JSON needs double-quoted keys and strings. Comments and trailing commas are invalid. Parsing follows JavaScript JSON semantics: very large integers may lose precision and duplicate object keys retain the last value. Use a specialized parser for precision-sensitive data.
No. Comments are not part of standard JSON and produce a validation error.
JavaScript can lose precision for integers beyond Number.MAX_SAFE_INTEGER. Represent such identifiers as strings or use a specialized parser.
Find common JSON syntax mistakes, then format safely. Check duplicate keys, large numeric identifiers and the difference between validation and schema rules.