Unix Timestamp Converter
Use this free Unix timestamp converter to turn a Unix timestamp into a readable date and time — or a date into a Unix timestamp. See the live timestamp right now, convert in seconds or milliseconds, and get both the UTC and your local time, plus how long ago (or how far ahead) the date is. Everything runs in your browser: nothing is uploaded or stored.
Unix Timestamp Converter
Convert Unix timestamps to dates & dates to timestamps.
Milliseconds: —
—
Date & time
Unix timestamp
Private by design: every conversion happens in your browser — nothing is uploaded or stored.
How to use the Unix Timestamp Converter
- See the current Unix timestamp at the top — it ticks every second. Copy it in seconds or milliseconds.
- Timestamp to date: paste a timestamp (10 digits = seconds, 13 digits = milliseconds), pick seconds, milliseconds or auto-detect, then click “Convert to date”.
- Date to timestamp: pick a date and a time, choose UTC or your local time, then click “Convert to timestamp”.
- Use the quick examples below to try famous timestamps — for example 0 is the start of Unix time, 1 January 1970.
What is a Unix Timestamp?
A Unix timestamp is a single number that represents a date and time: the number of seconds that have passed since 1 January 1970, 00:00:00 UTC, a moment programmers call the “Unix epoch”. For example, the timestamp 1700000000 means 14 November 2023 at 22:13:20 UTC. Instead of writing dates as text — which every country and language writes differently — computers store time as one plain number. That number is the same everywhere in the world, no matter what timezone you are in, which is why databases, APIs, log files and programming languages all use Unix timestamps to record when something happened.
How does the converter work?
This tool converts in both directions. Timestamp to date: paste any timestamp and it shows the date and time in UTC and in your own local time, the ISO 8601 form, the day of the week, and how long ago — or how far in the future — that moment is. Date to timestamp: pick a date and a time, choose UTC or your local time, and the tool gives you the Unix timestamp in seconds and in milliseconds. The live timestamp at the top of the page ticks every second, so you can copy the current time in either unit with one click. Every conversion happens in your browser — nothing is uploaded or stored.
Seconds or milliseconds?
A Unix timestamp in seconds has 10 digits today (for example 1700000000). The same moment in milliseconds has 13 digits (1700000000000) — it is simply the seconds value times 1,000. Most databases, servers and Unix systems use seconds; JavaScript's Date.now() and many web APIs use milliseconds. Mixing them up is one of the most common developer mistakes: if you feed a seconds timestamp into code that expects milliseconds, you get a date in January 1970; feed milliseconds where seconds are expected and you get a date thousands of years in the future. This tool accepts both and tells you which one you pasted, so the mistake is easy to spot — the auto-detect option reads a 13-digit number as milliseconds and a 10-digit number as seconds.
Example
Try the timestamp 1700000000. It converts to 2023-11-14 22:13:20 UTC, a Tuesday. The timestamp 0 is the epoch itself — 1 January 1970, 00:00:00 UTC, a Thursday. The famous 1000000000 is 9 September 2001, 01:46:40 UTC, and 2000000000 will be 18 May 2033, 03:33:20 UTC. Going the other way, the date 1 January 2030 at 00:00 UTC is timestamp 1893456000. Negative timestamps work too: −1 is 31 December 1969, 23:59:59 UTC — one second before the epoch began.
The Year 2038 problem
Old 32-bit systems store timestamps in a signed 32-bit number, which can only reach 2,147,483,647 — 19 January 2038, 03:14:07 UTC. After that moment the number overflows and those systems jump back to 1901. Modern 64-bit systems do not have this problem, and this converter has no such limit either: it handles dates far beyond 2038, including the year 3000 and beyond. If you work with old embedded devices, file formats or databases, always check whether they store timestamps in 32 or 64 bits.
Tips and common mistakes
- Always check the unit first. 10 digits means seconds, 13 digits means milliseconds. When a date looks wrong by a factor of a thousand, the unit is almost always the cause.
- Remember the timezone. A timestamp itself has no timezone — it is one absolute moment. The same timestamp is 22:13 in London and 03:13 the next day in Karachi (UTC+5). This tool shows both, so compare the UTC line when you share a time with someone abroad.
- Do not confuse Unix time with Excel dates. Excel counts days since 1 January 1900, not seconds since 1970 — the two systems are completely different.
- Use UTC for storage, local time for display. Store timestamps in your database, and convert to the visitor's local time only when showing the date on screen. That way the same stored value is correct for every user in every timezone.
When to convert a timestamp
Use it whenever you meet a long number where a date should be. A database row stamped 1700000000, a log file full of 13-digit numbers, an API response with a "created_at" field — all of these are Unix timestamps. Developers convert them to check when a user signed up, when an error happened, or when a payment was made. The other direction matters too: turning a deadline into a timestamp is how you schedule a post, a backup or a reminder in code. If the converted date looks wrong by a few hours, check the timezone; if it shows 1970 or the year 56000, check seconds versus milliseconds.
Frequently asked questions
What is a Unix timestamp?
A Unix timestamp is the number of seconds since 1 January 1970, 00:00:00 UTC — the “Unix epoch”. For example, 1700000000 means 14 November 2023, 22:13:20 UTC. Developers, databases and APIs use timestamps because one number works in every timezone.
Is this Unix timestamp converter really free?
Yes, 100% free, no sign-up, no limits. It runs entirely in your browser — convert as many timestamps as you like.
What is the difference between seconds and milliseconds?
A timestamp in seconds has 10 digits (for example 1700000000); the same moment in milliseconds has 13 digits (1700000000000). JavaScript and many APIs use milliseconds, while most databases and Unix systems use seconds. This tool accepts both and converts between them.
Does it work with dates before 1970 or far in the future?
Yes. Dates before 1970 give a negative timestamp (for example −1 is 31 December 1969, 23:59:59 UTC). Dates far in the future work too — but note the “Year 2038 problem”: old 32-bit systems stop at 2147483647 (19 January 2038). This converter has no such limit.
What timezone are the results shown in?
Both. Every conversion shows the date and time in UTC and in your own local time, so you can compare them at a glance. The timestamp itself has no timezone — it is one absolute moment — and the two lines are just two ways of writing that same moment.
Is my date or timestamp sent to a server?
No. Every conversion happens in your browser; nothing is uploaded or stored — safe even for private log files and database values.
Word Counter
Count words, characters, sentences & reading time of any text.
Age Calculator
Exact age in years, months & days from your date of birth.
JSON Formatter & Validator
Format, beautify, minify & validate JSON with exact error lines.
Countdown Timer & Pomodoro
Set any countdown with a sound alarm, plus a Pomodoro focus timer.
UUID Generator
Generate random UUID v4 & time-based v1 IDs, in bulk.
Date Calculator
Days between dates, add or subtract days & business days.
Time Zone Converter
Convert any time between world time zones, with live clocks.