Unix Timestamp and Unix Time Reference
Live reference for Unix timestamp, Unix time, and epoch time values — right now, today midnight, yesterday, this week, month, and year — plus fixed points including epoch 0 and the Year 2038 boundary.
Unix timestamp, Unix time, and epoch time
A Unix timestamp is a number that counts from 1970-01-01 00:00:00 UTC. Unix time, epoch time, POSIX time, and Unix timestamp usually refer to the same value: seconds since the Unix epoch. This page gives copyable reference values; use the linked converters when you need to turn a human date into a timestamp or an epoch value back into readable time.
How to use this reference
All timestamps are shown in UTC. The 'Right now' row updates every second. Click the copy button next to any value to grab Unix time for your code, query, log filter, or test fixture.
- Seconds — 10-digit integer, standard Unix time (Python, PHP, Go, Ruby, C)
- Milliseconds — 13-digit integer, multiply seconds × 1000 (JavaScript, Java, .NET)
- All midnight values are 00:00:00 UTC — add or subtract your timezone offset as needed
When you need a specific timestamp
Developers frequently need fixed timestamps for test fixtures, cron schedules, log filters, and date-range queries.
- Today midnight — filter events since the start of the current UTC day
- Yesterday midnight — build a one-day UTC date range for log queries
- Start of this month — first day of the billing or reporting period
- Start of this year — year-to-date aggregations and annual resets
- End of this year — boundary checks for annual reports and tests
- Unix epoch (0) — the reference point: January 1, 1970 00:00:00 UTC
- Y2038 max (2,147,483,647) — the largest value a 32-bit signed integer can hold
Using these timestamps in queries
The reference values are designed for copy-paste use in scripts, SQL filters, dashboards, and support investigations. For date ranges, copy both the lower boundary and the next boundary, then use a half-open comparison. That pattern works with second precision, millisecond precision, and databases that preserve fractional seconds.
- For today's UTC events, query created_at >= todayMidnight and created_at < tomorrowMidnight
- For yesterday's UTC events, query created_at >= yesterdayMidnight and created_at < todayMidnight
- For annual reports, query created_at >= yearStart and created_at < nextYearStart
- For JavaScript Date, multiply copied second values by 1000 before constructing a Date
What week in the year are we in? Today timestamp
The "This week" rows above answer "what week in the year are we in" — the start-of-this-week and end-of-this-week Unix timestamps are computed live, alongside today's epoch. ISO week numbers run 1–53; the current week index is implicit in the timestamps shown.
- What week in the year are we in — the "This week" rows above bracket the current ISO week
- This week start / end — Unix seconds for the current ISO 8601 week (Monday 00:00 UTC to Sunday 23:59:59 UTC)
- Today timestamp / today midnight — Unix seconds for today midnight UTC is the "Today" row
- "Today's timestamp", "today timestamp", and "today's epoch" all refer to the same Unix integer
Week in year, week number in year, exact time with seconds
Week-of-year queries — "week in year", "week number in year", "what is the current week number" — are derived from the ISO 8601 week date format (%V), which numbers weeks 1–53 with Monday as the first day. The "This week" rows above show the boundary Unix timestamps. Live precision: "what is the exact time with seconds" is answered by the live UTC clock at the top of every page.
- Week in year / week number in year / what is the current week number — ISO 8601 week-of-year format is %V; weeks run 1–53; first week of year contains the first Thursday
- ISO 8601 week format example: 2026-W22 = week 22 of 2026
- What is the exact time with seconds — the live clock above shows current UTC time at 1-second precision (ms shown as the 13-digit value)
- Day-of-year format (%j) runs 1–366; differs from ISO week which is %V (1–53)
Number week in year, epoch calendar reference
Variants: "number week in year" (same as ISO 8601 %V week number), "epoch calendar" and "epoch calendar 2025" — searches for a year-by-year Unix timestamp reference. The /timestamps/year/2024 etc. pages cover this directly.
- Number week in year / number week in year — ISO 8601 %V week number; runs 1–53; example 2026-W22
- Epoch calendar / epoch calendar 2025 — see /timestamps/year/2025 for a calendar of Unix timestamps for each day of 2025
- Quick reference years: /timestamps/year/2024 through /timestamps/year/2029 — start/end Unix seconds for each year
How many weeks in year so far, current week in year, what is the current week of the year
Variants of the week-number query: "how many weeks in year so far", "what is the current week of the year", "current week in year". ISO 8601 weeks are numbered 1-53; the count of completed weeks so far equals the current ISO week number minus 1.
- How many weeks in year so far / how many weeks in year so far — equal to (current ISO week − 1); the rows above show the current week boundary
- What is the current week of the year / what is the current week of the year — the current ISO 8601 week number; runs 1–53
- Current week in year / current week in year — same as ISO %V week number; first week contains the first Thursday
FAQ
- Are Unix timestamp, Unix time, and epoch time the same thing?
- In most developer searches, yes. They all mean a numeric count from 1970-01-01 00:00:00 UTC, usually in seconds. Some systems use milliseconds, microseconds, or nanoseconds instead.
- How do I convert timestamp to Unix time?
- If the timestamp is already a 10-digit epoch value, it is Unix time in seconds. If it is a date string, use the Date to Epoch converter. If it is a 13-digit value, divide by 1000 to get Unix seconds.
- Where do I convert epoch to time?
- Use the Epoch to Time converter for the reverse direction: paste a Unix timestamp and get the readable date, UTC time, ISO 8601, and local timezone output.