Unix Epoch Converter
If you searched for epoch converter, epoch to date, epoch time to date, epoch time converter, or unix epoch converter, start here. Paste any Unix timestamp and see the matching date, time, and timezone in one click. Need the reverse? Enter a readable date to get its epoch value. The converter auto-detects seconds (10 digits) versus milliseconds (13 digits) so you don't need to know the format — just paste and copy the result. Works with timestamps from server logs, JWT tokens, SQL databases, API responses, and shell commands.
Fast rule: if you already have a number, start with Timestamp to Date. If you already have a calendar date and time, jump to Date to Timestamp. If you only need the live Unix value, skip straight to Current Epoch Time.
Direct 2026 checkpoint
1767225600 is the Unix epoch seconds value for the start of 2026 in UTC. It converts to Thursday, January 1, 2026 at 00:00:00 UTC. Use 1767225600000 when the next system expects epoch milliseconds.
Paste a Unix number to decode it, or use Date to Timestamp if you start with a readable date.
1767225600 -> 2026-01-01 00:00:00 UTC
Use Timestamp to Date when you already have a 10-digit or 13-digit epoch value.
1767225600000 -> Thursday, January 1, 2026
Decode the raw epoch value first, then compare UTC and local timezone output if the visible day looks off.
1767225600 -> January 1, 2026 UTC
Paste epoch seconds from a log, API, SQL row, or JWT claim to get the full datetime.
1774708200 -> 2026-03-28 14:30:00 UTC
Use Timestamp to Date when you need the calendar date plus exact hour, minute, second, timezone, and ISO output.
1774708200 -> Saturday, March 28, 2026 at 14:30:00 UTC
Paste the value unchanged and let the converter detect seconds versus milliseconds before showing the date.
10 digits = seconds, 13 digits = milliseconds
If you have a raw epoch value, copy the readable timestamp string from Timestamp to Date.
1767225600 -> 2026-01-01T00:00:00.000Z
Use the same decode path for API, webhook, database, and event timestamps.
1774708200 -> 2026-03-28 14:30:00 UTC
Keep 13-digit millisecond values intact instead of trimming them before conversion.
1767225600000 -> 2026-01-01 00:00:00 UTC
The highest-impression homepage queries are action queries like epoch converter, epoch to date, epoch time to date, and unix epoch converter. The live converter now sits before the long guide content so those searches can paste a value first. Use the cards and table here when you need help choosing between epoch to date, epoch to timestamp, and date to epoch paths.
epoch converter / unix epoch converter / epoch timestamp converter
Paste the raw 10-digit or 13-digit value from logs, APIs, SQL, JWT claims, or shell commands and read the matching date, time, ISO string, and timezone output.
1767225600 -> 2026-01-01 00:00:00 UTC
epoch to date / epoch date
Use this when the question is what day, weekday, or human-readable date an existing epoch number represents. Keep the raw value intact and let the converter detect seconds versus milliseconds.
1767225600000 -> Thursday, January 1, 2026
epoch time to date / epoch to timestamp
Best when the exact time-of-day matters for log lines, API payloads, support tickets, or incident review. Paste the epoch and compare UTC against local output without editing the original value.
1774708200 -> 2026-03-28 14:30:00 UTC
date to epoch / convert to epoch time
Start with a readable calendar date and time, set the timezone first, and create the exact epoch value your API, database, queue, or script expects next.
2026-03-28 14:30:00 UTC -> 1774708200
| Search intent | You probably have | Use this path | Direct 2026 answer | Next step |
|---|---|---|---|---|
| epoch converter / epoch time converter / unix epoch converter | A raw Unix number, or a readable date you need to encode | Start with Timestamp to Date, then switch to Date to Timestamp only if your input is already a calendar time. | 1767225600 -> 2026-01-01 00:00:00 UTC, or 2026-01-01 00:00:00 UTC -> 1767225600. | Open Timestamp to Date |
| epoch to date / epoch date / epoch time to date / epoch to date time | A 10-digit or 13-digit epoch value copied from logs, SQL, a JWT, or an API response | Paste the value unchanged into Timestamp to Date and use the timezone selector for UTC or local output. | 1774708200 -> 2026-03-28 14:30:00 UTC with the matching date, time, weekday, and ISO string. | Convert Epoch to Date |
| epoch to timestamp / epoch timestamp converter / epoch timestamp to date | An existing epoch timestamp where you need the readable timestamp string | Use Timestamp to Date and copy the plain datetime or ISO 8601 result instead of changing the Unix value. | 1767225600 -> 2026-01-01 00:00:00 UTC or 2026-01-01T00:00:00.000Z. | Decode Epoch Timestamp |
| date to epoch / convert to epoch time / timestamp to epoch | A readable calendar date and wall-clock time | Use Date to Timestamp, set the timezone first, then copy seconds for many backends or milliseconds for JavaScript. | 2026-03-28 14:30:00 UTC -> 1774708200 seconds or 1774708200000 milliseconds. | Open Date to Timestamp |
The confusing part of these homepage queries is that epoch to timestamp and time to epoch sound similar but point in opposite directions. If you already have a Unix number, decode it in Timestamp to Date. If you already have a readable time and need the Unix output, jump straight to Date to Timestamp.
Use this map when your search phrase is broad and you are not sure which field to use. It covers epoch converter, epoch to date, epoch date, epoch time converter, epoch time to date, epoch to timestamp, unix epoch converter, epoch timestamp converter, and epoch timestamp to date with the exact converter, output, and example to copy next.
| What you typed | Start with | Use this converter | What you get | Copy-ready example |
|---|---|---|---|---|
| epoch converter | A Unix number, or a date you need to encode | Timestamp to Date first | Decode a Unix value, or switch to the reverse converter if your input is already a date. | 1767225600 -> 2026-01-01 00:00:00 UTC |
| epoch to date | A 10-digit or 13-digit epoch value | Timestamp to Date | Get the readable calendar date, weekday, exact time, ISO string, and selected timezone. | 1767225600000 -> Thursday, January 1, 2026 |
| epoch date | An epoch value where the calendar day matters | Timestamp to Date | Confirm the date and weekday behind the raw Unix number before checking timezone details. | 1767225600 -> Thursday, January 1, 2026 |
| epoch date converter | A Unix timestamp where the date is the main thing you need | Timestamp to Date | Decode the Unix value into the readable date first, then use the time and timezone output if you need more detail. | 1767225600 -> Thursday, January 1, 2026 |
| convert epoch to time | An epoch value where the hour, minute, and second matter | Timestamp to Date | Convert the raw epoch into a full time-of-day answer instead of stopping at the calendar date. | 1774708200 -> 14:30:00 UTC on March 28, 2026 |
| epoch time converter | An epoch number but the unit is unclear | Timestamp to Date | Paste the value unchanged and let the converter detect seconds versus milliseconds. | 10 digits = seconds, 13 digits = milliseconds |
| epoch time to date | Epoch seconds from logs, SQL, or an API | Timestamp to Date | Decode the full datetime, including hour, minute, second, and timezone-aware output. | 1774708200 -> 2026-03-28 14:30:00 UTC |
| epoch to date time | An epoch value where the date and exact time both matter | Timestamp to Date | Copy the full date, time, timezone, and ISO 8601 output instead of stopping at the calendar day. | 1774708200 -> Saturday, March 28, 2026 at 14:30:00 UTC |
| epoch to datetime | A Unix value that needs a complete datetime string | Timestamp to Date | Use the ISO or readable datetime output when another system needs the full date plus exact time. | 1767225600 -> 2026-01-01T00:00:00.000Z |
| epoch to utc | A raw epoch value that should be checked in UTC | Timestamp to Date with timezone set to UTC | Keep the Unix number unchanged and set the timezone to UTC before comparing logs, APIs, or database rows. | 1774708200 -> 2026-03-28 14:30:00 UTC |
| unix epoch converter | Unix seconds or milliseconds | Timestamp to Date | Turn a Unix timestamp into a readable UTC or local datetime without manual unit math. | 1767225600000 -> 2026-01-01T00:00:00.000Z |
| epoch to timestamp | A raw epoch value that needs a readable timestamp string | Timestamp to Date | Copy the readable datetime or ISO 8601 timestamp behind the Unix value. | 1767225600 -> 2026-01-01T00:00:00.000Z |
| epoch timestamp converter | A log, webhook, database, or API timestamp | Timestamp to Date | Translate the timestamp into a human-readable UTC or local datetime for debugging. | 1774708200 -> 2026-03-28 14:30:00 UTC |
| epoch timestamp to date | An existing epoch timestamp you need to decode | Timestamp to Date | Convert the existing timestamp to its readable date without trimming 13-digit values first. | 1767225600 -> 2026-01-01 00:00:00 UTC |
| "1767225600" "start of 2026" | A known epoch value for the first second of 2026 | Timestamp to Date | 1767225600 is the Unix seconds value for the start of 2026 in UTC. | 1767225600 -> 2026-01-01 00:00:00 UTC |
Short rule: raw Unix numbers stay in Timestamp to Date. Readable dates and times go to Date to Timestamp.
These are the real broad queries currently driving impressions to the homepage. Each example opens Timestamp to Date with a raw Unix value already pasted so you can verify the answer immediately instead of reading another generic definition first.
Search query
Search query
Search query
Search query
Search query
Search query
Search query
Search query
Search query
Every example above stays on the homepage and uses the live converter below. If your input is already a Unix number, keep it in Timestamp to Date. If you start with a readable calendar time instead, switch to Date to Timestamp.
This homepage is meant to answer the exact phrases people use when they need a fast conversion: epoch converter, epoch to date, epoch time converter, epoch time to date, epoch date, unix epoch converter, epoch to timestamp, and epoch timestamp to date. Instead of another wide comparison table, this section now answers each search phrase as its own mini-guide with a direct example, the right tool, and the main mistake to avoid on mobile or desktop.
Search query
Start here when you have A raw Unix number or a readable calendar time.
Example paste
1767225600 or 2026-01-01 00:00:00 UTC
Decode 1767225600 to 2026-01-01 00:00:00 UTC, or encode 2026-01-01 00:00:00 UTC back to 1767225600.
Search query
Start here when you have A 10-digit or 13-digit Unix value.
Example paste
1767225600
Convert 1767225600 into Thursday, January 1, 2026 at 00:00:00 UTC with ISO output ready to copy.
Search query
Start here when you have Unix seconds copied from logs, APIs, SQL, or JWT claims.
Example paste
1774708200
Convert 1774708200 into 2026-03-28 14:30:00 UTC, plus local-time and ISO variants for the same instant.
Search query
Start here when you have A Unix value where the time-of-day matters, not just the calendar day.
Example paste
1774708200
Convert 1774708200 into Saturday, March 28, 2026 at 14:30:00 UTC, then copy the ISO string when another system needs a precise datetime.
Search query
Start here when you have A Unix number when the unit is unclear.
Example paste
1767225600000
Paste 1767225600000 unchanged and the homepage converts it to 2026-01-01 00:00:00 UTC without manual unit guessing.
Search query
Start here when you have An epoch value when the calendar day matters most.
Example paste
1767225600
Convert 1767225600 into Thursday, January 1, 2026 and confirm the weekday before comparing UTC or local displays.
Search query
Start here when you have Unix seconds, milliseconds, or a decimal epoch value.
Example paste
1767225600000
Decode 1767225600000 to 2026-01-01T00:00:00.000Z and compare the same instant in UTC or your local timezone.
Search query
Start here when you have An epoch timestamp copied from logs, SQL, or an API response.
Example paste
1767225600
Convert 1767225600 into 2026-01-01 00:00:00 UTC and keep the readable timestamp plus ISO output side by side for comparison.
Search query
Start here when you have A raw epoch number that needs a readable timestamp string.
Example paste
1767225600
Convert 1767225600 into the full timestamp 2026-01-01 00:00:00 UTC, then copy the ISO string if the next system expects standard formatting.
If the query starts with an existing epoch value or timestamp, stay in Timestamp to Date. If you already have a calendar time and need a Unix number, switch to Date to Timestamp.
The broad homepage queries are often ambiguous because people use epoch, Unix timestamp, timestamp, and date interchangeably. In practice, they point to two jobs: decode an existing Unix number into a readable datetime, or encode a readable datetime back into Unix seconds or milliseconds. This comparison table makes that language explicit so the homepage answers broad searches more directly instead of forcing users to infer which tool to open.
| What was searched | What it usually means | Example starting value | Best tool on this page | Answer you can copy next |
|---|---|---|---|---|
| epoch converter / unix epoch converter / epoch time converter | You already have a raw Unix number and need the readable answer behind it, or you want one page that handles both decode and encode paths. | 1767225600 or 1767225600000 | Timestamp to Date first | 2026-01-01 00:00:00 UTC, ISO output, weekday, and local-time variants for the same instant. |
| epoch to date / epoch time to date / epoch date | You have an existing epoch value and want the calendar date, weekday, or full datetime it represents. | 1774708200 | Timestamp to Date | 2026-03-28 14:30:00 UTC plus timezone-aware readable output without editing the original epoch. |
| epoch to timestamp / epoch timestamp to date | The search usually wants a human-readable timestamp string from a raw epoch value, not a second epoch number. | 1767225600 | Timestamp to Date | A readable timestamp like 2026-01-01 00:00:00 UTC or 2026-01-01T00:00:00.000Z ready to copy. |
| date to epoch / convert to epoch time | You already have a readable calendar date and need the Unix seconds or milliseconds that point to that exact instant. | 2026-03-28 14:30:00 UTC | Date to Timestamp | 1774708200 seconds or 1774708200000 milliseconds, depending on what the next system expects. |
| epoch timestamp converter / seconds vs milliseconds | You are not asking for a different date. You are checking which unit the raw Unix value uses before you convert it. | 1767225600 and 1767225600000 | Timestamp to Date with auto-detection | The same instant in readable form, with the converter identifying whether the input was seconds or milliseconds. |
Fast rule: if your starting point is already a raw Unix number, stay in Timestamp to Date. If your starting point is a readable calendar value, switch to Date to Timestamp. The search wording changes, but the conversion paths on the homepage stay the same.
The homepage already has both converters, but many searchers still need the shortest path for the exact job they searched. These walkthroughs answer the two main intents directly: decode a raw Unix value into a readable datetime, or encode a readable date into Unix seconds or milliseconds.
Query cluster
epoch to date, epoch time to date, epoch date, unix epoch converter
Use this path when you already have a Unix value copied from a log line, API response, SQL query, JWT claim, or shell command and need the readable datetime back.
1767225600 -> 2026-01-01 00:00:00 UTC
Open Timestamp to DateQuery cluster
date to epoch, convert to epoch time, epoch converter
Use this reverse path when you start with a calendar date and time and need the Unix seconds or milliseconds required by an API, SQL filter, cron-adjacent workflow, or test fixture.
2026-03-28 14:30:00 UTC -> 1774708200
Open Date to TimestampUnix epoch time — also called Unix time, POSIX time, or epoch timestamp — is a single integer that counts the seconds elapsed since January 1, 1970 00:00:00 UTC. That origin moment is called the Unix epoch. Every instant in time maps to exactly one integer: positive numbers represent dates after 1970, and negative numbers represent dates before it. The count never resets and never adjusts for leap seconds, which makes epoch time reliable for storing, sorting, and doing arithmetic on timestamps across systems and timezones.
Why January 1, 1970? Early Unix engineers needed a fixed reference point that fit inside a 32-bit signed integer and still left room to count forward for several decades. That 32-bit counter reaches its maximum on January 19, 2038 03:14:07 UTC — the so-called Y2K38 problem. Modern operating systems and languages now use 64-bit integers, extending the safe range billions of years into the future.
Seconds vs. milliseconds. The original Unix convention stores time as whole seconds: a current epoch value like 1767225600 is 10 digits. JavaScript's Date.now() and many browser APIs use milliseconds instead — a 13-digit number like 1767225600000. To convert milliseconds to seconds divide by 1,000; to convert seconds to milliseconds multiply by 1,000. This epoch converter auto-detects the format so you can convert epoch to date without a manual calculation step.
Where epoch values appear. Epoch timestamps show up in server logs, JWT iat and exp claims, SQL and NoSQL database fields, Unix date +%s output, cron schedules, API rate-limit headers, and cache-control timestamps. An epoch converter turns those raw numbers back into a readable date and time — or generates the right epoch value when you need to insert a specific moment into a query or payload.
If you searched for epoch to date, epoch time to date, unix epoch converter, or date to epoch, this page already covers both directions. Use Timestamp → Date when you have a Unix value and need a readable time. Use Date → Timestamp when you have a wall-clock time and need the epoch seconds or milliseconds for an API, log, JWT, SQL query, or cron-adjacent workflow.
This tool handles both directions: decoding an existing Unix value into a readable date, and encoding a date back into epoch seconds or milliseconds. The table below identifies the right converter for each common task, what input to expect, and the exact output format.
| Search phrase | What you likely have | Best section | What this page answers | Example |
|---|---|---|---|---|
| epoch to date | A 10-digit or 13-digit Unix value | Timestamp to Date | Get the readable date, time, ISO 8601 string, weekday, and relative time in UTC or your selected timezone. | 1767225600 -> 2026-01-01 00:00:00 UTC |
| convert epoch time to date | Epoch seconds from a log, API, token, or database | Timestamp to Date | Decode the raw epoch number into the exact calendar time without dividing or multiplying first. | 1774708200 -> 2026-03-28 14:30:00 UTC |
| convert unix time to datetime | A Unix timestamp that needs a full datetime | Timestamp to Date | Turn Unix time into a human-readable datetime with timezone-aware output and a copyable ISO string. | 1767225600000 -> 2026-01-01T00:00:00.000Z |
| convert from epoch | An epoch value but not its unit | Timestamp to Date | Paste the value as-is and let the tool auto-detect seconds versus milliseconds before converting. | 10 digits = seconds, 13 digits = milliseconds |
| date to epoch | A calendar date and wall-clock time | Date to Timestamp | Generate the matching Unix seconds and milliseconds for the exact moment you choose. | 2026-03-28 14:30:00 UTC -> 1774708200 |
| date to epoch converter | A date that must be encoded for an API or query | Date to Timestamp | Pick the timezone first, then copy the epoch seconds or milliseconds format the destination system expects. | 2026-01-01 00:00:00 UTC -> 1767225600 |
| convert to epoch time | A readable date and time you need to serialize | Date to Timestamp | Use the reverse converter when the job is not decoding epoch, but creating a fresh Unix timestamp. | 2026-03-28 14:30:00 UTC -> 1774708200000 |
| date epoch converter | Either direction, but you are unsure which tool to open | Both converters on this page | Use the first tool for epoch to date and the second tool for date to epoch so both intents are covered on one page. | Decode or encode Unix time without leaving the homepage |
Convert Epoch to Date
Paste the timestamp into the converter above and it will auto-detect whether the input is in seconds or milliseconds. You immediately get the full date, time, weekday, ISO 8601 output, and relative time in the timezone you choose.
1708560000.Convert Date to Epoch
If your query is closer to convert time to epoch or convert to epoch time, the second tool handles that path. Pick the calendar date, set the time, then use the timezone selector so the resulting epoch points to the exact intended instant.
The homepage is also picking up reverse-intent queries like date to epoch, date to epoch converter, convert to epoch time, date time epoch, datetime to epoch, and convert time to epoch. Those searches are the reverse of epoch to date: you already have a readable datetime and need the exact Unix seconds or milliseconds output. This comparison table shows how the timezone choice changes the final epoch value even when the wall-clock time stays the same.
| Search phrase | Type into Date to Timestamp | Timezone before convert | Epoch seconds | Epoch milliseconds | Why this example helps |
|---|---|---|---|---|---|
| date to epoch | 2026-01-01 00:00:00 | UTC | 1767225600 | 1767225600000 | Best for a clean start-of-day Unix value in APIs, database seeds, migrations, and test fixtures. |
| date to epoch converter | 2026-03-28 14:30:00 | UTC | 1774708200 | 1774708200000 | Shows the standard reverse-conversion path: type a readable datetime and copy the exact Unix output immediately. |
| convert to epoch time | 2026-03-28 14:30:00 | America/Los_Angeles | 1774733400 | 1774733400000 | Useful when the destination system cares about the instant, but your input is local Pacific wall-clock time. |
| date time epoch | 2026-03-28 14:30:00 | America/New_York | 1774722600 | 1774722600000 | Makes the timezone offset visible so the same wall-clock time does not generate the wrong Unix value. |
| datetime to epoch | 2026-03-28T14:30:00Z | UTC from Z suffix | 1774708200 | 1774708200000 | Use this when the source datetime already includes UTC and you just need the Unix seconds or milliseconds form. |
| convert time to epoch | 2026-03-28 14:30:00 | Europe/Berlin | 1774704600 | 1774704600000 | Confirms that choosing the timezone before converting is the safe way to reproduce the intended instant. |
If your starting point is a readable date, stay in Date to Timestamp and set the timezone before copying the Unix value. If your starting point is already a raw epoch number, switch back to Timestamp to Date.
These examples cover the most common query patterns that send users to the homepage. They also show the difference between seconds-based epoch values and millisecond-based values.
| Intent | Input | Output | Why it matters |
|---|---|---|---|
| Epoch to date | 1767225600 | 2026-01-01 00:00:00 UTC | 10 digits means seconds since the Unix epoch. |
| Epoch milliseconds to date | 1767225600000 | 2026-01-01 00:00:00 UTC | 13 digits means milliseconds, common in JavaScript. |
| Date to epoch | 2026-01-01 00:00:00 UTC | 1767225600 | The Date to Timestamp form returns seconds and milliseconds. |
| Date and time to epoch | 2026-03-28 14:30:00 UTC | 1774708200 | Timezone selection matters before you convert. |
Several homepage queries are not asking for a different tool. They are asking for the same epoch value in a different output format. Searchers who type epoch timestamp, epoch timestamp converter, epoch timestamp to date, epoch to datetime, epoch to utc, or epoch seconds usually want to confirm which version of the answer they should copy next. This table uses the same sample instant so the output format change is obvious at a glance.
| Query intent | Best output to copy | Example answer | When to use it |
|---|---|---|---|
| epoch timestamp | Unix seconds timestamp | 1774708200 | Use this raw 10-digit value in JWT claims, many APIs, SQL filters, and shell workflows that expect classic Unix seconds. |
| epoch timestamp converter | Unix milliseconds timestamp | 1774708200000 | Use the 13-digit form for JavaScript, browser events, and tools that store epoch time in milliseconds instead of seconds. |
| epoch timestamp to date | Readable UTC date | 2026-03-28 14:30:00 UTC | Best when you need the human-readable answer behind a pasted epoch value and want to compare it against logs or docs in UTC. |
| epoch to datetime | Copyable datetime string | 2026-03-28 14:30:00 | Useful when a dashboard, migration note, or support ticket needs a plain datetime instead of a raw Unix number. |
| epoch to utc | ISO 8601 UTC output | 2026-03-28T14:30:00.000Z | Choose this when another system expects a standard UTC string with an explicit Z suffix instead of a localized date display. |
| epoch seconds | Seconds vs. milliseconds unit check | 10 digits = seconds, 13 digits = milliseconds | Use this quick rule before converting when you are unsure whether the source system emitted Unix seconds or Unix milliseconds. |
If you start with a raw Unix number, paste it into Timestamp to Date and copy the specific output format you need: plain datetime, UTC timestamp string, ISO 8601, or the original seconds and milliseconds values. If you instead start with a readable calendar time and need to create the Unix number, switch to Date to Timestamp.
Searchers who type epoch converter, epoch to date, epoch date, or unix epoch converter often want to confirm that a pasted Unix number maps to the date they expect before they trust the result. This reference table covers the most useful checkpoint values: the Unix epoch itself, one-day math, clean 2026 boundaries, a full datetime example, the 2038 limit, and a negative pre-1970 timestamp.
| Reference point | Epoch seconds | Epoch milliseconds | Readable UTC date | Why it matters |
|---|---|---|---|---|
| Unix epoch start | 0 | 0 | 1970-01-01 00:00:00 UTC | Baseline sanity check for any epoch converter or epoch to date lookup. If a modern timestamp unexpectedly lands here, the units are almost certainly wrong. |
| One day after epoch | 86400 | 86400000 | 1970-01-02 00:00:00 UTC | Useful for day-count math, retention windows, and verifying that UTC midnight calculations are behaving the way you expect. |
| Start of 2026 UTC | 1767225600 | 1767225600000 | 2026-01-01 00:00:00 UTC | Common reference point for 2026 docs, test fixtures, migration notes, and any query that asks for a clear epoch to date example. |
| March 2026 UTC midnight | 1772323200 | 1772323200000 | 2026-03-01 00:00:00 UTC | Helpful when you need a clean start-of-month timestamp for reports, billing periods, and SQL filters in 2026. |
| Worked datetime example | 1774708200 | 1774708200000 | 2026-03-28 14:30:00 UTC | Shows the full time component, not just the day, for searchers looking for epoch time to date or epoch to date time examples. |
| End of 2026 UTC | 1798761599 | 1798761599000 | 2026-12-31 23:59:59 UTC | Good boundary case when validating end-of-year reports, cache expiries, and inclusive date-range logic. |
| 32-bit Unix limit | 2147483647 | 2147483647000 | 2038-01-19 03:14:07 UTC | Important for Y2038 debugging. Many searches for unix epoch converter or epoch date appear when legacy systems hit this boundary. |
| Pre-1970 example | -315619200 | -315619200000 | 1960-01-01 00:00:00 UTC | Confirms that negative Unix timestamps are valid when you need historical dates before January 1, 1970 UTC. |
If your value is close to one of these reference points but not exact, paste it into Timestamp to Date and compare it in UTC first. That usually makes unit mistakes, timezone shifts, and start-of-day errors obvious within a few seconds.
Date-specific searches such as unix timestamp for December 31, 2026 or epoch converter September 1, 2026 after January need the reverse path: start with the calendar date, choose UTC or the original timezone, then copy the Unix seconds or milliseconds value. Use the January 1 baseline to compare whether a later 2026 timestamp is after the start of the year.
| Date lookup | UTC date | Epoch seconds | Epoch milliseconds | Comparison check |
|---|---|---|---|---|
| unix timestamp for January 1, 2026 | 2026-01-01 00:00:00 UTC | 1767225600 | 1767225600000 | Baseline for 2026 date comparisons. |
| epoch converter June 20, 2026 after January 2026 | 2026-06-20 00:00:00 UTC | 1781913600 | 1781913600000 | After January 1, 2026 because 1781913600 is greater than 1767225600. |
| epoch converter September 1, 2026 after January 2026 | 2026-09-01 00:00:00 UTC | 1788220800 | 1788220800000 | After January 1, 2026 and before December 31, 2026. |
| unix timestamp for December 18, 2026 after January 2026 | 2026-12-18 00:00:00 UTC | 1797552000 | 1797552000000 | After January 1, 2026 and close to the end-of-year boundary. |
| unix timestamp for December 31, 2026 | 2026-12-31 00:00:00 UTC | 1798675200 | 1798675200000 | Last UTC midnight of 2026 before the final day completes. |
For a date that is not in the table, use Date to Timestamp with the exact timezone first. Use Timestamp to Date only when you already have the Unix number and need to decode it.
Searchers who type epoch to date, epoch time to date, or epoch date often think the raw Unix value is wrong when the converted answer is off by a few hours. In reality, the epoch number stays the same; only the readable display changes when you switch timezone. This comparison table uses the same sample epoch everywhere so you can spot that difference immediately.
| Epoch input | Selected timezone | Readable result | Why this matters |
|---|---|---|---|
| 1774708200 | UTC | 2026-03-28 14:30:00 UTC | Reference output for logs, APIs, databases, and docs that already standardize on UTC. |
| 1774708200 | America/Los_Angeles | 2026-03-28 07:30:00 PDT | Useful when a browser, laptop, or app is rendering the same epoch value in Pacific time. |
| 1774708200 | America/New_York | 2026-03-28 10:30:00 EDT | Common when comparing backend UTC logs against East Coast product or support tooling. |
| 1774708200 | Europe/London | 2026-03-28 14:30:00 GMT | Matches UTC on this specific 2026 example, which helps confirm the raw epoch itself is not changing. |
| 1774708200 | Europe/Berlin | 2026-03-28 15:30:00 CET | Shows how the same epoch date can shift by one hour when a European timezone is selected. |
| 1774708200 | Asia/Tokyo | 2026-03-28 23:30:00 JST | Good reference when a globally shared timestamp must be compared against APAC local time. |
If your converted time looks wrong, keep the epoch input unchanged and switch the Timestamp to Date timezone instead. That resolves most “wrong epoch” reports faster than multiplying, dividing, or editing the original Unix value.
Generic homepage queries like epoch to date, epoch converter, epoch time to date, and unix epoch converter usually begin with a raw value copied from a shell command, language runtime, database query, token payload, or event stream. This expanded reference turns that vague search into the exact conversion path to use on the homepage.
| Source system | Unit | Example value | Typical use | Best conversion path | Why it matters |
|---|---|---|---|---|---|
| Linux or macOS `date +%s` | Seconds | 1767225600 | Shell debugging, cron-adjacent scripts, and server logs | Paste directly into Timestamp to Date | Classic 10-digit Unix seconds. No divide or multiply step is needed. |
| JavaScript `Date.now()` | Milliseconds | 1767225600000 | Browser debugging, Node.js services, and event timestamps | Paste directly and let the converter detect milliseconds | JavaScript emits 13-digit epoch milliseconds by default. |
| Python `int(time.time())` | Seconds | 1767225600 | Python jobs, API clients, and CLI tools | Use Timestamp to Date with no format change | Python examples usually serialize Unix time as whole seconds. |
| Java `System.currentTimeMillis()` | Milliseconds | 1767225600000 | JVM services, Android apps, and queue payloads | Paste into Timestamp to Date as a 13-digit value | Java and Android often store epoch in milliseconds, not seconds. |
| Postgres `extract(epoch from now())` | Seconds with decimals | 1774708200.123 | SQL queries, ETL checks, and analytics exports | Trim or round the decimal part before comparing whole-second values | Database functions often include fractional seconds for sub-second precision. |
| MySQL `UNIX_TIMESTAMP()` | Seconds | 1774708200 | Database filters, scheduled jobs, and reporting queries | Paste directly into Timestamp to Date | MySQL defaults to seconds-based Unix time. |
| JWT `iat` or `exp` claim | Seconds | 1774708200 | Token issue, expiry, and replay-window checks | Convert in UTC to verify the exact security boundary | JWT claims are almost always stored as epoch seconds. |
| Analytics or event pipeline timestamp | Usually milliseconds | 1767225600000 | Client telemetry, clickstreams, and queued events | Paste directly, then compare UTC against local display if needed | Browser-originated pipelines typically mirror JavaScript millisecond values. |
If your job is the reverse and you are starting with a readable calendar time instead of a raw Unix value, jump to Date to Timestamp above and generate the exact seconds or milliseconds format your API, SQL query, or app expects.
Searches like epoch to date, epoch time to date, epoch date, and unix epoch converter usually come down to four problems: the input was milliseconds instead of seconds, the timezone is different from the expected display, a database returned decimal seconds, or the job is actually date to epoch instead of epoch to date. Use this table as a quick debugging reference before you change the raw value.
| What you see | Most likely cause | Fastest fix | Example |
|---|---|---|---|
| The epoch to date result lands in 1970 | A 13-digit milliseconds value was treated like 10-digit epoch seconds, or digits were dropped. | Paste the full value into Timestamp to Date and keep the milliseconds input intact. | 1767225600000 -> 2026-01-01 00:00:00 UTC |
| The converted time is correct but shifted by hours | The epoch value is universal, but the readable date changes with timezone. | Switch the timezone selector to UTC or the original timezone before comparing logs or API output. | 1774708200 -> 2026-03-28 14:30:00 UTC |
| A SQL or Postgres value includes decimals | Database functions often return epoch seconds with fractional milliseconds. | Round or trim the decimal part when you need a whole-second Unix timestamp. | 1774708200.123 -> 1774708200 |
| You searched for epoch date but need the reverse conversion | You have a readable date and time, not an existing Unix value. | Use the Date to Timestamp tool to generate both seconds and milliseconds for that moment. | 2026-03-28 14:30:00 UTC -> 1774708200 |
| An API expects milliseconds but you only have seconds | Different systems store Unix time in different units. | Copy the milliseconds output or multiply the 10-digit seconds value by 1,000. | 1774708200 -> 1774708200000 |
A 10-digit number usually means epoch seconds. A 13-digit number usually means epoch milliseconds. JavaScript's Date.now() returns milliseconds, while Unix shell commands, many SQL functions, and common API payloads still use seconds. The converter above auto-detects both formats so you can go from epoch to date without manually dividing or multiplying by 1,000.
Convert Epoch to Date
Focused guide for turning Unix timestamps into readable UTC or local time.
Convert Time to Epoch
Use a calendar date and timezone to generate Unix seconds or milliseconds.
Milliseconds to Date
Quick path when you already know the value is a 13-digit timestamp.
Current Epoch Time
Open a live current timestamp page for copy-paste debugging.
This FAQ answers the exact homepage search language driving impressions, including epoch converter, epoch to date, epoch time converter, epoch time to date, unix epoch converter, and epoch timestamp to date.
Related Tools
More free tools for developers debugging timestamps, schedules, and text changes.