Identify the source unit
Confirm whether the value is Unix seconds, Unix milliseconds, or an ISO string before converting anything.
Check Unix seconds, milliseconds, ISO strings, UTC offsets, and local time side by side before shipping a broken date.
Timestamp bugs are rarely about formatting alone. They usually come from unit mismatches, implicit local time, or assumptions about daylight saving behavior. This page is structured for those search intents while the converter remains interactive.
Confirm whether the value is Unix seconds, Unix milliseconds, or an ISO string before converting anything.
Always review both so it is obvious whether the bug is in storage, display, or timezone math.
Check logs, database fields, and API docs to ensure every step in the chain uses the same convention.
Check whether a 10-digit value is seconds or milliseconds.
Why are my dates off by exactly 1000x?
The most common cause is treating Unix seconds as milliseconds, or the reverse.
Store UTC whenever possible and convert for display at the edge. It keeps logs, APIs, and alerts consistent.
Show UTC and local representations together, then reproduce the timestamp around the transition boundary.
Related tools