Unix Timestamps vs Calendar Dates: Units, UTC and Conversion

Identify an instant or a calendar date

A timestamp identifies a point on a time scale. A calendar date identifies a named day in a calendar. “October 5, 2026” does not by itself specify an exact UTC instant because the location and time of day are missing.

Use the Unix Timestamp Converter when you have a numerical timestamp or an explicit UTC date-time. Use a date calculator for a birthday, a named holiday or a date-only deadline. Converting a date-only value to midnight adds a convention; it does not recover a previously unknown event time.

Start with the epoch and the unit

The Unix epoch anchor is January 1, 1970 at 00:00 UTC. Seconds and milliseconds count from that same anchor at different scales. A millisecond is one thousandth of a second, so a numerical value needs an explicit unit before it can identify the intended instant.

JavaScript Date values use milliseconds. Many external records provide seconds. Multiplying seconds by 1,000 converts them to milliseconds; dividing milliseconds by 1,000 converts them to seconds. Do not infer the unit solely from the number of digits. Dates near the epoch, negative values and fractional values can defeat that shortcut.

Verify simple conversions first

The small examples below are useful checks before converting a large exported value. All displayed date-times are UTC.

A seconds value mistakenly read as milliseconds will appear much closer to the epoch. A milliseconds value mistakenly read as seconds may land in a distant year or outside the supported range. Check the provider’s field definition before deciding that the converter is wrong.

Keep UTC conversion separate from local display

The converter’s date-time input is explicitly UTC. It appends the UTC interpretation to the entered date and time before calculating the timestamp. The same instant can then be displayed in many zones without changing its numerical timestamp.

Use the Time Zone Converter to display that instant in another location. For example, 23:30 UTC on January 10 is January 11 in Tokyo. Preserve the full local date with the time. A clock time alone can hide the change of calendar date and lead to a meeting scheduled on the wrong day.

Handle negative and fractional values

A negative timestamp represents an instant before the epoch. It is not automatically an error. A fractional seconds value can represent part of a second, such as 1.5 seconds after the epoch. The browser Date model ultimately stores integer milliseconds.

When converting an exported file, inspect whether it uses whole seconds, fractional seconds or integer milliseconds. Keep the original unit and precision in the record. Do not promise more precision than the source contains. Adding extra decimal zeros to a whole-second timestamp does not recover the original event’s subsecond timing.

Understand the browser time model

This tool uses the ECMAScript Date time model. It does not represent leap seconds as a separate 23:59:60 value. Date-only arithmetic likewise uses an idealized Gregorian day structure rather than reconstructing every historical timekeeping adjustment.

That model is useful for ordinary application timestamps and calendar comparisons. A scientific timing system, a specialized time scale or a provider with its own epoch may need a different interpretation. Confirm the source format instead of treating every numeric time field as Unix seconds. A counter measured since another starting event needs that event’s anchor.

Avoid confusing durations with timestamps

The value 3,600 can mean an hour-long duration or a timestamp 3,600 seconds after the epoch. The number alone cannot tell you which. A duration measures a separation; a timestamp locates an instant.

To add two elapsed amounts, use Add Time Durations. To compare two actual date-times, use Hours Between Dates. For a calendar-month offset, use actual dates in the date calculator because months do not have one fixed duration in seconds.

Copy a conversion that another person can reproduce

Keep the entered number, its seconds-or-milliseconds unit, the UTC ISO output and the provider’s field name. If you display a local time as well, include its IANA zone identifier and its full date. These details make a mismatch much easier to diagnose.

The timestamp itself remains fixed when another year begins. A current-time clock changes because it samples a new instant, not because timestamps need an annual list. Time-zone displays depend on the runtime’s available rules, so distant future local offsets may change after governments revise their policies.

Frequently asked questions