Unix Timestamp Converter
Convert Unix timestamps in seconds or milliseconds to ISO 8601, UTC, local and IANA timezone dates, or turn a date back into a timestamp.
Unix Timestamp Converter
Timestamp to date
Enter a Unix timestamp above
Date to timestamp
Enter a date/time above
What this tool does
You can convert a Unix timestamp to a readable date (and back) directly in the browser: paste the number and get ISO 8601, UTC, local time, a chosen timezone, and relative time at once. The converter detects the unit by magnitude — a 10-digit value is seconds, a 13-digit value is milliseconds. A timestamp itself has no timezone; only its rendering does.
Updated . Provided as is. Check the output before you rely on it in production.
How to use Unix Timestamp Converter
- 1
Enter a Unix timestamp
Paste a timestamp in seconds or milliseconds since 1970-01-01 UTC. The tool detects the unit.
- 2
Read the converted date
See the timestamp as ISO 8601, UTC, your local time and a relative description such as 3 days ago.
- 3
Convert a date to a timestamp
Enter a date such as 2026-02-11 12:00:00 or an ISO 8601 string to get seconds and milliseconds back.
- 4
Pick the timezone
Choose the timezone the input and output are read in, so the result matches the system you are debugging.
- 5
Jump in time
Use Now, +1 hour, +1 day or +1 week to generate timestamps for tests and fixtures.
Questions and answers
What is Unix Timestamp Converter?
Does Unix Timestamp Converter store or send my data?
What is a Unix timestamp?
Use it as an API
Unix Timestamp Converter is also callable as a free HTTP JSON API at
https://aidevhub.io/api/timestamp-converter/ — GET with query
parameters or POST with a JSON body, no authentication, CORS enabled, fair use
(abusive traffic is throttled at the edge; there is no per-request quota header). Responses return
{ ok, tool, result, meta }.
curl -s "https://aidevhub.io/api/timestamp-converter/?input=1752307200&direction=timestamp_to_date"
Machine-readable contract: /api/tool/timestamp-converter.json All API endpoints: /agents/ LLM site index: /llms.txt
For AI agents: how to call this tool
Machine-readable contract, endpoints and examples. Humans can ignore this section.
Best Path For Builders
Dedicated API endpoint
Deterministic outputs, machine-safe contracts, and production-ready examples.
Dedicated API
https://aidevhub.io/api/timestamp-converter/ OpenAPI: https://aidevhub.io/api/openapi.yaml
How do I convert a Unix timestamp to a human-readable date?
Paste the timestamp into the left panel. Unix time counts seconds since the epoch, 1970-01-01T00:00:00 UTC, so the number itself carries no timezone — the converter renders that single instant as ISO 8601, UTC, your local time, any of 22 common timezones, and a relative phrase like "3 hours ago". The right panel goes the other way: type an ISO 8601 date or YYYY-MM-DD HH:MM:SS and get seconds and milliseconds back.
Step by step
- Paste the raw number — no unit needed. The converter reads a 10-digit number as seconds and a 13-digit one (1012 or larger) as milliseconds, and tells you which it detected.
- Pick a timezone from the selector to render the same instant in another region alongside UTC and local time.
- Click any result row to copy it; the Now, +1 hour, +1 day, and +1 week buttons generate reference timestamps.
- For the reverse direction, paste a date string; the live clock at the top shows the current Unix timestamp ticking each second.
Seconds or milliseconds? Epoch unit boundaries
| Value | Unit | Meaning |
|---|---|---|
| 0 | seconds | The Unix epoch: 1970-01-01T00:00:00Z. |
| 1000000000 – 9999999999 | seconds (10 digits) | 2001-09-09 through 2286-11-20 — every present-day seconds timestamp has 10 digits. |
| 2147483647 | seconds | 2038-01-19T03:14:07Z — the largest value a signed 32-bit integer holds (the "year 2038 problem"). |
| > 1012 | milliseconds (13 digits) | This converter's detection threshold: larger values are treated as milliseconds, the unit JavaScript's Date.now() returns. |
Detection as implemented in this converter. Microsecond (16-digit) and nanosecond (19-digit) timestamps are not auto-detected — divide by 1,000 or 1,000,000 first.
Is a Unix timestamp in UTC?
Strictly, a Unix timestamp has no timezone at all — it is a count of seconds since an instant that is defined in UTC. The same number denotes the same moment everywhere on Earth; converting it "to a timezone" only changes the wall-clock rendering. This is why storing timestamps (or ISO 8601 with an explicit offset) beats storing local datetime strings: nothing shifts when servers or users change zones.
Does Unix time count leap seconds?
No. Unix time pretends every day is exactly 86,400 seconds, so leap seconds are absorbed rather than counted. For logging, scheduling, and API work this never matters; it only matters if you need sub-second astronomical accuracy across decades, which calls for TAI-based time instead.
Do converted timestamps leave the browser?
No. All conversion runs client-side with the browser's own date and timezone machinery; nothing is uploaded. Timestamps from logs and tokens can reveal user activity patterns, so a local-only converter is the right default when you are debugging production data.