How to use this calculator
The Unix timestamp converter translates Unix seconds or milliseconds into a readable date and time, or converts a local timestamp back to an epoch value. Select the units explicitly before entering a numeric timestamp. Seconds and milliseconds differ by a factor of 1,000, so using the wrong interpretation can move the result far from the intended date.
Choose a display zone to read an instant in a familiar location. In the reverse direction, enter the local date and time with its location so the calculator can identify the instant. Unix time is an instant-based representation; the readable date changes with the display zone while the underlying timestamp remains the same.
Formula and calculation method
Unix seconds = elapsed POSIX seconds since 1970-01-01T00:00:00Z. Unix milliseconds = Unix seconds × 1,000.
Interpret the numeric unit explicitly
A Unix value has no built-in label telling the parser whether it is in seconds or milliseconds. Choose the same unit as the source system. Modern timestamps often have different digit counts in the two formats, but explicit selection is more reliable than a digit-count guess, especially for historical values near zero.
Convert local readings through a zone
When starting with a readable local timestamp, the location determines its offset on that date. The calculator resolves it to an instant before calculating the epoch value. Repeated or missing local times need a policy, just as they do in the time-zone converter. A bare local reading cannot always identify one Unix value.
Worked examples
The Unix epoch
Unix seconds 0 represents January 1, 1970 at 00:00:00 UTC. Choosing another display zone can show a local date in December 1969 without changing the numeric instant. This is expected: the epoch is defined using UTC, while a local representation applies the chosen location’s offset.
One second before the epoch
Unix seconds -1 represents December 31, 1969 at 23:59:59 UTC. Negative timestamps describe instants before the epoch rather than invalid time by definition. A particular application may impose a narrower range, so confirm that the receiving system supports the historical date you intend to use.
Seconds compared with milliseconds
Unix seconds 1,000 represents 00:16:40 UTC on January 1, 1970. Unix milliseconds 1,000 represents 00:00:01 UTC that day. The same digits produce very different instants because their unit differs. Preserve the units in filenames, column names, or API field descriptions when exchanging values.
Edge cases and practical checks
Precision and supported dates
The converter rejects unsafe numeric values and limits calendar output to 1900–2100. Use the selected seconds or milliseconds unit rather than entering a long value and expecting automatic correction. When exchanging timestamps with a spreadsheet, make sure it preserves the complete integer instead of displaying or exporting a rounded scientific-notation value.
Leap seconds and local ambiguity
Leap-second readings such as 23:59:60 are unsupported. The calculator follows the time representation used by its browser date-time tools rather than a leap-second-aware scientific timescale. During a backward local clock change, two Unix instants can share the same displayed local reading; the offset or occurrence distinguishes them.
Frequently asked questions
Are Unix timestamps always in UTC?
The epoch reference is UTC and the numeric timestamp identifies an instant. A timestamp itself does not carry a preferred display zone. You can show that instant in UTC, New York, Tokyo, or another location without changing the value it represents.
How do I tell seconds from milliseconds?
Check the source system’s documentation or field label. Milliseconds are 1,000 times the seconds value for the same instant. Digit count can be a clue for recent dates but is not a universal rule, so the converter requires an explicit unit selection.
Can a Unix timestamp be negative?
Yes. Negative values represent instants before January 1, 1970 at 00:00 UTC. This calculator supports dates within its stated 1900–2100 range. Other databases and APIs can impose different limits, so verify compatibility before transferring an older timestamp.
Why is the date different in another zone?
The same instant can be represented on different local calendar dates near midnight. The timestamp remains unchanged while the formatted date and clock reading follow the destination zone. Include an offset or zone when sending a human-readable version of the result.
Does it handle leap seconds?
No. Leap-second input is not supported, and the output follows the ordinary Unix-style time model used here. Tasks requiring precise astronomical or scientific timescales need a dedicated system that explicitly models leap seconds and the relevant time standard.
Can I convert many timestamps at once?
Use Batch Time Calculator for a column or file. Select Unix seconds or milliseconds to match the source and inspect row-level errors before exporting. Preserve the original units and avoid mixing them in a single column without normalizing the data first.
Published by TrueHour. Calculation methodology and sources · Report a correction · Time and date guides