Epoch seconds
1767225600
2026-01-01 00:00:00 UTC
10-digit Unix timestamp for APIs, SQL filters, logs, and shell commands.
Epoch to Timestamp Converter
Convert an epoch value into a readable timestamp string. Paste Unix seconds or milliseconds from logs, APIs, databases, browser events, or JWT claims and get UTC, ISO 8601, and selected-timezone output without guessing the unit first.
Start of 2026 answer
1767225600 is 2026-01-01 00:00:00 UTC
The Unix seconds value 1767225600 marks January 1, 2026 at midnight UTC. The matching millisecond timestamp is 1767225600000, and the ISO timestamp is 2026-01-01T00:00:00.000Z.
Timezone
Epoch to Date Converter
Use this converter for searches like epoch converter, epoch to date, epoch time to date, epoch time converter, and unix epoch converter. It also matches narrower searches like epoch timestamp converter and epoch timestamp to date. Paste the raw Unix value exactly as you copied it and this tool turns it into a readable date, time, ISO string, and timezone-aware answer.
These examples match the broad homepage queries people use when they are not sure whether their timestamp came from seconds, milliseconds, or decimal SQL output. Decimal SQL values and negative timestamps work too.
Readable answer
1767225600 converts to Thursday, January 1, 2026 at 00:00:00 UTC. If this looks shifted by hours, keep the same epoch value and change the timezone instead of editing the number.
UTC answer for epoch search results
In UTC, 1767225600 is Thursday, January 1, 2026 at 00:00:00 UTC. Use this baseline for searches like epoch to date, epoch date, and epoch timestamp converter before comparing local timezone output.
seconds3 months ago
UTC Date
Thursday, January 1, 2026
UTC Time
00:00:00 UTC
Date
Thursday, January 1, 2026
Time
00:00:00
Day
Thursday
ISO 8601
2026-01-01T00:00:00.000Z
Timezone
UTC
Epoch to timestamp format examples
Searchers use epoch to timestamp, epoch time converter, epoch date, and epoch to date for the same practical job: decode a raw Unix value into a timestamp humans can compare against logs, release notes, migrations, and customer-facing dates.
Epoch milliseconds
1767225600000
2026-01-01T00:00:00.000Z
13-digit timestamp used by JavaScript Date.now(), browser events, and telemetry.
Worked epoch time
1774708200
2026-03-28 14:30:00 UTC
Useful when the time-of-day matters for incident review or API validation.
Seconds vs milliseconds
A 10-digit epoch timestamp normally means seconds. A 13-digit timestamp normally means milliseconds. If a converted date lands in 1970 or far in the future, check the unit before changing timezone settings or editing the source value.
UTC first, local second
Use UTC when verifying backend behavior, then compare local timezone output only when the timestamp needs to match a user interface, support ticket, or regional report. The raw epoch number does not change when the display timezone changes.
Related conversion pages
Frequently asked questions
What does epoch to timestamp mean?
It usually means taking a Unix epoch value and showing the readable timestamp string behind it, such as 2026-01-01 00:00:00 UTC or an ISO 8601 value.
Should I paste seconds or milliseconds?
Paste the value exactly as you copied it. The converter treats 10-digit values as seconds and 13-digit values as milliseconds.
Why does my local timestamp differ from UTC?
The epoch value is the same instant everywhere. UTC and local timezone settings only change the display string.