Unix timestamp converter
Turn 1757001600 into something a human can read — and back again.
Convert
Type in either box. The other follows.
That moment in every format
What a Unix timestamp is
A single number: the count of seconds since midnight UTC on 1 January 1970. That is it. No timezone, no format, no ambiguity about whether 03/04 means March or April.
That last point is why programmers use them. 1757001600 means exactly one moment,
everywhere on Earth. 04/09/2026 means two different days depending on which country you
are in.
Seconds or milliseconds?
This catches everybody. Unix timestamps are traditionally in seconds, but JavaScript, Java and many APIs use milliseconds — the same number with three more digits.
| Digits | Unit | Example |
|---|---|---|
| 10 | Seconds | 1757001600 → Sep 2026 |
| 13 | Milliseconds | 1757001600000 → Sep 2026 |
If your date comes out in the year 57000, you have read milliseconds as seconds. Divide by 1000. This tool detects which you pasted automatically.
The timezone confusion
A timestamp has no timezone. It is a moment. The timezone only decides how that moment is displayed.
The same timestamp is 9:30am in London and 2:00pm in Chennai. Neither is more correct. This is why storing timestamps rather than formatted dates saves so much pain — convert to local time only when you show it to a person.
The year 2038 problem
Systems that store the timestamp as a signed 32-bit integer run out of room on 19 January 2038, when the number exceeds 2,147,483,647. Modern 64-bit systems are fine for roughly 292 billion years. Old embedded hardware is the concern, not your website.
Common questions
Why is my date showing 1970?
The timestamp is 0 or empty. In practice this nearly always means a date field that was never filled in, and the system defaulted to the start of Unix time.
Why does the same timestamp show different times?
Because a timestamp is a moment, not a clock reading. Displaying it in a different timezone shows a different local time for the same instant. Change the timezone above to see it.
Does it handle daylight saving?
Yes. Converting a date back to a timestamp accounts for whether that zone was in daylight saving on that date, which is why the answer can shift by an hour across the changeover.
Which format should I store dates in?
A Unix timestamp or an ISO 8601 string in UTC. Both are unambiguous. Store one of those and format for the reader at the moment you display it.
Want this checked on your real account?
A tool can only work with the numbers you give it. If you want someone to look at what is actually happening in your ad account, the first conversation is free.
Book a free consultation