The Intellectual Wilderness There is nothing more useless than doing efficiently that which should not be done at all.

2013.04.20 13:46

Most common Bash date commands for timestamping

Filed under: Computing — Tags: , , , , — zxq9 @ 13:46

From time to time I get asked how to use the date command to generate a timestamp. Here is an idiot-friendly script you can post for reference in your team’s bin/ if you get interrupted about timestamp questions or have an aversion to typing phrases like “man date” (with or without a space).

All but the first one and last three produce filename-friendly strings.

A big thanks to the following folks for pointing out mistakes and suggesting useful format inclusions:

  • 2013-05: Rich for the reminder to include UTC and timezoned stamps.
  • 2017-10: “Hamilton and Meg” (haha!) for pointing out I had my 4 year example formats messed up and for prodding me to include a 2-year example.
  • 2018-01: Autumn Gray for suggesting that I add examples of including short and long days of the week.
  • 2020-09: rade noticed that I had a “Zulu” notation for UTC listed as ISO8601, which it is not, and provided a correction. I’ve specified the Z-notation UTC timestamp separately from the (now corrected) ISO8601 timestamp. Thanks, rade!
#! /bin/bash

# An overly obvious reference for most commonly requested bash timestamps
# Now all you Mac fags can stop pestering me.

cat << EOD
        Format/result           |       Command              |          Output
YYYY-MM-DD_hh:mm:ss             | date +%F_%T                | $(date +%F_%T)
YYYYMMDD_hhmmss                 | date +%Y%m%d_%H%M%S        | $(date +%Y%m%d_%H%M%S)
YYYYMMDD_hhmmss (UTC version)   | date --utc +%Y%m%d_%H%M%SZ | $(date --utc +%Y%m%d_%H%M%SZ)
YYYYMMDD_hhmmss (with local TZ) | date +%Y%m%d_%H%M%S%Z      | $(date +%Y%m%d_%H%M%S%Z)
YYYYMMSShhmmss                  | date +%Y%m%d%H%M%S         | $(date +%Y%m%d%H%M%S)
YYYYMMSShhmmssnnnnnnnnn         | date +%Y%m%d%H%M%S%N       | $(date +%Y%m%d%H%M%S%N)
YYMMDD_hhmmss                   | date +%y%m%d_%H%M%S        | $(date +%y%m%d_%H%M%S)
Seconds since UNIX epoch:       | date +%s                   | $(date +%s)
Nanoseconds only:               | date +%N                   | $(date +%N)
Nanoseconds since UNIX epoch:   | date +%s%N                 | $(date +%s%N)
Z-notation UTC timestamp        | date --utc +%FT%TZ         | $(date --utc +%FT%TZ)
Z-notation UTC timestamp + ms   | date --utc +%FT%T.%3NZ     | $(date --utc +%FT%T.%3NZ)
ISO8601 UTC timestamp           | date --utc +%FT%T%Z        | $(date --utc +%FT%T%Z)
ISO8601 UTC timestamp + ms      | date --utc +%FT%T.%3N%Z    | $(date --utc +%FT%T.%3N%Z)
ISO8601 Local TZ timestamp      | date +%FT%T%Z              | $(date +%FT%T%Z)
YYYY-MM-DD (Short day)          | date +%F\(%a\)             | $(date +%F\(%a\))
YYYY-MM-DD (Long day)           | date +%F\(%A\)             | $(date +%F\(%A\))

If executed, it will produce the (obvious) output:

        Format/result           |       Command              |          Output
YYYY-MM-DD_hh:mm:ss             | date +%F_%T                | 2020-09-09_11:17:10
YYYYMMDD_hhmmss                 | date +%Y%m%d_%H%M%S        | 20200909_111710
YYYYMMDD_hhmmss (UTC version)   | date --utc +%Y%m%d_%H%M%SZ | 20200909_021710Z
YYYYMMDD_hhmmss (with local TZ) | date +%Y%m%d_%H%M%S%Z      | 20200909_111710JST
YYYYMMSShhmmss                  | date +%Y%m%d%H%M%S         | 20200909111710
YYYYMMSShhmmssnnnnnnnnn         | date +%Y%m%d%H%M%S%N       | 20200909111710866549239
YYMMDD_hhmmss                   | date +%y%m%d_%H%M%S        | 200909_111710
Seconds since UNIX epoch:       | date +%s                   | 1599617830
Nanoseconds only:               | date +%N                   | 873291281
Nanoseconds since UNIX epoch:   | date +%s%N                 | 1599617830874893393
Z-notation UTC timestamp        | date --utc +%FT%TZ         | 2020-09-09T02:17:10Z
Z-notation UTC timestamp + ms   | date --utc +%FT%T.%3NZ     | 2020-09-09T02:17:10.878Z
ISO8601 UTC timestamp           | date --utc +%FT%T%Z        | 2020-09-09T02:17:10UTC
ISO8601 UTC timestamp + ms      | date --utc +%FT%T.%3N%Z    | 2020-09-09T02:17:10.881UTC
ISO8601 Local TZ timestamp      | date +%FT%T%Z              | 2020-09-09T11:17:10JST
YYYY-MM-DD (Short day)          | date +%F\(%a\)             | 2020-09-09(水)
YYYY-MM-DD (Long day)           | date +%F\(%A\)             | 2020-09-09(水曜日)

Note that the last two, short and long day-of-week are dependent on the environment variable LANG. After setting LANG=en_US we wind up with the following:

YYYY-MM-DD (Short day)          | date +%F\(%a\)             | 2020-09-09(Wed)
YYYY-MM-DD (Long day)           | date +%F\(%A\)             | 2020-09-09(Wednesday)


  1. “man date”… haaaaaaa…

    Comment by avraml — 2013.04.22 11:14 @ 11:14

  2. You nearly made me choke with those non-UTC timestamps! You want to add date --utc +%FT%TZ and date +%FT%T%Z? The “T” makes it a little harder to read at first, but it’s correct per ISO 8601.

    Comment by Rich — 2013.05.17 10:00 @ 10:00

  3. @Rich
    Not a bad point. I didn’t include anything with timezones. I didn’t articulate this clearly, but the primary motivation for the post/script was being pestered with questions about how to produce filename-friendly timestamps in scripts — hence the lack of characters that are tricky on some operating systems (colons, in particular).

    Anyway, its easy to forget about timezones living in a country where there is only one! I’ve updated the post with your examples, because they are indeed useful.

    Thanks for the input!

    Comment by zxq9 — 2013.05.17 10:16 @ 10:16

  4. Wow, for about 2-3 minutes I thought you were smart until I reached the following in your text:
    “# Now all you Mac fags can stop pestering me.”

    Now I just think you’re a complete loser.

    Comment by Mac Fag — 2014.05.6 08:51 @ 08:51

  5. @Mac Fag
    At the time I wrote this I was surrounded by the Mac Fag Clone Army (figuratively, at least). That comment was for them, but if you feel you belong in the same category you’re welcome to apply the label to yourself.

    Comment by zxq9 — 2014.05.6 12:10 @ 12:10

  6. “Mac Fag” might be a touch juvenile, but it clearly hit close to home for someone… i can’t imagine any other reason you left it in the comments than to troll.

    +1 for the Best in Show reference! Excellent demonstration why its stupid to try flaming someone on their own blog.

    Btw, writing this on my iPhone, which is actually quite annoying.

    Comment by Marzipan — 2014.05.6 16:50 @ 16:50

  7. When I posted this I never imagined that a single commented line would become such a topic for discussion.

    Comment by zxq9 — 2014.05.6 16:58 @ 16:58

  8. Brilliant. Both the post and the retort.

    Comment by apocalysque — 2015.12.18 13:06 @ 13:06

  9. I would like to get this:
    ISO8601 UTC timestamp | date –utc +%FT%TZ | 2013-05-17T01:16:09Z

    But with milliseconds also. I.E.

    Comment by Brian M — 2016.08.24 07:05 @ 07:05

  10. For three digits of the nanosecond output you can insert a length field before the “N”:
    date --utc +%FT%T.%3NZ
    I’ll add that to the list.


    Comment by zxq9 — 2016.10.14 09:16 @ 09:16

  11. “When I posted this I never imagined that a single commented line would become such a topic for discussion.”

    That’s what happens when you use hate speech.

    Comment by Conor — 2017.05.28 03:09 @ 03:09

  12. “hate speech”

    At first I was like

    Then I was like

    Comment by zxq9 — 2017.05.28 21:04 @ 21:04

  13. As I type this on my MacBook Air sipping a Café Mocha from Starbucks I appreciate the beautiful table of formats and outputs. Viewing in a log file the output reminds me of the regularity of receiving my J Crew catalogs. :-)

    Currently your excellent table is one of the top Google results for “bash create timestamp”. Would you adjust the first column to be consistent with the output for number of years, and add 2-year formats?
    YYYYMMDD_hhmmss | date +%Y%m%d_%H%M%S | $(date +%Y%m%d_%H%M%S)
    YYMMDD_hhmmss | date +%y%m%d_%H%M%S | $(date +%y%m%d_%H%M%S)

    Comment by Hamilton and Meg — 2017.10.16 18:00 @ 18:00

  14. How delightful to find a Starbucks-going MacBook user with a sense of humor!

    Good idea. I’ll make that change directly.

    Thank you for taking the time to make the suggestion. Whatever else you’re doing, I hope you’re having fun coding! o/

    Comment by zxq9 — 2017.10.16 21:31 @ 21:31

  15. Thanks! Needed this for an EDI application…
    Had to get to at least %4N to guarantee a unique value on our platforms.
    Used this for testing:

    while [ $cnt -lt 25 ]
      echo $(date +%Y%m%d%H%M%S_%3N) #milliseconds
      echo $(date +%Y%m%d%H%M%S_%6N) #microseconds
      echo $(date +%Y%m%d%H%M%S_%N) #nanoseconds

    Comment by Larry — 2017.10.27 03:52 @ 03:52

  16. Might be useful to add `%a` and `%A`.

    Comment by Autumn Grey — 2018.01.6 07:52 @ 07:52

  17. Added. Thank you for the suggestion!

    Comment by zxq9 — 2018.01.24 13:19 @ 13:19

  18. `–utc` is not in standard date, it is part of GNU date (or gdate on many systems)

    `TZ=UTC date +%FT%T%Z`

    will work in any bash-like shell, it will not work in a shell like csh tcsh or fish.

    Comment by Lewis — 2018.09.18 23:30 @ 23:30

  19. Interesting! I’ll add a note and some examples about this.

    Thank you for pointing that out.

    Comment by zxq9 — 2018.09.19 07:29 @ 07:29

  20. Google brought me here while seeking a quick example of different date/timestamps with bash… googled this plenty before, first time finding this result… totally caught off guard by the mac-fag comment in the example you chose to include.

    You either put that in there or decided to leave it when you copy-pasted something you did not create. That has nothing to do with the topic at hand. Unnecessary hate.

    Comment by t — 2019.04.30 16:00 @ 16:00

  21. Hope it was helpful for you.

    And I wrote the above code and the comment — it was a jab back at some of the folks I was working with at the time, “Mac fag” being a bit of an in-joke at the time.

    I have left it up here on the site specifically because I find it amusing that some tiny fraction of people find it (and anything else) “hateful” and leave drive-by comments such as yours.

    Comment by zxq9 — 2019.05.1 16:39 @ 16:39

  22. No hate … I just think you’re kind of a dick. Because of you’re small bit of bash-ery you offered up here, you think people should have to put up with you’re assbaggery – which makes you also a bit of a douche. Cheers.

    Comment by animalmutha — 2019.06.1 02:22 @ 02:22

  23. …says this assbag on someone else’s website where a resource was provided out of pure generosity…

    Haha! I’ve missed this aspect of the intertubes!

    Comment by zxq9 — 2019.06.1 06:21 @ 06:21

  24. Hey, there’s a slur in your post you and should probably remove it. Congrats on your SEO ranking and all I guess, but that doesn’t excuse using slurs to marginalize/dehumanize a group of people you don’t like. Perhaps you should try listening instead of getting so offended and hurt when someone corrects you. I know it can be difficult It comes off like you’re too insecure and weak to admit you were wrong. We’re all wrong sometimes, it’s okay.

    Comment by americanjello — 2019.12.10 22:46 @ 22:46

  25. This becoming a top result was a total surprise to me — I’ve never made any attempt at SEO.
    I’m pretty sure this is the only page that’s got any rank, though. Almost all of my traffic is from people who know me in some way or people browsing documentation for obscure projects I’ve written.

    As for the “slur”… Picking on a certain stereotype associated with Mac users is funny to me, and harsh or “problematic” language is something I’ve found useful in just the last few years as a social filter. People who will immediately take the attack angle “you’re too insecure and weak to admit you were wrong” are exactly the sort I prefer not to deal with.

    Comment by zxq9 — 2019.12.12 10:36 @ 10:36

  26. Wow. One poster called you 3 pejoratives in a single comment: dick, assbag and douche. Don’t people have manners anymore? I don’t understand the rationale behind responding to a generalized jovial jab at a group (intended to harm no specific person) with a vitriolic attack on an individual.

    Funny thing, I never even noticed the Mac fag reference. It was a #comment, and because I came here on a date formatting mission, my eyes went right to the tables of date commands. I never even noticed the Mac reference until I read Comment 5. Then I had to scroll up to find it. Suffice it to say that I’m grateful for the free information you’ve published here, and since I’m not a self-appointed patrolman for the PC Police, I didn’t take offense.

    Comment by bob — 2020.02.17 02:11 @ 02:11

  27. @bob I believe we can generally choose how to feel about almost anything that does not directly and repeatedly impact one’s own life, and the decision to feel rage and take vicarious offense on behalf of imagined people is a prime example of how this ability to choose can manifest negatively.

    Thanks for keeping things light. Let’s keep choosing to feel inspired and eager to create new things! Woohoo!

    Whatever you’re making, I sure hope you’re having a good time doing it. \o/

    Comment by zxq9 — 2020.02.17 12:30 @ 12:30

  28. missing ‘%’ before symbol ‘Z’

    Type error in line 12 of the date table:
    wrong: date –utc +%FT%TZ $(date –utc +%FT%TZ)
    right: date –utc +%FT%T%Z $(date –utc +%FT%T%Z)

    Type error in line 13 of the date table:
    wrong: date –utc +%FT%T.%3NZ $(date –utc +%FT%T.%3NZ)
    right: date –utc +%FT%T.%3N%Z $(date –utc +%FT%T.%3N%Z)

    Comment by rade — 2020.09.5 21:15 @ 21:15

  29. Oops! Thank you for noticing! I had intended that to be the “Zulu” notation for UTC, and you’re right — Z-notation (nautical/aviation/NATO) is not the same as ISO8601. I’ve added your correction as well as separate Z-notation lines.

    Comment by zxq9 — 2020.09.9 11:30 @ 11:30

  30. Is it possible to get date minus e.g. 14 days?

    Comment by Vladimir — 2021.03.30 18:45 @ 18:45

  31. Hi, Vladimir! Can we add or subtract a certain interval of time? That is an interesting question. Let’s see…

    There is a switch `–date=STRING` that instructs the command to render a formatted date set to the value provided by STRING, and we know that we can have the date command give us the epoch in seconds, and we should be able to perform arithmetic on those seconds in an inner command. So… YES! I think I can do this.
    Two weeks in seconds should be 60 seconds * 60 minutes * 24 hours * 14 days.

    In the four command examples below I:
    1. Get the date in seconds.
    2. Insert this as an inner command to date itself via –date.
    3. Perform the subtraction of 14 days.
    4. Add a format at the end of that subtraction to have it produce whatever format I want.

    ceverett@okonomiyaki:~$ date +%s
    ceverett@okonomiyaki:~$ date --date=@$(date +%s)
    2021年  3月 31日 水曜日 13:13:42 JST
    ceverett@okonomiyaki:~$ date --date=@$(($(date +%s) - (60 * 60 * 24 * 14)))
    2021年  3月 17日 水曜日 13:13:46 JST
    ceverett@okonomiyaki:~$ date --date=@$(($(date +%s) - (60 * 60 * 24 * 14))) +%FT%T%Z

    And it worked! Yay! From here a script command could easily be written that makes the number of days an arbitrary argument. If you stumble on a simpler way to do this please let me know!

    Comment by zxq9 — 2021.03.31 13:17 @ 13:17

RSS feed for comments on this post.

Leave a comment

Powered by WordPress