How to Convert a Unix Timestamp to a Date
A Unix timestamp is a plain number that stands for a single moment in time — the count of seconds since 1 January 1970 at midnight UTC (the “epoch”). It shows up everywhere in software: log lines, database columns, API tokens, cookie expiry. The trouble is that a number like 1751500800 means nothing at a glance. This guide shows you how to turn an epoch into a readable date — and a date back into an epoch — using the Timestamp Converter, which runs entirely in your browser with nothing uploaded.
The tool
Timestamp Converter
Step by step
- Open the Timestamp ConverterHead to the Timestamp Converter. At the top you’ll see the live current Unix time ticking upward, read straight from your device’s clock — a handy sanity check for whether a value you’re holding is in the past or the future.
- Paste an epoch to get a dateDrop a Unix timestamp into the input and the tool decodes it instantly. A 10-digit number is read as seconds; a 13-digit number as milliseconds. Use the seconds/milliseconds toggle if the tool guesses wrong for your value.
- Read UTC, local, and ISO 8601The result appears three ways at once: UTC (the universal reference), your local time (the same instant on your own clock), and ISO 8601 (the machine-friendly string like 2026-07-03T00:00:00Z). Copy whichever format fits where you’re pasting it.
- Go the other way — date to timestampNeed the number instead? Pick a calendar date and time and the converter returns the matching Unix timestamp. Flip the seconds/milliseconds toggle depending on whether your system stores 10-digit or 13-digit values.
- Copy and use itCopy the format you need and paste it into your log viewer, database field, API call, or bug report. Nothing was sent anywhere — the conversion happened locally on your machine.
What a Unix timestamp actually is
A Unix timestamp — also called epoch time — is the number of seconds that have elapsed since 1 January 1970 00:00:00 UTC. Because it’s a single integer tied to UTC, it’s unambiguous: the same timestamp means the same instant no matter where in the world it’s read. That’s exactly why servers, databases, and APIs love it.
Watch the digit count. Ten digits is almost always seconds, while thirteen digits is almost always milliseconds (seconds × 1000). If a converted date lands in 1970 or thousands of years in the future, you’ve likely got the wrong unit — flip the seconds/milliseconds toggle and it’ll snap into place.
Why UTC and local time both matter
UTC and your local time are the same instant expressed on two different clocks. A server log stamped in UTC and an event you remember happening at 3 p.m. your time can look like they’re hours apart on paper even though they describe the same moment. Seeing both side by side is what lets you line them up.
This is the everyday pain the converter removes: you paste the epoch from a log, read the UTC value to match the server, and read the local value to match your own recollection — no mental timezone math required.
Where developers reach for this
Debugging is the big one. When a log line or error trace carries a raw epoch, dropping it into the converter tells you exactly when the event fired. The same goes for database fields — created_at, updated_at, expires_at columns are frequently stored as integers rather than dates.
It’s also handy for APIs: token and session expiry are often expressed as epoch seconds, so converting one tells you at a glance whether a credential is still valid or already stale.
ISO 8601, the portable format
ISO 8601 is the standardized text form of a date and time — for example 2026-07-03T00:00:00Z, where the trailing Z means UTC. It sorts correctly as plain text, is unambiguous across systems, and is what most modern APIs and config files expect when they want a human-readable timestamp instead of a raw number.
The converter gives you the ISO string alongside the epoch, so you can move between “the number the database stores” and “the string the API wants” without hand-formatting anything.
Private by design
The whole conversion runs in your browser using your device’s own clock. Nothing you paste is uploaded, logged, or sent to a server — the epoch you’re debugging never leaves your machine, which matters when that timestamp comes from production data or a customer’s record.
Frequently asked questions
Is it seconds or milliseconds?
A 10-digit timestamp is seconds; a 13-digit one is milliseconds (seconds × 1000). The converter picks a sensible default from the length, and the seconds/milliseconds toggle lets you force the unit if a value is ambiguous.
Why is my local time different from the UTC result?
They’re the same instant shown on two clocks. UTC is the universal reference, and your local time is that same moment adjusted for your timezone — so a gap between them is expected, not an error.
Does my timestamp get uploaded anywhere?
No. The conversion happens entirely in your browser using your device’s clock. Nothing you enter is sent to a server or stored.
What is ISO 8601 and when should I use it?
ISO 8601 is a standardized date-time string like 2026-07-03T00:00:00Z (the Z means UTC). Reach for it when a system wants a readable, sortable, unambiguous timestamp rather than a raw epoch number.