Timestamp Converter
Convert a Unix timestamp to a readable date, or a date to its Unix timestamp.
Unix timestamps count seconds since 1 January 1970 (UTC) and are used throughout programming, databases and APIs. This tool converts a timestamp into a readable local date and time, or takes a date you pick and shows its Unix timestamp in both seconds and milliseconds — useful for debugging logs, APIs, or database records.
Why computers count time from 1970
January 1st, 1970 (UTC) is known as 'the Unix epoch' — an arbitrary but now deeply entrenched reference point chosen by early Unix system designers. Counting seconds from a fixed point rather than storing a calendar date directly makes date arithmetic (like figuring out how many days are between two events) a simple subtraction of two numbers instead of complicated calendar-aware logic, which is why the convention stuck and spread into countless programming languages and database systems.
Seconds versus milliseconds — a common source of bugs
Some systems (like most Unix/Linux tools and many databases) use timestamps in seconds, while JavaScript's own Date object internally uses milliseconds. Mixing the two up is an extremely common bug — treating a seconds-based timestamp as milliseconds makes a date appear to be sometime in 1970, while treating milliseconds as seconds pushes a date far into the future. This tool automatically detects which unit you've entered based on the number of digits.
Timestamps and timezones are separate concepts
A Unix timestamp itself has no timezone — it's a single global count of seconds since the epoch. Timezone only enters the picture when converting that number into a human-readable date, which is why the same timestamp displays as a different local time depending on which timezone the viewer is in, even though the underlying number never changes.
How to use it
- To convert a timestamp: paste it into the timestamp field.
- The equivalent readable date and time appears automatically.
- To go the other way: pick a date and time in the date field.
- The Unix timestamp (seconds and milliseconds) appears automatically.
Common ways people use this tool
Debugging API responses
Convert a raw timestamp field from a JSON API response into a readable date to verify it's correct.
Reading database timestamp columns
Quickly check what date a stored Unix timestamp value in a database actually corresponds to.
Scheduling something for a specific future timestamp
Pick a target date and time, then get its exact Unix timestamp value to hard-code into a script or configuration.
Tips for getting the best results
- Count the digits in a timestamp you're unsure about — 10 digits usually means seconds, 13 digits usually means milliseconds.
- Remember the readable date shown reflects your browser's local timezone, not necessarily UTC.
- Use 'Use current time' as a quick way to get right now's timestamp for testing a script or API call.
- When debugging a timestamp that looks wrong, check whether the source system might be storing it in a different timezone than you assumed.
Frequently asked questions
Does this use seconds or milliseconds?
The tool accepts and displays both — enter a 10-digit number for seconds or a 13-digit number for milliseconds, and it detects which one automatically.
What timezone is used for the readable date?
The readable date shown reflects your browser's local timezone; the underlying timestamp itself is always UTC-based.
Can I get the current timestamp right now?
Yes, click 'Use current time' to fill in right now's date and see its timestamp instantly.
Why do some systems use a timestamp in seconds and others in milliseconds?
It largely comes down to historical convention — Unix and many databases default to seconds, while JavaScript's Date object and some web APIs use milliseconds for finer precision.
Can a Unix timestamp be negative?
Yes, negative timestamps represent dates before January 1st, 1970, though most everyday systems rarely need to represent dates that far back.
Is there a maximum date this can represent?
Standard 32-bit timestamp systems have a known limit around the year 2038, though most modern 64-bit systems (and this tool) can represent dates far beyond that.
Does daylight saving time affect the timestamp itself?
No — the underlying Unix timestamp never changes with daylight saving; only its displayed local time shifts, since DST is a timezone display concept, not a change to the actual moment in time.
Why do some APIs return timestamps as strings instead of numbers?
Some systems format timestamps as ISO 8601 date strings (like 2026-07-05T14:30:00Z) rather than a raw Unix number, since that format is more directly human-readable while still being precisely parseable by software — both approaches represent the same underlying moment in time.
Can a timestamp represent a date far in the past, before computers existed?
Yes, a Unix timestamp is just a signed number of seconds relative to the 1970 epoch, so negative values can represent any date before 1970, including historical dates well before computing existed.
Why did some older systems have a 'Year 2038 problem'?
Systems storing timestamps as a 32-bit signed integer can only count seconds up to a certain maximum before overflowing, which happens to fall in the year 2038 — modern 64-bit systems, including this tool, aren't affected by that specific limitation.