I have a server running with the timezone set to UTC. It seemed like that was generally a good practice (please correct me if I'm wrong).

Anyhow, one of the servers I connect to, in order to scp files, is running on EDT and stores files that I need to copy in the format /path/to/filename/data20120913

I looked at trying to rsync files using something like find's -mtime -1 flag for files modified in the last day, but I didn't have any luck.

I don't mind just using scp to copy the current day's file, but as of right now there is a 4-hour window where running date +%Y%m%d will give a different day on each server and that bugs me a little.

Looking through man date I see that I can have the time output as UTC, but I don't see a way to have it output as another timezone like EDT

I suppose I could also use something like the GNU date extension date -d 20100909 +%s to get the date in seconds from the epoch, apply a manual 4 * 60 * 60 second calculation, and see about rendering that as a date - but then when daylight time kicks in it will still be an hour off.

Is there a simpler way to output the date in a YYYYMMDD format for EDT on a server that is set to UTC ?

  • EDT is not a recognized timezone- in Linux, at least. See my "Be careful!" answer below for the whole ugly story. If EDT is recognized on your brand of *NIX, you should still exercise caution and double-check your timezone string. – Mike S Mar 17 '15 at 15:27
  • See also this answer which searches /usr/share/zoneinfo and shows the time in zones matching your query. – mivk Jan 15 '20 at 12:17

You can set a timezone for the duration of the query, thusly:

TZ=America/New_York date

Note the whitespace between the TZ setting and the date command. In Bourne-like and rc-like shell, that sets the TZ variable only for the command line. In other shells (csh, tcsh, fish), you can always use the env command instead:

env TZ=America/New_York date


On Linux systems. timezones are defined in files in the /usr/share/zoneinfo directory. This structure is often referred to as the "Olson database" to honor its founding contributor.

The rules for each timezone are defined as text file lines which are then compiled into a binary file. The lines so compiled, define the zone name; a range of data and time during which the zone applies; an offset from UTC for the standard time; and the notation for defining how transition to-and-from daylight saving time occurs, if applicable.

For example, the directory "America" contains the requisite information for New York in the file America/New_York as used, above.

Beware that the specification of a non-existent zone (file name) is silently ignored and UTC times are reported. For example, this reports an incorrect time:

TZ="America/New York" date ### WRONG ###

The Single UNIX Specification, version-3, known as SUSv3 or POSIX-2001, notes that for portability, the character string that identifies the timezone description should begin with a colon character. Thus, we can also write:

TZ=":America/New_York" date
TZ=":America/Los_Angeles" date

As an alternative method to the specification of timezones using a pathname to a description file, SUSv3 describes the POSIX model. In this format, a string is defined as:

std offset [dst[offset][,start-date[/time],end-date[/time]]]

where std is the standard component name and dst is the daylight saving one. Each name consists of three or more characters. The offset is positive for timezones west of the prime meridian and negative for those east of the meridian. The offset is added to the local time to obtain UTC (formerly known as GMT). The start and end time fields indicate when the standard/daylight transitions occur.

For example, in the Eastern United States, standard time is 5-hours earlier than UTC, and we can specify EST5EDT in lieu of America/New_York. These alternatives are not always recognized, however, especially for zones outside of the United States and are best avoided.

HP-UX (an SUSv3 compliant UNIX) uses textual rules in /usr/lib/tztab and the POSIX names like EST5EDT, CST6CDT, MST7MDT, PST8PDT. The file includes all of the historical rules for each time zone, akin to the Olson database.

NOTE: You should be able to find all of the timezones by inspecting the following directory: /usr/share/zoneinfo.

  • not sure if am I wrong, but export looks better than env command – insign Dec 23 '17 at 15:58
  • @JRFerguson - If a timezone is not included in the list e.g. Las Vegas or Nevada, what are the alternatives in validating the time? – Motivated Jan 31 '19 at 16:26
  • @Motivated If your city or state isn't included, choose one that uses the same zone info as yours. For instance, I'm in Florida, which uses the same timezone as New York, so my machines synchronize to New York time. – JRFerguson Jan 31 '19 at 17:45
  • 1
    @JRFerguson - That assumes that the person is aware of the various timezones and is able to use an alternative e.g. New York in your case. Would that be the only option? For example, i don't live in Europe and i won't know the overlapping timezones. – Motivated Jan 31 '19 at 17:49
  • 1
    @Motivated You can use something like this site to assist you in finding other points in your zone. – JRFerguson Jan 31 '19 at 17:53

You can do this by manipulating the TZ environment variable. The following will give you the local time for US/Eastern, which will also be smart enough to handle DST when that rolls around:

# all on one line
TZ=":US/Eastern" date +%Y%m%d

The zone name comes from the files and directories inside /usr/share/zoneinfo.


Be careful! Date will happily spit out the time in your CURRENT timezone, if you give it a timezone it doesn't recognize.

Check this out:

-bash-4.2$ env TZ=EDT date
Wed Feb 18 19:34:41 EDT 2015
-bash-4.2$ date
Wed Feb 18 19:34:43 UTC 2015

Note that there is no timezone called EDT. As a matter of fact,

-bash-4.2$ find /usr/share/zoneinfo -name "*EDT*"



And this works:

-bash-4.2$ TZ=EST5EDT date
Wed Feb 18 14:36:59 EST 2015
-bash-4.2$ date
Wed Feb 18 19:37:01 UTC 2015

However, if your friend lives in the mystic land of Gobbledygook and its zone info coincides with your own, you can have date output the time in Gobbledygook's zone and it will be happy to do so with nary an exit value to let you know that the zone is not known to it:

-bash-4.2$ TZ=Gobbledygook date
Wed Feb 18 19:37:36 Gobbledygook 2015
-bash-4.2$ echo $?
  • 1
    YMMV: on my MacOS/BSD box, malformed TZ string returns UTC time. – Mark Hudson Sep 20 '19 at 17:40
  • +1 for "mystic land of Gobbledygook" 😂 – Leo Galleguillos Feb 26 '20 at 4:54
TODAY=$(TZ=":US/Eastern" date)
echo $TODAY

The date syntax is arcane and error-prone, which makes a command-line invocation a pain. I therefore wrote a small script (I named it worldtime), which will print the specified (or current) time from base time zome (your local one) in some other time zones and the converse.

Here it is. Adjust it to match your needs, put it in your path, and make it executable.

# Print the specified (or current) time from base time in other time zones
# and the converse

# Base time zone from/to which to convert

# Time zones to display
# See /usr/share/zoneinfo/ for more names
TZONES='UTC America/Los_Angeles America/New_York Europe/London Europe/Paris'

# Display format
FORMAT='%H:%M (%p) %Z %a %m %b %Y'

if [ "$1" ] ; then
  time=`date +%T`

# Show the time from the specified input time zone in the specified output
# time zone

  TZ=$TZOUT date --date='TZ="'$TZIN'"'" $time" +"$time $TZIN is $TZOUT $FORMAT"

for tz in $TZONES ; do
  showtime $TZBASE $tz


for tz in $TZONES ; do
  showtime $tz $TZBASE


Often you have timestamp in local timezone and you need to convert it to remote tz. It can be done with:

TZ=America/Curacao date -d 'Tue Nov 28 00:07:05 MSK 2016'


America/Curacao - remote timezone
MSK - local timezone

Show New York time tomorrow at 3pm

date --date='TZ="America/NewYork" 15:00 tomorrow'


ti 3.11.2020 17.00.00 +0200

(ti is Finnish short from tiistai, meaning tuesday in English.)

My local timezone is Finland/Helsinki. So tommorrow at 17 o'clock in Finland/Helsinki is same time: 3pm in New York.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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