June 16, 2026

How to Convert a Unix Timestamp to a Human-Readable Date

You are reading a log file, an API response, or a database row and you hit a value like 1750000000. It is clearly a date, but which one? Computers love these compact numbers; humans cannot read them at a glance.

A timestamp converter translates that number into a real date and time, and back again. Here is how.

How to convert a Unix timestamp to a date

QuickWand's free timestamp converter runs entirely in your browser, so your data never leaves your device.

Open the timestamp converter.
Paste the Unix timestamp (for example 1750000000) into the input.
Read the human-readable date and time, shown in both UTC and your local time zone.
To go the other way, enter a date and copy out its Unix timestamp.

What a Unix timestamp actually is

A Unix timestamp — also called epoch time— is simply the number of seconds since 00:00:00 UTC on 1 January 1970, not counting leap seconds. That single agreed-upon starting point (the “epoch”) means every computer can represent any moment as one plain integer.

Why systems love it:

Compact— one number instead of a long date string.
Unambiguous— it is always UTC, so there is no timezone confusion in storage.
Easy to compare— a later moment is always a bigger number, so sorting and subtracting durations is trivial.

The seconds-vs-milliseconds gotcha

The classic trap: some systems count millisecondssince 1970 instead of seconds. JavaScript's Date.now() is the usual culprit. A present-day timestamp in seconds has 10 digits; in milliseconds it has 13. If your converted date lands decades in the future, you almost certainly have milliseconds — divide by 1000 and try again.

Time zones

The timestamp itself has no time zone — it is the same instant everywhere. The display is where time zones enter: the same number can read as one wall-clock time in UTC and another in your local zone. The converter shows both so you can be sure which one a log entry refers to.

Going the other direction

Need to hard-code a cutoff date or test a time-based feature? Enter a calendar date and the converter gives you its Unix timestamp to paste into your code or query. If you are also formatting the variable names around that value, the case converter turns a label like created at into created_at or createdAt.

Paste the number, read the date — no more squinting at ten-digit integers in your logs.

Frequently asked questions

What is a Unix timestamp?

A Unix timestamp (also called epoch time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is a compact, timezone-free way to store a moment in time, which is why databases, logs, and APIs use it everywhere. For example, 1750000000 corresponds to a date in June 2025.

Why is my timestamp in milliseconds, not seconds?

Some systems — notably JavaScript's Date.now() — store time in milliseconds since 1970, so the number has three extra digits (13 digits instead of 10 for current dates). If your converted date lands far in the future, your value is probably in milliseconds; divide by 1000 to get seconds.

Does the timestamp account for time zones?

A Unix timestamp is always defined in UTC and has no timezone of its own — it is the same instant everywhere on Earth. When you convert it to a readable date, you choose whether to display it in UTC or your local time zone, but the underlying number does not change.

Is the converter free and private?

Yes. It is free with no sign-up and runs entirely in your browser. Your timestamps and dates are never uploaded to a server.