Explore · time zones
PKT to PST converter
Pakistan Standard Time (Karachi) → Pacific Time (Los Angeles)
Quick answer
The difference changes with daylight saving time. Los Angeles is 13 hours behind Karachi from Jan 1, 2026 to Mar 8, 2026 10:00 UTC (Los Angeles on PST · UTC−8); 12 hours behind Karachi from Mar 8, 2026 10:00 UTC to Nov 1, 2026 09:00 UTC (Los Angeles on PDT · UTC−7); 13 hours behind Karachi from Nov 1, 2026 09:00 UTC to Dec 31, 2026 (Los Angeles on PST · UTC−8).
- Jan 1, 2026 to Mar 8, 2026 10:00 UTCKarachi (PKT, UTC+5) → Los Angeles (PST, UTC−8)Los Angeles is 13 hours behind Karachi
- Mar 8, 2026 10:00 UTC to Nov 1, 2026 09:00 UTCKarachi (PKT, UTC+5) → Los Angeles (PDT, UTC−7)Los Angeles is 12 hours behind Karachi
- Nov 1, 2026 09:00 UTC to Dec 31, 2026Karachi (PKT, UTC+5) → Los Angeles (PST, UTC−8)Los Angeles is 13 hours behind Karachi
9:00 AM PKT (UTC+5) in Karachi is 8:00 PM PST (UTC−8) in Los Angeles, the previous day. Los Angeles is 13 h behind Karachi.
| Format | Result | Copy |
|---|---|---|
| Los AngelesPST · UTC−8 · Tuesday, January 13, 2026 · the previous day | 8: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768363200 | |
| RFC 2822UTC | Wed, |
Conversions use Karachi (Asia/Karachi) and Los Angeles (America/Los_Angeles). Other cities reached through search aliases may have different historical rules.
Current time in Karachi and Los Angeles
Hour by hour: Karachi (PKT, UTC+5) → Los Angeles (PST, UTC−8)
There is no time when both Karachi and Los Angeles are inside 9:00–17:00.
| Karachi | Los Angeles | Day |
|---|---|---|
| 12:00 AM | 11:00 AM | previous day |
| 1:00 AM | 12:00 PM | previous day |
| 2:00 AM | 1:00 PM | previous day |
| 3:00 AM | 2:00 PM | previous day |
| 4:00 AM | 3:00 PM | previous day |
| 5:00 AM | 4:00 PM | previous day |
| 6:00 AM | 5:00 PM | previous day |
| 7:00 AM | 6:00 PM | previous day |
| 8:00 AM | 7:00 PM | previous day |
| 9:00 AM | 8:00 PM | previous day |
| 10:00 AM | 9:00 PM | previous day |
| 11:00 AM | 10:00 PM | previous day |
| 12:00 PM | 11:00 PM | previous day |
| 1:00 PM | 12:00 AM | same day |
| 2:00 PM | 1:00 AM | same day |
| 3:00 PM | 2:00 AM | same day |
| 4:00 PM | 3:00 AM | same day |
| 5:00 PM | 4:00 AM | same day |
| 6:00 PM | 5:00 AM | same day |
| 7:00 PM | 6:00 AM | same day |
| 8:00 PM | 7:00 AM | same day |
| 9:00 PM | 8:00 AM | same day |
| 10:00 PM | 9:00 AM | same day |
| 11:00 PM | 10:00 AM | same day |
Hour by hour: Karachi (PKT, UTC+5) → Los Angeles (PDT, UTC−7)
There is no time when both Karachi and Los Angeles are inside 9:00–17:00.
| Karachi | Los Angeles | Day |
|---|---|---|
| 12:00 AM | 12:00 PM | previous day |
| 1:00 AM | 1:00 PM | previous day |
| 2:00 AM | 2:00 PM | previous day |
| 3:00 AM | 3:00 PM | previous day |
| 4:00 AM | 4:00 PM | previous day |
| 5:00 AM | 5:00 PM | previous day |
| 6:00 AM | 6:00 PM | previous day |
| 7:00 AM | 7:00 PM | previous day |
| 8:00 AM | 8:00 PM | previous day |
| 9:00 AM | 9:00 PM | previous day |
| 10:00 AM | 10:00 PM | previous day |
| 11:00 AM | 11:00 PM | previous day |
| 12:00 PM | 12:00 AM | same day |
| 1:00 PM | 1:00 AM | same day |
| 2:00 PM | 2:00 AM | same day |
| 3:00 PM | 3:00 AM | same day |
| 4:00 PM | 4:00 AM | same day |
| 5:00 PM | 5:00 AM | same day |
| 6:00 PM | 6:00 AM | same day |
| 7:00 PM | 7:00 AM | same day |
| 8:00 PM | 8:00 AM | same day |
| 9:00 PM | 9:00 AM | same day |
| 10:00 PM | 10:00 AM | same day |
| 11:00 PM | 11:00 AM | same day |
Worked examples
| When | Karachi | Los Angeles | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 7:00 PM PKT (UTC+5), January 14, 2026 | 6:00 AM PST (UTC−8), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 7:00 PM PKT (UTC+5), July 15, 2026 | 7:00 AM PDT (UTC−7), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 5:00 AM PKT (UTC+5), January 1, 2027 | 4:00 PM PST (UTC−8), December 31, 2026 | 2027-01-01T00:00:00.000Z | 1798761600 |
The ISO 8601 and Unix columns are the same instant written without a zone — how APIs and databases should store it. Need this for a whole column? Convert a CSV file.
PKT — Pakistan Standard Time
- IANA identifier
- Asia/Karachi
- UTC offset
- PKT · UTC+5
- Daylight saving
- Not observed
- On this clock today
- Karachi, Lahore, Islamabad
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Asia/Karachi; a listed place's past or future rules may differ.
UTC+5 all year.
PST — Pacific Time
- IANA identifier
- America/Los_Angeles
- Standard time
- PST · UTC−8
- Daylight time
- PDT · UTC−7
- On this clock today
- Los Angeles, San Francisco, Seattle, San Diego, Portland
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Los_Angeles; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 8, 2026, 3:00 AM local (2026-03-08 10:00 UTC): clocks go forward to UTC−7 (PDT)
- Nov 1, 2026, 1:00 AM local (2026-11-01 09:00 UTC): clocks go back to UTC−8 (PST)
- Mar 14, 2027, 3:00 AM local (2027-03-14 10:00 UTC): clocks go forward to UTC−7 (PDT)
- Nov 7, 2027, 1:00 AM local (2027-11-07 09:00 UTC): clocks go back to UTC−8 (PST)
PST here is North American Pacific Standard Time (UTC−8), with PDT (UTC−7) in summer. Philippine Standard Time (UTC+8) is on the Manila page. British Columbia (Vancouver) stays on UTC−7 all year from 2026 and is not on this clock.
Related conversions
File workspace
Converting a whole column of timestamps?
The free converter handles one value at a time across 82 formats and 92 zones. The file workspace converts an entire CSV column between any two formats and zones, previews the first rows, and leaves unreadable cells exactly as they were.
Offsets and change dates on this page are computed from IANA time zone database 2026f for 2026–2027; the live tool uses the same data.