Choose the operation that matches your data: readable JSON, a precise instant in time, a correctly encoded URL value or a table-shaped export. These utilities work locally, without sending your input to a debugging service.
What do you want to do?
Inspect a JSON payload
Use the JSON formatter to validate syntax and turn compact JSON into a readable structure, or minify it for copying. If the source is a spreadsheet export instead, convert the CSV to JSON first rather than manually assembling object syntax.
Use the Unix timestamp converter for seconds or milliseconds since the Unix epoch, inspect the date in your chosen time zone, or convert UTC date fields back to a timestamp. Check the unit before comparing values from different systems.
Use the URL encoder and decoder for individual URL components or form values, or inspect an HTTP or HTTPS URL locally. Choose the matching mode: spaces and plus signs do not have the same meaning in every encoding context.
A syntax check cannot confirm required fields, business rules or a server's schema. Review the receiving application's requirements before importing formatted or converted data.
Encoding is not encryption
URL encoding makes characters safe for a particular URL context; it does not hide secrets. Do not put passwords or private tokens into links, even when their characters are encoded.
Your tool inputs stay in your browser. Optional analytics track these page visits only, not your files or text. Privacy.
Optional analytics help us see which tools are used. No tool inputs are sent. Privacy