New to Rust? Grab our free Rust for Beginners eBook Get it free →
Online Unix Timestamp Date Converter

When a scheduled event is written as a date and time, you may need to compare it with a system value. The online Unix timestamp converter changes between that count and a readable date and time.
I’ll show how to select the right unit and convert between timestamps and dates, then compare local time with UTC.
TL;DR
Use the converter to turn a Unix timestamp into a date, or a date and time into a timestamp. Select seconds or milliseconds to match the input.
- Unix time starts at 1970-01-01 00:00:00 UTC.
- JavaScript Date values use milliseconds, while many Unix timestamps use seconds.
- Compare UTC output when you need a stable reference across locations.
What Is a Unix Timestamp?
Unix time counts from 1970-01-01 at 00:00:00 UTC, the Unix epoch. For cross-system checks, compare UTC because local displays depend on device settings.
| Value format | Unit | Meaning for JavaScript Date |
|---|---|---|
| 1724822400 | Seconds | Multiply by 1,000 before passing as a Date timestamp |
| 1724822400000 | Milliseconds | Pass as the Date timestamp |
| -86400 | Seconds | One day before the epoch after unit conversion |
How to Convert a Unix Timestamp to a Date Step by Step
Choose the direction based on the value you have. For an API response or log entry, start with its epoch number. For a scheduled local event, enter the date and time.
Step 1: Choose the timestamp unit
Select the unit documented by the value’s source. A wrong choice can move the result far from the intended date.
Step 2: Convert the timestamp to a date
Enter the number and use the timestamp conversion action. Compare the UTC date with the event time documented by the source.
For example, 1,724,822,400 seconds and 1,724,822,400,000 milliseconds represent the same instant.
Step 3: Convert a date and time to a timestamp
Enter the date and time in the date-time field, confirm the selected unit, and use the date conversion action. The result is an epoch value you can compare with the source system or copy into a query.
A date-time entered without an offset is treated as local time by JavaScript’s date parsing rules. Confirm the browser’s time zone before converting if the source date uses another location.
Step 4: Compare local time with UTC
Use the ISO value ending in Z as the UTC reference. The local result uses the device’s time-zone rules for that date, including daylight-saving changes where they apply.
Common Errors and Edge Cases with Unix Timestamps
Conversion can fail when a value is outside the date implementation’s range or the date-time uses the wrong local zone. Check the supported range and input context because a valid-looking number can still produce an unintended date.
| Case | What you may see | What to check |
|---|---|---|
| Seconds read as milliseconds | A date close to January 1970 | Choose seconds, or multiply seconds by 1,000 for a millisecond-based API |
| Milliseconds read as seconds | A date far in the future or invalid output | Choose milliseconds and do not infer solely from length |
| Negative value | A date before January 1, 1970 | Confirm the sign and source convention |
| Fractional seconds | Subsecond precision may be rounded or truncated by a tool | Check the source’s precision and the converter’s displayed precision |
| Date outside supported range | An invalid date result | Check the number and target platform’s date range |
| Local time differs from UTC | Different calendar date or clock time | Compare the UTC value and the applicable local offset |
JavaScript Date stores the underlying instant in milliseconds. A date-time string with Z marks UTC, while one without an offset is treated as local time by JavaScript’s date parsing rules.
A signed 32-bit counter storing seconds reaches its upper limit on January 19, 2038 at 03:14:07 UTC, the Year 2038 problem. This limit applies only to systems using that representation.
Unix time also does not model leap seconds as a distinct sequence of timestamp values in the way a civil-time clock displays them. Routine conversion can use the ordinary timestamp, while scientific or synchronization work should use a time scale designed for that precision.
Conclusion: Match the Unit Before Converting
A timestamp names an instant. Compare its UTC and local displays when the event’s date matters.
For JavaScript date construction and formatting, see the CodeForGeek JavaScript Date guide and the Temporal API guide. The MDN Date reference documents the millisecond value and local versus UTC methods.
FAQ
These answers cover the unit, epoch and time-zone questions that commonly come up during conversion.
Is a Unix timestamp in seconds or milliseconds?
It depends on the source. Many Unix timestamps use seconds, while JavaScript Date values use milliseconds. Check the source documentation and select the matching unit.
Does a Unix timestamp include a time zone?
No. It identifies an instant relative to the Unix epoch. A time zone is applied when displaying that instant as a local date and time.
Can a Unix timestamp be negative?
Yes. A negative value represents an instant before 1970-01-01 00:00:00 UTC, provided the converter and target date implementation support that value.




