Conversions
Instant, private, and free
Unix Time Converter.
Convert UTC ISO-8601 timestamps to Unix seconds or milliseconds and back.
Set your values
Results update as you type.
Unix timestamps are interpreted in UTC. ISO output is normalized to an explicit Z suffix.
FAQs
How does the unix time converter work?
Convert UTC ISO-8601 timestamps to Unix seconds or milliseconds and back.
Use Cases
Debugging and Log Analysis
When analyzing logs or debugging software, you often encounter Unix timestamps. Convert them to human-readable UTC dates to understand when events occurred.
Example: Convert 1700000000 to see it as 2023-11-14T22:13:20Z.
Data Integration and API Development
When working with APIs that return Unix timestamps, you can quickly convert them to ISO-8601 for easier processing or display in your applications.
Example: Convert a millisecond timestamp like 1700000000000 to its UTC equivalent.
Frequently Asked Questions
- What is Unix time?
- Unix time (also known as Epoch time) is the number of seconds that have elapsed since January 1, 1970 (UTC), excluding leap seconds. It is widely used in computing for timestamping events.
- How do I convert a Unix timestamp to a readable date?
- Enter the Unix timestamp (in seconds or milliseconds) into the converter, and it will instantly display the corresponding UTC ISO-8601 date and time. The converter handles both units automatically.
- What is the difference between Unix seconds and milliseconds?
- Unix seconds count the number of seconds since the epoch, while Unix milliseconds count milliseconds (1/1000 of a second). Many systems use milliseconds for higher precision. This converter supports both.
Tips & Common Mistakes
Tips
- Always verify whether your timestamp is in seconds or milliseconds. A millisecond timestamp will be much larger (e.g., 1700000000000 vs 1700000000).
- Use the converter to check if a timestamp is in the past or future by comparing the resulting date to the current time.
- When converting ISO-8601 strings, ensure they are in UTC (with a 'Z' suffix) to avoid timezone confusion.
- For precise conversions, remember that Unix time does not account for leap seconds; the converter follows standard Unix conventions.
Common Mistakes to Avoid
- Confusing seconds and milliseconds: entering a millisecond timestamp as seconds will give a date far in the future (or past).
- Assuming the converter handles timezones: it only works with UTC, so local timezone offsets must be applied separately.
- Using an ISO-8601 string with a timezone offset (e.g., +02:00) without converting to UTC first, which can lead to incorrect Unix time.
Last updated: August 13, 2026