EpochTools

Current epoch time in United States (Pacific)

America/Los_Angeles · United States (Pacific)

Current Unix timestamp live

0

–

–

Epoch to America/Los Angeles converter

Timestamps below are shown in America/Los Angeles. The unit is auto-detected from the input.

Seconds or milliseconds — the unit is auto-detected. Example: 1735689600

Waiting for input…

UTC ISO 8601

–

Local — auto

–

RFC 2822 / GMT

–

Seconds value

–

Relative time

–

UTC offset

UTC-07:00

Abbreviation: PDT

Daylight saving

Observed

Jan UTC-08:00 · Jul UTC-07:00

Region

United States (Pacific)

IANA: America/Los_Angeles

Next offset change

2026-11-01

→ UTC-08:00

Reference conversions for America/Los Angeles

The same Unix timestamps converted to America/Los Angeles time (UTC-07:00, PDT) — useful as a quick sanity-check table while you work.

Unix timestamp (seconds) UTC (ISO 8601) America/Los Angeles (PDT)
0 1970-01-01T00:00:00.000Z 12/31/1969, 16:00:00 PST
946,684,800 2000-01-01T00:00:00.000Z 12/31/1999, 16:00:00 PST
1,754,136,000 2025-08-02T12:00:00.000Z 08/02/2025, 05:00:00 PDT
2,147,483,647 2038-01-19T03:14:07.000Z 01/18/2038, 19:14:07 PST
2,524,608,000 2050-01-01T00:00:00.000Z 12/31/2049, 16:00:00 PST
1,787,458,618 2026-08-23T04:16:58.673Z 08/22/2026, 21:16:58 PDT

Using America/Los Angeles in real projects

United States (Pacific) runs on America/Los_Angeles, which is UTC-07:00 (with daylight saving moving it to UTC-07:00 part of the year). Whenever your app stores a Unix timestamp and then displays it to a user in United States (Pacific), you should convert using an IANA timezone identifier like America/Los_Angeles rather than a hard-coded offset — the OS keeps the DST rules up to date for you.

For example, an event logged at 2038-01-19T03:14:07.000Z UTC renders as 01/18/2038, 19:14:07 PST in America/Los Angeles. The same number means a different wall-clock time in London, Tokyo or New York — which is exactly why storing the epoch value is the safe, portable choice. See how in the JavaScript timestamp guide or the Python epoch converter guide.

Frequently asked questions

What is the current UTC offset for America/Los Angeles?

America/Los Angeles (America/Los_Angeles) is currently at UTC-07:00, usually written as PDT. Because a Unix timestamp counts seconds since 1970-01-01T00:00:00Z, converting it to America/Los Angeles means adding the offset shown above.

Does America/Los Angeles observe daylight saving time?

Yes. America/Los Angeles switches between UTC-08:00 in the standard part of the year and UTC-07:00 during daylight saving time, so the abbreviation changes too. The next scheduled change is 2026-11-01, when the offset becomes UTC-08:00.

How do I convert a Unix timestamp to America/Los Angeles?

Take the epoch seconds value and add -07:00 (PDT) to get the wall-clock time in America/Los Angeles. The converter on this page does that instantly for any timestamp, and shows the UTC value alongside so you can compare.

Why is a Unix timestamp the same in America/Los Angeles as everywhere else?

The Unix epoch is an absolute instant, not a wall-clock reading. The number is identical no matter where you read it — only the human-readable date and time changes depending on the timezone. America/Los Angeles (America/Los_Angeles) is one of the IANA identifiers used to pick the right offset automatically.

What programming languages handle America/Los Angeles automatically?

Every modern language reads IANA timezones like America/Los_Angeles natively — from Date and Intl in JavaScript, to zoneinfo in Python, time in PHP, java.time in Java and time.Time in Go. Grab copy-paste code on the America/Los Angeles conversion snippets to get started.

About America/Los Angeles

America/Los Angeles (America/Los_Angeles) is one of the IANA timezones supported by the converter above. IANA identifiers are the standard way to refer to timezones in programming languages and databases — they handle daylight saving transitions automatically.

Convert epoch to America/Los Angeles

The Unix epoch is a single instant in time that looks the same in every timezone — only its wall-clock representation changes. The converter above shows the same timestamp formatted in America/Los Angeles (as well as UTC), so you can see exactly what a given epoch value means in this part of the world.

Looking for another zone? Browse the full list on the timezone index.