Unix timestamps in PowerShell
PowerShell can call .NET's DateTimeOffset directly, which works the same in Windows PowerShell 5.1 and PowerShell 7.
Get the current Unix timestamp
[DateTimeOffset]::UtcNow.ToUnixTimeSeconds()
[DateTimeOffset]::UtcNow.ToUnixTimeMilliseconds()
Get-Date -UFormat %s # seconds, as a string
Convert a Unix timestamp to a date
[DateTimeOffset]::FromUnixTimeSeconds(1700000000).UtcDateTime
# Tuesday, 14 November 2023 22:13:20
Get-Date -UnixTimeSeconds 1700000000 # PowerShell 7.1+, shown in local time
Convert a date to a Unix timestamp
[DateTimeOffset]::new(2026, 11, 14, 10, 0, 0, [TimeSpan]::Zero).ToUnixTimeSeconds()
# 1794650400
([DateTimeOffset](Get-Date '2026-11-14T15:30:00+05:30')).ToUnixTimeSeconds()
Timezones
$tz = [TimeZoneInfo]::FindSystemTimeZoneById('Asia/Kolkata') # IANA IDs work in PowerShell 7
[TimeZoneInfo]::ConvertTime([DateTimeOffset]::FromUnixTimeSeconds(1700000000), $tz)
Common mistakes
- Windows PowerShell 5.1 runs on .NET Framework, where
FindSystemTimeZoneByIdonly knows Windows IDs such asIndia Standard Time. Get-Date -UnixTimeSecondsexists only in PowerShell 7.1+ and returns local time (KindisLocal). Add-AsUTCor useDateTimeOffsetfor UTC.FromUnixTimeSecondsthrowsArgumentOutOfRangeExceptionoutside -62,135,596,800 to 253,402,300,799 (0001-01-01 to 9999-12-31). Passing milliseconds where it expects seconds triggers this. UseFromUnixTimeMillisecondsfor 13-digit values.(Get-Date).Tickscounts 100 ns since the year 1, not since 1970.
Complete example
$now = [DateTimeOffset]::UtcNow.ToUnixTimeSeconds()
"Now: $now"
$t = [DateTimeOffset]::FromUnixTimeSeconds(1700000000)
"UTC: " + $t.ToString('o')
"Back: " + $t.ToUnixTimeSeconds()
Check any value with the epoch converter, or convert a whole column with the batch converter. All examples use 1700000000 (2023-11-14 22:13:20 UTC) and 1794650400 (2026-11-14 10:00:00 UTC).