Unix Timestamp in Go

The Go-specific pitfall

Go's time.Time is timezone-aware by design — every Time value carries a *Location — so the naive/aware bug class that hits Python and C# mostly can't happen here. The more common Go-specific mistake is forgetting that time.Unix()'s second argument is nanoseconds, not milliseconds, and passing a millisecond value straight into it without conversion.

Have a timestamp right now?

Paste it into the Timestamp ⇄ Date Converter to check it instantly, in any timezone, without writing any code. Working across several languages on the same project? The full Epoch Time in Programming Languages guide has all of them side by side for quick comparison.