Konverter
Date & Time Converter
The Datetime Converter translates between Unix timestamps, ISO 8601 date strings, and human-readable date and time representations across any time zone. It is an essential tool for developers working with APIs, databases, log files, and scheduling systems that store time as epoch seconds or milliseconds. All common date formats are supported, and the tool displays the result in multiple representations simultaneously.
What is a Unix timestamp?
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. Many programming languages, databases, and APIs use Unix timestamps as a universal, timezone-agnostic representation of a point in time. Millisecond-precision variants (common in JavaScript) multiply the second-based timestamp by 1000. Because timestamps are integers with no embedded timezone information, they are unambiguous and easy to compare, sort, and store.
How does the converter work?
Enter a Unix timestamp (seconds or milliseconds), an ISO 8601 date string (e.g. 2024-06-15T12:00:00Z), or a natural date string, and the tool parses the input to an internal Date object. It then formats the date in UTC, the selected local timezone, ISO 8601, RFC 2822, and relative human time (e.g. '3 days ago'). Timezone conversion uses the IANA timezone database embedded in modern browsers. You can also use 'Now' to insert the current timestamp and explore the resulting conversions.
Typical Use Cases
- Decoding Unix timestamps from API responses or database records to readable dates
- Generating the current epoch time for use in authentication headers or cache busters
- Converting scheduled event times between time zones for international deployments
- Debugging log files that store timestamps in epoch seconds
Step-by-step Guide
- Step 1: Enter a Unix timestamp, ISO 8601 date, or natural date string in the input field.
- Step 2: Select the target time zone from the dropdown if needed.
- Step 3: The tool instantly displays the date in all supported formats.
- Step 4: Click any result to copy it to your clipboard.
Example
Input
1718438400
Output
UTC: 2024-06-15 08:00:00 | ISO 8601: 2024-06-15T08:00:00Z | RFC 2822: Sat, 15 Jun 2024 08:00:00 +0000
Tips & Notes
- Watch out for millisecond vs. second timestamps – JavaScript's Date.now() returns milliseconds, while most Unix tools use seconds.
- ISO 8601 with a Z suffix (e.g. 2024-06-15T12:00:00Z) is always UTC – it is the safest format to exchange between systems.
- When storing timestamps in databases, prefer UTC to avoid ambiguity caused by daylight saving time transitions.
Frequently Asked Questions
What is the Unix epoch and why does it start in 1970?
The Unix epoch of January 1, 1970 was chosen by early Unix developers as a convenient reference point. It has no deeper significance; it simply predates most deployed Unix systems of the time.
What happens to Unix timestamps in 2038?
On 32-bit systems that store timestamps as signed 32-bit integers, the value overflows on January 19, 2038 (the Year 2038 problem). Modern 64-bit systems are not affected, and most platforms have already migrated to 64-bit time types.
Can I convert dates before 1970?
Yes. Negative Unix timestamps represent dates before January 1, 1970. For example, -86400 corresponds to December 31, 1969 at 00:00:00 UTC.
Date & Time Converter
Convert dates and times into various formats: ISO 8601, RFC 3339, Unix timestamp, Mongo ObjectID, Excel, and more.
Open Tool