free_tool
Unix Timestamp Converter
A number like 1719705600 is just seconds since 1970, but reading it by eye is a guess. Paste a timestamp and get the date back in UTC, your local zone and plain "3 hours ago" relative time, or go the other way and turn a date into the epoch value your code expects. It runs in your browser.
Current Unix time
Loading…
Auto-detected as seconds from 10 digits.
Pick a local date and time, or paste an ISO 8601 string into the text field.
Timestamps look simple until a units mismatch or a naive local time quietly corrupts your data. I get time handling right across your stack, from storage to rendering, so dates stop drifting.
Fix your time handling: book a callAuto-detects seconds vs milliseconds by digit count, with a manual toggle when you need it. Epoch values are zone-free instants; the human strings show what that instant looks like in UTC and in your browser's local time.
seconds_or_milliseconds
The off-by-1000 bug, caught before it ships
Half the timestamp pain in a codebase is one system speaking seconds and another speaking milliseconds. Feed a seconds value into a milliseconds API and your event lands in 1970; feed milliseconds into a seconds parser and it lands fifty thousand years out. Seeing the decoded date next to the raw number makes that mismatch obvious instantly.
Time zones are the other trap. An epoch value has no zone, it is a single instant, but the moment you render it the zone decides what day it is. This tool shows UTC and your local time side by side so you can tell which one a log line, a token claim or a database row actually meant.
faq
Questions & answers
- What is a Unix timestamp?
- A Unix timestamp, or epoch time, is the number of seconds that have elapsed since midnight UTC on 1 January 1970. It is a single integer with no timezone attached, which makes it a compact, unambiguous way to store and compare moments in time across systems.
- How can I tell if a timestamp is in seconds or milliseconds?
- By its length: a seconds timestamp for a current date is 10 digits, while a milliseconds timestamp is 13. The tool auto-detects which one you pasted based on magnitude and converts accordingly, so you do not have to divide or multiply by 1000 yourself.
- How do I convert epoch time to a human-readable date?
- Paste the timestamp and the tool shows it as an ISO 8601 string in UTC, as your local time, and as a relative time like 3 hours ago. You can also go the other way and enter a date to get the seconds and milliseconds values back.
- What timezone is the converted time in?
- It shows two: the canonical ISO 8601 value in UTC, and the same moment rendered in your browser's local timezone. The underlying timestamp itself carries no timezone, so UTC is the reference and your local time is computed from your machine's settings.
- What is the year 2038 problem and is conversion done in my browser?
- The year 2038 problem is that a signed 32-bit seconds counter overflows on 19 January 2038, after which it wraps to a negative number; modern systems use 64-bit timestamps and are unaffected. All conversion here runs in your browser, including the live current-epoch clock, so nothing you enter is sent to a server.
Time zones and timestamps tripping up your data?
Mismatched units, naive timestamps, logs in the wrong zone, dates that drift by an hour twice a year. I'll get time handling right across your stack. Book a call, or leave your email.
Prefer proof first? See how this plays out in real case studies →