When displaying a listing of events, each with their own date, time, and timezone, I'd like to present the timezone that the given event has been assigned. However, there is potentially a lot of information to convey. Two options I've considered are:

  1. UTC offset - e.g. 2010-08-16 4:15 pm (+5:00 GMT)
  2. Timezone abbreviation - e.g. 2010-08-16 4:15 pm EST

My problems with these are:

  1. As soon as I see the plus (or minus) with the GMT offset, I feel like I need to do the math. How does the user know if the displayed time has already been adjusted? Also, if daylight saving is in effect for that timezone, this is misleading.
  2. There's information missing here. There are a lot of timezones and I have yet to find an authoritative list of timezone abbreviations. The closest seems to be this TimeAndDate.com list. Alternatively, there is the tz database list, but I don't think users would know what to do with this.

So, my question is, how can I convey which timezone a given event occurs in, given that there is going to be a list of them on the screen?

  • 1
    Just remember to cater to where most of your visitors are coming from. If 99% of your visitors are from India, relating everything to GMT would be a mess. I'm in PST, but if I see something in EST, it's close enough to my time zone I don't have to convert it -- not so with GMT. If your visitors will be from all over the world, maybe GMT would be better. Commented Aug 18, 2010 at 2:23
  • UTC offset != time zone. Many time zones switch offset depending whether DST is in effect, so UTC offsets are not sufficient. Commented Oct 6, 2011 at 23:25

6 Answers 6


Time zones are a great example of horrible UX in everyday concepts. It's not DMMT: if you tell me an event is at 7pm GMT+4, then first I have to think of where I am in relation to GMT, and then I have to add 4 hours. What a mess!

Instead, think of the different things you can do with time if you're able to calculate or design. For instance:

  • Show a map with a pin in your location and a pin in the event's location with a ticking digital clock above each pin showing what time it is in each location. This works well if you have an event overview page and you know who the logged in user is.
  • Do the work for me and say "(this event takes place at) 3:15 AM on Thursday, your time" in plain English. Or if you're in a table, put "Takes place at (your time)" in the column header and just print "3:15 AM on Thursday" in the cell. This works well for notifications or streams.
  • Use relative time to avoid having to be specific (this depends on the use case obviously). If dates are far in the future, who cares what time they are? Just say "in 2 weeks". If they're within a certain margin, get more specific: "in 3h44m". Those time should be relative to the user's time zone.
  • Still need to display time zones (for some reason)? Display a map like this one:

map of timezones

And perhaps highlight the time zone the event takes place in when the user hovers over an event in the list. You could even combine that with my first suggestion.

Ideally though, use plain English and rely on real-world metaphors as much as you can to display information. Obviously you have a constraint: you need to show information concisely in a list. But that's the challenge for this design.


One quick comment on using the three letter abbreviations - be careful not to use them as the sole indicator of the timezone since there are cases where timezones have the same three letter abbreviation.

For example EST can mean any of:

  • Eastern Summer Time Australia UTC + 11 hours
  • Eastern Standard Time Australia UTC + 10 hours
  • Eastern Standard Time North America UTC - 5 hours

if your really have to, don't show time zone info but the city associated with the event (or the time zone if no location is provided).

Better, don't show time zones at all. What does it matter if I'm in time zone X, as a user I want it all normalized to my time zone. You loose track of concurrency if you show multiple time zones on one screen.

Ideally you normalize the time zone and provide a simple to view ti in another time zone. So if I want to plan something that some of the participants are in another time zone, let me see when in the day this meeting will be in that other time zone with a simple slider, that moves to countries or to cities around the globe.

  • 2
    I like your "better" solution - just show the time in the user's local time. However, it might not always be possible to tell...
    – Dan Barak
    Commented Aug 17, 2010 at 21:30
  • 4
    Usually I'd say normalize to the users time zone, but it would be weird reading a news article about 9/11 in England that said it happened at 3PM. Commented Aug 18, 2010 at 2:18
  • 1
    Love the city idea (I would use state/country), but I hate normalized times - this always ends up displaying someting that is either complete nonsense (like showing the local time at my home town for a face-to-face meeting at teh otehr side of the world) or plain wrong (normelized time + daylight saving time change = being one hour late for a meeting)
    – Nir
    Commented Aug 18, 2010 at 14:09
  • 1
    I created an application which deals with flights between timezones. We wanted to keep it as simple as possible and simply display the local time at a particular event. But that means a later event sometimes can appear to be at an earlier time. So I realized it's crucial to show in a clear way when a change of time zone occurs, so there is an obvious "before and after" in the list. But I agree most users shut down when they see the time offset or official tz name.
    – Felixyz
    Commented Aug 19, 2010 at 9:36

I like the abbreviations with the offset.

Tuesday, August 17, 2010 4:30pm EDT (GMT -4)

That allows me to automatically associate with the time zones I am familiar with and do the math for the ones I don't know. Also if you can't find a name for a timezone it doesn't look out of place if you put the offset.

Another bonus to this is during daylight savings time. EST which is GMT -5 becomes GMT -4. By putting the number this will remind me of this.

Another issue though is UTC or GMT. UTC seems to be more correct these days but I am used to GMT, so I prefer that.

  • Daylight saving time has its own abbreviations since not all locations follow it. So EST becomes EDT when daylight saving time is in effect. Also, UTC is pretty universally (pardon the pun) preferred to GMT from my understanding. Commented Aug 17, 2010 at 21:12
  • Notice the first date I posted (EDT GMT -4)
    – Sruly
    Commented Aug 18, 2010 at 9:30
  • 2
    The difference between UTC and GMT is that GMT has daylight saving time. UTC does not. Commented Aug 24, 2010 at 1:13

When an explicit time offset needs to be displayed, the World Wide Web Consortium generally aligns its standard for time zones with ISO 8601. That is to say, they prefer "[time] UTC(+/-)hh:mm".

Alternatively, if you don't want to use UTC, they suggest using the CLDR unicode library to get "Country/Major City" formatted identifiers (e.g. "America/Los Angeles") which identify the country's daylight savings rules and the relative time.


For letting the user know if the time has already been adjusted - I think you need to be consistent; either all times listed should be adjusted (in which case you probably don't need to have the timezone information displayed) or all times should not be adjusted (in which case the most descriptive timezone information should be used, like +5 GMT).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.