Go Time Format Converter (time.Time)

Go formats time with layout strings based on the reference time `Mon Jan 2 15:04:05 MST 2006` — you do not use `yyyy`/`MM`, you use `2006`/`01`. Go also ships named constants: `time.Kitchen`, `time.Stamp`, `time.StampNano`, `time.RFC822`, `time.RFC822Z`, `time.RFC1123` and `time.RFC1123Z`.

This converter renders your date-time in each of these Go constants so you can see exactly what `t.Format(time.RFC3339)` or `t.Format(time.Kitchen)` will print.

Timezone:
Enter a date-time above to see the conversion results.

Go Time Format Converter (time.Time) Quick Reference

FormatPattern / DescriptionExample 1Example 2
Go Layout (Reference)Standard layout for Go2026-08-13T14:30:00Z2026-01-01T00:00:00Z
Go KitchenKitchen time format (3:04PM)2:30PM12:00AM
Go StampJan _2 15:04:05Aug 13 14:30:00Jan 1 00:00:00
Go StampNanoStamp with nanosecondsAug 13 14:30:00.000000000Jan 1 00:00:00.000000000
Go RFC82202 Jan 06 15:04 MST13 Aug 26 14:30 GMT01 Jan 26 00:00 GMT
Go RFC822Z02 Jan 06 15:04 -070013 Aug 26 14:30 +000001 Jan 26 00:00 +0000
Go RFC1123Wed, 24 Apr 2024 06:35:45 GMTThu, 13 Aug 2026 14:30:00 GMTThu, 01 Jan 2026 00:00:00 GMT
Go RFC1123ZWed, 24 Apr 2024 14:35:45 +0800Thu, 13 Aug 2026 14:30:00 +0000Thu, 01 Jan 2026 00:00:00 +0000

* Examples are rendered in UTC for the fixed sample instants above.

When to Use Go Time Format (time.Time)

Choosing a format constant

Pick the right Go constant for logs (`time.StampNano`), HTTP headers (`time.RFC1123`), or APIs (`time.RFC3339`) by previewing the output.

Writing custom layouts

Verify a custom layout string like `2006-01-02 15:04:05` produces the intended output before deploying.

Cross-language parity

Confirm a Go timestamp matches what a Python or Java consumer expects by comparing all rendered variants side by side.

Frequently Asked Questions

What is the Go time layout reference?

Go uses `Mon Jan 2 15:04:05 MST 2006` as the reference; your layout re-uses those tokens (e.g. `2006-01-02` = year-month-day). There is no `yyyy-MM-dd` in Go.

What is the difference between RFC822 and RFC822Z?

`RFC822` = `02 Jan 06 15:04 MST` (abbreviated year); `RFC822Z` uses a numeric zone `02 Jan 06 15:04 -0700`. Same for RFC1123 (`Mon, 02 Jan 2006 15:04:05 MST`) vs RFC1123Z (`... -0700`).

What does time.Kitchen print?

`2:04PM` (hour:minute with AM/PM, no seconds, no date). Ideal for compact UI time display.

What does time.Stamp print?

`Jan _2 15:04:05` — e.g. `Aug 13 14:30:00`. `StampNano` adds nanoseconds: `Aug 13 14:30:00.123456789`.

Related Time Format Converters

Java Date Time Format Converter (java.time)
Convert dates to Java java.time formats: ISO_INSTANT, ISO_LOCAL_DATE_TIME, ISO_OFFSET_DATE_TIME, ISO_ZONED_DATE_TIME and more. Free converter for Java developers.
Python Datetime Format Converter
Convert dates to Python datetime formats: isoformat() output and time.ctime() string. Free converter showing exactly what Python prints.
RFC 3339 Date-Time Converter
Convert any date to RFC 3339 format (2026-08-13T14:30:00Z or +00:00 offset). The timestamp standard for JSON APIs and cloud services. Free converter.
UTC Time Converter (Coordinated Universal Time)
Convert any local time to UTC (Coordinated Universal Time) instantly. See the UTC string, Z-suffixed ISO form and GMT equivalent. Free UTC converter.

All Format Guides

Unix TimestampISO 8601ISO Week DateISO Ordinal DateMilitary TimeDecimal TimeRFC 2822RFC 3339SQL DatetimeJulian DateHTTP DateExcel Serial DateGPS TimeUTC TimeCron Expression
Browse all 50 format guides →

Need to Convert Between All Formats?

Use the main Time Format Converter for instant conversion across 100+ formats — epoch, ISO 8601, RFC 3339, SQL datetime, military time and more in one click.

Open Time Format Converter