JSON formatter and validator
Indent, minify or validate JSON syntax. Formatting reveals structure, but it cannot confirm whether field values or permissions are correct.
DEVELOPER TOOL COLLECTION
Use these tools for quick debugging, documentation examples and copied payloads. They are designed for lightweight tasks, not as a replacement for schema validation, source control or a secure development environment.
Indent, minify or validate JSON syntax. Formatting reveals structure, but it cannot confirm whether field values or permissions are correct.
Represent UTF-8 text as Base64 or inspect an encoded value. Base64 is reversible representation, not encryption.
Encode query values and decode copied parameters. Usually the parameter value should be encoded rather than the complete URL.
Test a JavaScript pattern, flags and capture groups against sample text before adding it to code or an automation.
Create a repeatable fingerprint for text. Hashing is one-way and differs from encoding; it does not prove who created a value.
Generate identifiers for local prototypes, documentation, fixtures and test records.
Convert seconds, milliseconds and dates to ISO, UTC and device-local formats.
Keep selected fields from a copied export. For large or irregular files, use a dedicated CSV parser and validate the source encoding.
Inspect a token header and payload locally. Decoding does not verify the signature or establish trust.
Break a URL into its origin, host, path, query parameters and fragment using the browser URL standard.
Escape metacharacters before inserting literal text into a JavaScript-style regular expression.
Convert common headings, paragraphs, lists, links and emphasis for small content migrations.
Encode markup-sensitive characters or inspect common named and numeric entity references.
Inspect and decode strict eight-bit UTF-8 byte groups for learning and debugging.
Remove API keys, tokens, customer records and private identifiers before sharing a debugging example. The text redactor can help with common patterns, but manual review is still required.
Avoid putting production secrets into any general-purpose web page. Use isolated, audited tooling and rotate a secret if it may have been exposed.
UTC and local time zones can place the same instant on different calendar dates.