San Francisco is 8 hours behind UTC in winter and 7 hours behind UTC in summer — 8 hours behind UTC in winter. Its standard offset is UTC−08:00, moving to UTC−07:00 when daylight saving is in effect. This page explains the difference, shows it month by month, and gives the conversion tables in both directions.
Try the tool: UTC Converter — convert any time between UTC and San Francisco, with the offset for the date you pick.
How far is San Francisco from UTC?
The difference between San Francisco and UTC is the offset: UTC−08:00 in standard time and UTC−07:00 in daylight saving time. When it is noon in San Francisco, it is already afternoon or evening in London — the day at Greenwich is 8 hours ahead the day in San Francisco. The sign matters: a positive offset means ahead of UTC (east of Greenwich), a negative offset means behind it (west of Greenwich).
In practical terms, the difference means that the working day in San Francisco (09:00–17:00 local) is 17:00–01:00 UTC in January and 16:00–00:00 UTC in July. A team that schedules in UTC needs to know both numbers, because a meeting set for 15:00 UTC is 07:00 in San Francisco in January and 08:00 in July — and one of those may be outside the working day even when the other is inside it.
San Francisco vs UTC through the year
The offset on the 15th of each month in 2026. If the table shows one value all year, San Francisco does not observe daylight saving. If it shows two values, the change between them is the clock change.
| Month | Offset from UTC |
|---|---|
| January | UTC−08:00 |
| February | UTC−08:00 |
| March | UTC−07:00 |
| April | UTC−07:00 |
| May | UTC−07:00 |
| June | UTC−07:00 |
| July | UTC−07:00 |
| August | UTC−07:00 |
| September | UTC−07:00 |
| October | UTC−07:00 |
| November | UTC−08:00 |
| December | UTC−08:00 |
The clock changes are: in 2026, Sunday, 8 March 2026, Sunday, 1 November 2026; in 2027, Sunday, 14 March 2027, Sunday, 7 November 2027. For the full story, see the San Francisco DST 2026 page and the daylight saving checker.
Conversion tables
UTC to San Francisco, for eight hours of the day:
| UTC | San Francisco (January) | San Francisco (July) |
|---|---|---|
| 00:00 | 16:00 | 17:00 |
| 03:00 | 19:00 | 20:00 |
| 06:00 | 22:00 | 23:00 |
| 09:00 | 01:00 | 02:00 |
| 12:00 | 04:00 | 05:00 |
| 15:00 | 07:00 | 08:00 |
| 18:00 | 10:00 | 11:00 |
| 21:00 | 13:00 | 14:00 |
San Francisco to UTC, for the same eight hours:
| San Francisco local | UTC (January) | UTC (July) |
|---|---|---|
| 00:00 | 08:00 | 07:00 |
| 03:00 | 11:00 | 10:00 |
| 06:00 | 14:00 | 13:00 |
| 09:00 | 17:00 | 16:00 |
| 12:00 | 20:00 | 19:00 |
| 15:00 | 23:00 | 22:00 |
| 18:00 | 02:00 | 01:00 |
| 21:00 | 05:00 | 04:00 |
Two things to watch in these tables. First, the date: a UTC time in the evening is the next day in San Francisco when the offset is positive — 21:00 UTC is 13:00 the next day in San Francisco in January — and a San Francisco time early in the morning is the previous day in UTC when the offset is positive. Second, the season: the January and July columns differ by an hour, which is daylight saving. The UTC to San Francisco page has the full 24-hour table.
Daylight saving and the difference
San Francisco observes daylight saving, so the difference from UTC is not constant. In 2026 the clocks go forward on Sunday, 8 March 2026 and back on Sunday, 1 November 2026; in 2027 the clocks go forward on Sunday, 14 March 2027 and back on Sunday, 7 November 2027. Between those dates the difference is 7 hours behind UTC; outside them it is 8 hours behind UTC. The change happens at 2am local time in most places, so the hour from 02:00 to 03:00 does not exist on the spring change day and happens twice on the autumn change day.
What the difference means for scheduling
For a team that works in UTC — software, aviation, science — the difference is the number you add to every UTC time to get San Francisco time, and the number you subtract from every San Francisco time to get UTC. The mistake is to use one number all year when there are two. The safe habit is to put the UTC time in every invitation as well as the local time, and to let the calendar do the conversion: a calendar event set in UTC moves correctly when daylight saving changes, and an event set in local time does not always.
For comparison, two other major cities: London is the same time UTC in January and 1 hour ahead UTC in July, and Tokyo is 9 hours ahead UTC all year. San Francisco's difference of 8 hours behind (January) sits between them in the sense that matters for scheduling: a meeting at 14:00 UTC is 06:00 in San Francisco, 14:00 in London and 23:00 in Tokyo in January. The time in San Francisco page has the working-hours tables, and the meeting planner finds the overlap for any pair of cities.
San Francisco vs UTC: the numbers at a glance
| Fact | Value |
|---|---|
| Standard offset | UTC−08:00 |
| Daylight saving offset | UTC−07:00 |
| Offset in January 2026 | UTC−08:00 |
| Offset in July 2026 | UTC−07:00 |
| Difference from UTC in January | 8 hours behind |
| Difference from UTC in July | 7 hours behind |
| IANA time zone | America/Los_Angeles |
| Country | United States |
Adjusting to the difference — travel and jet lag
Travelling to San Francisco from London means setting your watch back by 8 hours in January — you gain time going west, and the first day feels long. Travelling the other way, from San Francisco to London, you lose the hours. The rule of thumb for jet lag is that it takes about a day to adjust for each hour of difference when travelling east, and a little less when travelling west — so the return trip from San Francisco to London takes most travellers about 8 days to fully adjust to, while the outward trip is usually easier. The practical advice is the same in both directions: get sunlight in the morning at your destination, avoid naps longer than 20 minutes, and do not schedule important meetings for the first morning after you arrive.
The same arithmetic applies to remote work. If you are in San Francisco and your team works in UTC, your working day of 09:00–17:00 local time is 17:00–01:00 UTC in January — so a stand-up at 09:00 UTC is 01:00 for you, and a stand-up at 16:00 UTC is 08:00. If those times are outside your working day, the meeting is in the wrong place in the day, and the fix is to move the UTC time, not to ask one person to work at midnight. The meeting time finder finds the hours that work for a whole team, and the time in San Francisco page has the working-hours tables.
Frequently asked questions
How many hours is San Francisco ahead of UTC?
San Francisco is 8 hours behind UTC in January and 7 hours behind UTC in July. The difference changes with daylight saving.
Is San Francisco ahead of or behind UTC?
San Francisco is behind UTC — its offset is negative (UTC−08:00 in January), so local time is earlier than UTC.
Does the time difference between San Francisco and UTC change?
Yes — it is 8 hours behind in standard time and 7 hours behind in daylight saving time. In 2026 the clocks go forward on Sunday, 8 March 2026 and back on Sunday, 1 November 2026.
What is San Francisco's UTC offset?
San Francisco's standard offset is UTC−08:00, and its daylight saving offset is UTC−07:00. Its IANA time zone is America/Los_Angeles.
When it is midnight UTC, what time is it in San Francisco?
It is 16:00 in January and 17:00 in July — the previous day, because the offset is negative.
Sources
- IANA Time Zone Database, via Node.js Intl (
Intl.DateTimeFormatwithtimeZone) — offsets, daylight saving dates and local times in this article were worked out from the IANA database, not typed from memory. - TimeFlow's own time-zone data (
data/cities.ts,data/dst.ts), computed from the IANA database. - TimeFlow's UTC converter and world clock — the live tools behind the numbers on this page.
- Time-zone and daylight saving rules are set by governments and can change. For flights, deadlines and meetings that cannot move, confirm the time with an official source.