Unix Timestamp Converter: A Practical Guide
You're reading a server log and hit a line like ban_issued_at: 1762819200. When was that? Last week? 1997? Unix timestamps are how computers actually store time, and being able to read them fluently is a genuinely useful skill for developers, modders, and anyone who digs through log files.
What Is a Unix Timestamp?
A Unix timestamp counts the seconds since January 1, 1970, 00:00:00 UTC — a moment called "the epoch." Right now the counter is somewhere past 1.7 billion. It sounds arbitrary, but the design is brilliant: a single integer represents a moment in time with no timezones, no daylight saving chaos, no formatting ambiguity. Add 3600 and it's exactly one hour later, anywhere on Earth.
That's why APIs return expires_at: 1762905600, databases store created_at as an integer, and game servers log events in epoch time — computers think in these numbers.
Seconds vs Milliseconds: The Classic Gotcha
Traditional Unix time counts seconds. But JavaScript's Date.now(), Java, and many modern APIs count milliseconds — the same number with three extra zeros. Mix them up and your date lands in the year 57816 or the year 1970.
The quick rule: a current timestamp in seconds has 10 digits (like 1762819200); in milliseconds it has 13 (1762819200000). The timestamp converter on this site auto-detects the unit — 10 digits or fewer is treated as seconds, anything longer as milliseconds — so you don't have to think about it.
Converting Both Directions
Timestamp → Date
- Open the converter and paste the number.
- The date appears as you type — both the UTC ISO time and your local timezone, so there's never ambiguity about which you're reading.
- Click Now whenever you just need the current epoch value for a test.
Date → Timestamp
Need the timestamp for "next Friday at 8pm"? The lower section takes any date and time from a picker and returns both the seconds and milliseconds forms. Handy for scheduling scripts, setting expiry times, or seeding test data.
Everything runs locally in your browser — which is nice when the timestamp came from a production log you shouldn't paste into random websites.
Real Scenarios
- Debug auth issues: compare a token's
expagainst the current epoch time to see if it's really expired. - Read game logs: convert event times to figure out what happened during a crash.
- API testing: generate "tomorrow at noon" as a timestamp for a request body.
- Database forensics: find out when that row was actually created.
Fun Bonus: The Year 2038 Problem
Older systems store Unix time in a 32-bit signed integer, which maxes out at 2,147,483,647 — that's January 19, 2038, 03:14:07 UTC. One second later, those systems think it's 1901. Modern 64-bit systems are immune (they'll overflow in about 292 billion years), and this converter handles dates far beyond 2038 without breaking a sweat.
Related Guides
Frequently Asked Questions
Why is the timestamp 10 digits on some systems and 13 on others?
10-digit timestamps are in seconds (standard Unix time). 13-digit timestamps are in milliseconds, commonly used by JavaScript. Divide or multiply by 1000 to convert between them.
Will the timestamp overflow in 2038?
32-bit signed integers overflow on January 19, 2038 at 03:14:07 UTC. Most modern systems and languages have moved to 64-bit integers which push the limit to the year 292 billion.
What timezone does the timestamp use?
Unix timestamps are always in UTC. You apply timezone offset only when formatting the timestamp for human display.