Maui operates on Hawaii-Aleutian Standard Time year-round
The clock on Maui is always HST, which is UTC-10. No daylight saving time. No seasonal shifts. That is the single most important thing to understand before you try to coordinate anything with anyone on the island. Most people assume Hawaii observes DST because every other US state does. It does not. The Hawaii State Legislature passed a law in 1947 rejecting daylight saving time, and it has stuck ever since. So when mainland California flips its clocks forward in March, Maui stays exactly where it was. When mainland falls back in November, Maui still does not move. Here is how you figure it out without pulling your hair out. Take the current UTC time and subtract 10 hours. That is your Maui time. If you are in New York during standard time, that is UTC-5, so Maui is 5 hours behind New York. During Eastern Daylight Time, New York shifts to UTC-4, making Maui only 4 hours behind. The gap changes depending on whether the mainland is on DST or not. This is where most scheduling mistakes happen. People write down a meeting time assuming the offset stays constant. It does not. I once scheduled a vendor call with a Maui-based team and assumed the 3-hour gap from EST would hold all year. I called at 9 AM Maui time expecting them to be online at 12 PM my time. They were already off the clock at 2 PM my time because they had shifted to the 2-hour gap after Arizona decided to stay on standard time year-round too. I lost three months of consistent scheduling rhythm because I treated time zone math like a static formula instead of something that changes mid-year.
Converting times between Maui and other zones
The practical method is to use UTC as your anchor point rather than trying to memorize every possible offset pair. Convert your local time to UTC first, then subtract 10 for Maui. This double-conversion approach eliminates the error that creeps in when you are mentally juggling shifting offsets across DST boundaries. For example, if it is 3 PM on a Tuesday in Los Angeles during PDT, that is 22:00 UTC. Subtract 10 and you get 12 PM in Maui. Same moment, different mental model, fewer bugs. When scheduling recurring meetings, pick a window that works regardless of which side of DST the mainland is on. A 10 AM to noon Maui window translates to 1 PM to 3 PM Pacific Standard Time or 2 PM to 4 PM Pacific Daylight Time. The window slides by an hour depending on the season, but both teams are always in a reasonable calling range. This is not a theoretical optimization. Teams that lock into a fixed time slot like 10 AM Maui time end up running into the same problem I did: the meeting suddenly lands at an unreasonable hour for half the year.
Tools that actually work for this
World Clock apps are fine for one-off lookups but unreliable for planning. Google Calendar handles multi-timezone events natively and will show you the overlap automatically. TimeAndDate.com has a reliable converter that accounts for historical DST changes. Everytimezone.org is useful for finding overlap windows between two cities. These are the tools I actually use and recommend. Anything more elaborate than these tends to introduce its own parsing bugs. For programmatic solutions, use the IANA timezone database identifier Pacific/Honolulu. This is the canonical key that every major library recognizes. Do not use abbreviations like HST or Hawaii Time in code. They are ambiguous and not consistently parsed across different systems. The IANA identifier is the only thing that is unambiguous. I learned this the hard way when a Python script using "HST" silently fell back to a wrong offset on one deployment server but worked correctly on another. The root cause was inconsistent timezone data packaging between environments.
Get the Full Details
Edge cases and things that break
The most common failure mode is assuming the time difference is constant. It is not. The gap between Maui and the US mainland shifts by one hour twice a year. The gap between Maui and Europe shifts by one hour twice a year for the European side only. Maui never shifts. This asymmetry creates scheduling landmines that are easy to miss if you are not tracking it explicitly. Another edge case involves the International Date Line. Maui is west of the date line but close enough that cross-Pacific scheduling gets weird. A flight departing Maui at 8 AM can arrive in Honolulu the same calendar day at 9:30 AM, but a flight from Maui to Tokyo departs at 11 PM and arrives the next evening at 6 PM Japan time, which is technically still the same calendar day in Hawaii due to the date line crossing. People get tripped up writing confirmation emails that say "see you tomorrow" when the recipient's calendar still shows the same date. Always confirm the actual date in the recipient's local timezone, not yours. There is also the issue of Samoa time. American Samoa uses UTC-11, which is one hour behind Maui. This is often overlooked in logistics planning because the geographic proximity suggests they should share a zone. They do not. The split happened in 2011 when Samoa jumped the International Date Line to align with Australia and New Zealand for trade purposes, leaving American Samoa on the old offset. If you are coordinating shipping or communications between Maui and American Samoa, do not assume they share the same clock.
When the standard approach fails
If you need millisecond precision for system synchronization across Hawaii and other zones, NTP servers that are geographically distant from the equator can introduce latency variation that matters for high-frequency trading or distributed consensus protocols. In those cases, using a local stratum-1 NTP source or hardware timestamping becomes necessary. For almost everything else, the calendar app approach is sufficient and far less painful to maintain. The biggest limitation of treating this as a simple conversion problem is that it ignores human behavior. People in Hawaii still sometimes reference "island time" loosely, meaning roughly whenever you show up. This is not a timezone issue. It is a cultural one. Scheduling a hard 2 PM meeting in Maui and showing up at 2:07 PM is usually fine. Showing up at 2:15 PM without warning is not. Knowing the difference between technical timezone correctness and social timezone expectation is something you learn through repeated failure, not from any conversion tool.
