Manila Time, PhST and US Shifts: Time Zones for Developers
Manila stays on UTC+8 all year, so US accounts shift by an hour twice a year. Asia/Manila in code, the PST mix-up, PAGASA time and 2026 shift dates.
By Redbison Dev · · 6 min read

Philippines edition. Written for developers and BPO teams in the Philippines: Philippine Standard Time under RA 10535 and PAGASA's time service, the Asia/Manila zone, PhST versus Pacific Standard Time, and 2026 US and UK changeover dates. US edition
The Philippines never changes its clocks. Manila is UTC+8 in January and UTC+8 in July, so when a US account's 9:00 AM New York start moves from 10:00 PM to 9:00 PM Manila time in March, the change came from the US side. For developers building schedulers, rosters and dashboards for Philippine teams, that one-sided change is the main source of bugs, along with an abbreviation that means two different things. This edition covers how Philippine time is defined, how to handle Asia/Manila in code, and the 2026 dates when US and UK schedules move. Every conversion can be repeated in the Manila time converter.
How Philippine Standard Time is defined
Republic Act No. 10535, the Philippine Standard Time (PST) Act of 2013, signed on May 15, 2013, makes PAGASA's Time Service Unit, with the Department of Science and Technology, responsible for monitoring, maintaining and distributing official time. National and local government offices must display Philippine Standard Time and synchronize with PAGASA at least monthly, and the first week of each year is National Time Consciousness Week.
PAGASA's astronomy page uses the acronym PhST, noting that it distinguishes Philippine Standard Time from Pacific Standard Time. Its time service runs on three cesium clocks steered to UTC, and it publishes an NTP server, ntp.pagasa.dost.gov.ph, for synchronizing computers. Official time devices may deviate by up to plus or minus five seconds.
In the IANA time zone database, used by browsers, phones and servers, the zone is Asia/Manila, at UTC+8 on every date in the converter.
The PST problem
The act's own short title calls it "PST". To nearly every US colleague, client and calendar app, PST is Pacific Standard Time, UTC−8, which is 16 hours behind Manila. An email that says "the call is at 10 AM PST" is ambiguous by a day.
- In your UI, write PhST, or better, the zone and offset: "10:00 PM PhST (UTC+8)".
- Never parse "PST" into an offset. The IANA project's notes say abbreviations "are ambiguous in practice". Store
Asia/ManilaorAmerica/Los_Angelesexplicitly. - When a client writes PST, check the date. Los Angeles is actually on PDT (UTC−7) from March to November, so "PST" in a summer email is probably loose usage for Pacific time.
US shifts move twice a year
The US moves its clocks forward on the second Sunday of March and back on the first Sunday of November, which in 2026 means March 8 and November 1. Manila stays put, so every shift anchored to a US start time moves:
| US start | Manila, January 15, 2026 | Manila, July 15, 2026 |
|---|---|---|
| 9:00 AM New York | 10:00 PM | 9:00 PM |
| 8:00 AM Chicago | 10:00 PM | 9:00 PM |
| 6:00 AM Los Angeles | 10:00 PM | 9:00 PM |
Run it the other way and the shift that starts at 10:00 PM Manila time is 9:00 AM in New York on January 15, 2026, but 10:00 AM on July 15, 2026.
Worked example: a weekly roster across the March change. A support team starts at 10:00 PM Manila time to cover a 9:00 AM New York opening. On Friday, March 6, 2026, 10:00 PM in Manila is 9:00 AM in New York. On Monday, March 9, after the US change, 10:00 PM in Manila is 10:00 AM in New York, an hour late for the client. Either the roster moves to 9:00 PM from March 9 until November 1, or the client's opening time moves. Rostering software should store the anchor as "09:00 America/New_York" and compute the Manila start for each date, rather than storing "22:00 Asia/Manila".
The November change is a trap of its own. In New York, 1:30 AM on November 1, 2026 happens twice. The converter resolves it to the first occurrence, 1:30 AM EDT, which is 1:30 PM in Manila. Night jobs that run on US time can fire twice or be skipped on the change nights; schedule them in UTC or in Asia/Manila, which has no change nights.
The UK, the Middle East and Australia
- UK accounts move on the last Sundays of March and October (March 29 and October 25 in 2026). A 9:00 AM London call is 5:00 PM in Manila on January 15, 2026 and 4:00 PM on June 15, 2026.
- Gulf and Saudi Arabia: on December 10, 2026, 9:00 AM in Manila is 5:00 AM in Dubai (UTC+4) and 4:00 AM in Riyadh (UTC+3).
- Australia moves the other way. 9:00 AM in Manila is 12:00 PM in Sydney on December 10, 2026 (UTC+11) and 11:00 AM on June 10, 2026 (UTC+10).
Habits for Philippine systems
- Log in UTC. A log at 22:00 Manila time is 14:00 UTC; write the
Zand convert for display. - Store client-anchored events in the client's zone. The shift that must match a New York opening is stored in
America/New_York. - Use US date order with care. The Philippines writes dates month first, like the US, but partners in the UK, India or Australia write day first. In data exchange, use ISO 8601 (2026-03-09) to avoid 03/09 being read two ways.
- Synchronize clocks. Point servers and kiosks at a reliable NTP source such as PAGASA's, and keep the system clock in UTC.
- Keep tz data current. Manila's rules are stable, but your clients' rules can change, and devices only learn about it through tz data updates.
Tools for this job
- Manila time converter: a meeting or shift time between Manila and the US, UK and other zones on any date.
- World clock: live times for your team and your accounts side by side.
- Epoch converter: Unix timestamps to UTC and Manila time.
- Cron expression generator: check when a scheduled job fires.
For counting days and durations, see the guide to date math.
Frequently asked questions
Does the Philippines have daylight saving time?
No. Manila stays on UTC+8 all year, so any change in the gap to the US, UK or Australia comes from those countries changing their clocks.
How many hours is Manila ahead of New York?
13 hours while New York is on Eastern Standard Time, from early November to early March, and 12 hours while it is on daylight time. In 2026 the 12-hour period runs from March 8 to November 1.
Is PST the same as Philippine time?
Not to US software or US clients. RA 10535 uses "PST" for Philippine Standard Time, but PAGASA uses PhST to avoid confusion with Pacific Standard Time (UTC−8). Write PhST or UTC+8.
What NTP server gives official Philippine time?
PAGASA publishes ntp.pagasa.dost.gov.ph as its time server for synchronizing computers to Philippine Standard Time.
Sources and further reading
- Astronomy: Time Service and Philippine Standard Time, PAGASA. PhST, the cesium clock time scale, the NTP server and the five-second tolerance.
- Republic Act No. 10535: The Philippine Standard Time (PST) Act of 2013, Lawphil. PAGASA's role, the duty of government offices to synchronize, and National Time Consciousness Week.
- Daylight Saving Time Rules, NIST. The US rule and the 2026 dates.
- When do the clocks change?, GOV.UK. The UK rule and dates.
- Theory and pragmatics of the tz code and data, IANA. Why abbreviations are ambiguous and how zones are named.
- Time Zone Database, IANA. The data behind Asia/Manila.
More Time Tools
Every tool in the Time Tools section, free and in your browser.