JSON Formatter
Format, minify and validate JSON without changing large integers, number notation, key order or string escapes. Import files and locate syntax errors.
Seconds and milliseconds · Time zones · Date conversion
Inspect log entries or API time fields and copy UTC, ISO 8601 or local results separately. The live clock stays independent of your edited value.
Edit either the timestamp or the date to convert instantly. Seconds and milliseconds can be detected automatically or selected explicitly. Choose a time zone, or enter an ISO date with Z or a UTC offset. The unit selector changes how the input is interpreted; it does not rewrite the number.
Copy seconds, milliseconds, the selected zone’s time, ISO 8601, or UTC separately. The live clock does not overwrite your input; use “Use current time” to fill it. Invalid dates and sub-millisecond precision are rejected. Skipped local times are flagged, and repeated times require a choice.
All calculations run in your browser. Inputs are not uploaded.
No. Auto mode uses magnitude to recognize common values. Early millisecond timestamps and far-future or distant historical seconds can be ambiguous; choose the unit explicitly. One second is 1,000 milliseconds.
No. An explicit offset identifies the instant; the selected zone controls its local display. For example, 2026-09-10T08:00:00+08:00 is 2026-09-10T00:00:00Z.
Clock changes can skip or repeat local times. A skipped time is rejected; for a repeated time, choose the intended UTC occurrence. Supplying a correct explicit offset avoids that ambiguity.
Precision is one millisecond: choose seconds for up to three meaningful decimal places, or whole milliseconds. Pausing freezes the live clock only; editing conversion values does not stop or overwrite that clock.
Comments
0