JSON, CSV and developer tools online

Validate or convert JSON and CSV, inspect URLs, and generate UUIDs or hashes. Review types, precision, encodings and limits before integrating output.

Validate data and choose a representation

Each format has different rules. Keep a copy before converting and check the receiving program’s needs: data types, delimiter, encoding and structure.

Distinguish data, representations and identifiers before choosing an operation. JSON and CSV describe different structures, Base64 represents bytes as text, URL encoding handles component representation, UUID creates random references, and SHA-256 summarizes existing content. These functions are not interchangeable. Prepare a small sample matching the receiver’s expected format and test a round trip where appropriate. Knowing what is being transformed is essential to interpreting output instead of merely accepting a valid looking string.

Syntax validation does not establish an application schema. A JSON document can parse while containing incorrect types; a table can lose context around empty cells or nested data. Large numbers, repeated keys, leading zeros and delimiters deserve explicit review. Keep the original when an exchange depends on exact bytes. State encoding variant and character set for transformed strings, avoiding repeated conversions without knowing their current representation. Verify output in the destination with suitable fictitious data before integration. Tools process locally, but publishing a copied result still exposes its content; removing secrets from examples is a decision to make before sharing. A successful conversion should preserve the information the receiving workflow actually needs.

Read and validate JSON

Checks syntax and adds indentation. It does not validate a schema or retain every original numeric representation.

JSON formatter and validator →

Import a table

Headers become keys and cells remain text, including leading zeros.

CSV to JSON →

Export objects as a table

Includes all keys found. Nested data is stored as JSON inside a cell.

JSON to CSV →

Represent UTF-8 text in Base64

Uses standard Base64 with padding. This is a reversible encoding.

Base64 encoder and decoder →

Paste file contents into the corresponding field; CSV and JSON are not loaded through a file picker. Very large JSON numbers may lose precision and duplicate keys retain the last value.

Your files are processed here, on your device

We do not send your file or text contents to a processing server. No account is needed and there is no daily operation quota. Individual tools have size limits to protect your device’s memory.

A connection is needed to load the site and its resources. Hosting may receive technical visit data. Favorites store only tool identifiers in this browser.

How we handle your data →