JSON, Base64 and timestamps

You do not need a complicated editor for every small data task. Understanding the format often makes a confusing value easier to check.

JSON: structured data

JSON represents objects, arrays, strings, numbers, booleans and null. An example is {"name":"REMAX","active":true}. Use the JSON Formatter to indent it or validate syntax. Keys and strings need double quotes. Comments and trailing commas are not part of standard JSON.

Formatting uses JavaScript parsing. Very large integers can lose precision and duplicate object keys collapse to the last value. Preserve the original if exact numeric representations matter.

Base64: representation, not encryption

Base64 turns bytes into a restricted set of characters. It is commonly used to move data through text-based systems. The Base64 tool handles UTF-8 text, including international characters. Anyone can decode Base64; it does not protect secrets.

Unix timestamps: time as a number

A Unix timestamp expresses elapsed time from 1 January 1970 at 00:00:00 UTC. Many systems use seconds. JavaScript commonly uses milliseconds. In the Timestamp Converter, choose the unit explicitly and compare the UTC and local outputs.

Check the original specification

When working with an API, its documentation is the source of truth. Confirm whether a field uses seconds or milliseconds, whether a string is UTF-8, and whether a number must preserve exact precision. These small checks prevent errors that otherwise look like random broken data.