What is a Unix timestamp?
A Unix timestamp represents a moment in time as the number of seconds that have elapsed since 1 January 1970 at 00:00:00 UTC, known as the Unix epoch.
Unix time support
Unix Timestamp FAQs
Clear, technical explanations of how Unix timestamps work, why they use UTC, how to interpret seconds and milliseconds, and how Unix time is used in modern systems.
Why does Unix time start in 1970?
The Unix epoch was chosen during the development of early Unix operating systems as a practical and consistent reference point for time calculations.
Are Unix timestamps always in UTC?
Yes. Unix timestamps are always based on UTC and do not contain timezone, regional offset, or daylight saving information.
How are timezones handled with Unix time?
Timezones are applied only when converting a Unix timestamp into a human-readable date. The timestamp itself is timezone-independent.
What is the difference between seconds and milliseconds?
Unix timestamps are traditionally expressed in seconds. Some systems use milliseconds, which are simply the Unix timestamp multiplied by 1,000.
Why do some Unix timestamps have 13 digits?
A 13-digit Unix timestamp almost always represents milliseconds rather than seconds.
Does daylight saving time affect Unix timestamps?
No. Unix timestamps are not affected by daylight saving time. DST is only applied when converting to local time for display.
Why aren’t Unix timestamps human-readable?
Unix timestamps are optimised for machines. They allow efficient storage, comparison, and sorting without ambiguity caused by date formats or timezones.
How accurate are Unix timestamps?
Unix timestamps are accurate to the precision provided by the system generating them, commonly seconds or milliseconds.
Do Unix timestamps include leap seconds?
No. Unix time does not account for leap seconds. Time is treated as a continuous count of seconds since the epoch.
Why are Unix timestamps easy to sort?
Because Unix timestamps increase monotonically over time, they can be sorted numerically without additional context.
Why are Unix timestamps widely used in APIs?
Unix timestamps are compact, unambiguous, and easy to parse across programming languages and platforms.
Why do databases often store timestamps as Unix time?
Storing Unix timestamps avoids timezone ambiguity and simplifies indexing, comparison, and replication across systems.
What is the Year 2038 problem?
The Year 2038 problem affects systems using 32-bit signed integers to store Unix time, causing overflow on 19 January 2038.
Is the Year 2038 problem still relevant?
Most modern systems use 64-bit timestamps, making the Year 2038 problem largely irrelevant today.
Can Unix timestamps be negative?
Yes. Negative Unix timestamps represent dates before 1 January 1970.
Can Unix timestamps be more precise than milliseconds?
Some systems support microsecond or nanosecond precision, but these are extensions beyond traditional Unix time.
Does Velohost store Unix timestamp conversions?
No. Velohost performs Unix timestamp conversions live and does not store input values, results, or usage history.
Want to try it yourself? Convert Unix timestamps or Base-64 encoder & decoder or Decode JWTs
Need to convert Unix time?