Incident and log timelines
Paste epochs from CloudWatch, Datadog, or app logs to confirm exact UTC and local wall times during an outage review.
Epoch Converter – Timestamp to Date & Date to Timestamp
Paste a timestamp, select its unit, and click Convert to see the date in UTC and a selected time zone. Live current epoch. Free, runs in your browser.
The current Unix epoch time is 1793269099
Type to search (e.g. London or UTC). Use × to clear and choose another.
1. Timestamp → Date
Go to Date → TimestampInput unit
Auto uses digit length (≈10 → seconds, ≈13 → ms, ≈16 → µs, ≈19 → ns).
2. Date → Timestamp
Go to Timestamp → DateEnter a calendar date and time in the selected timezone, then convert to Unix epoch.
Results
Displayed dates use millisecond precision; human-date fields keep whole seconds only.
Epoch (seconds): —
Epoch (milliseconds): —
Date and time (UTC): —
Date and time (selected timezone): —
Relative: —
ISO 8601 (UTC): —
RFC 2822 (UTC): —
Epoch dates for the start and end of the year/month/day
Show start & end of
Start epoch (sec): —
End epoch (sec): —
Start: —
End: —
Convert between total seconds and days, hours, minutes, seconds
From a single duration in seconds, split into parts (and fill the fields below).
Or enter parts separately to get the total in seconds.
Parts are combined as-is (they do not need to be normalized; e.g. 25 hours is allowed).
—
Unix epoch time, explained
Unix epoch time counts from 1 January 1970, 00:00:00 UTC. The integer itself is timezone-agnostic; Asia/Karachi or America/New_York only change how that same instant is shown on a clock.
Seconds vs milliseconds: around “now”, seconds are ~10 digits (1700000000) and milliseconds ~13 (1700000000000). Example: 1700000000 seconds = 1700000000000 milliseconds → 14 November 2023, 22:13:20 UTC.
2038 note: 32-bit signed systems that store seconds overflow near early 2038. Prefer 64-bit timestamps (or milliseconds carefully) for long-lived data.
Current epoch in common environments
| Environment | Example |
|---|---|
| JavaScript | Math.floor(Date.now() / 1000) |
| Python | import time; int(time.time()) |
| PHP | time() |
| SQL (PostgreSQL) | EXTRACT(EPOCH FROM now()) |
| Bash | date +%s |
Epoch converter FAQs
Unix epoch time is the number of seconds (or a finer unit) since 1 January 1970 00:00:00 UTC. Systems store and exchange instants as integers so every timezone can format the same moment locally.
Seconds are usually 10 digits around “now” (e.g. 1700000000). Milliseconds are about 13 digits (e.g. 1700000000000). Microseconds ~16 digits and nanoseconds ~19. This tool auto-detects by digit length, or you can force a unit.
No. The epoch number is always UTC-based. Changing Asia/Karachi vs UTC only changes how the same instant is displayed as a calendar clock.
Yes. The integer counts from the UTC epoch. Local wall time is a presentation of that instant in a named zone with its offset (and DST rules when they apply).
For seconds: =A1/86400+DATE(1970,1,1) then format as date/time. Excel workbooks use either the 1900 or 1904 date system (File → Options → Advanced, or Excel → Preferences on Mac)—verify with a known value like 0 → 1970-01-01 under your workbook’s system. Prefer this page for a quick check, then paste the human date.
Common causes: treating milliseconds as seconds (off by ~1000×), the reverse, or reading UTC as if it were already local. Check the detected unit and compare the UTC line with your selected zone line.
When to use this epoch converter
Turn Unix timestamps from logs, databases, and APIs into readable dates—and back—without leaving the browser.
Unix time vs human dates
Systems store instants as integers counted from 1970-01-01 UTC. Humans need calendar clocks. This page bridges both directions so you can verify a value from a log line, ticket, or database row without guessing units or timezones.
Prefer ISO 8601 in new APIs when you control the contract; keep this converter handy when you inherit second- or millisecond-based fields that already ship in production.
Retention and range filters
Convert a boundary date to seconds, then use Epoch Time Ranges for start/end of day, month, or year in SQL and API queries.
API and JSON payloads
Check timestamp fields before sending a request in API Tester, or find nested epoch values in JSON Viewer.
Cross-timezone handoffs
Show the same instant in UTC and a named IANA zone with offset so on-call notes stay unambiguous across regions.