PowerShell Unix Timestamp Guide
PowerShell leverages .NET's DateTimeOffset class for Unix timestamp handling, supplemented by the Get-Date cmdlet. Since PowerShell runs on .NET, it can use [DateTimeOffset]::Now.ToUnixTimeSeconds() for modern, clean timestamp operations on both Windows and cross-platform PowerShell 7+.
Unix timestamps are a universal way to represent a specific moment in time as a single integer, counting the seconds elapsed since January 1, 1970 (the Unix epoch). Working with timestamps in PowerShell is a common task for developers building applications that log events, schedule jobs, compare dates, or communicate with APIs. The examples below cover the three most essential operations: retrieving the current timestamp, converting a timestamp into a human-readable date, and converting a date back into a timestamp.
Get Current Timestamp
The most common starting point is to capture the current moment as a Unix timestamp. In PowerShell, you can obtain the number of seconds (or milliseconds) since the epoch using built-in functions. This value is useful for recording when an event occurred, setting cache expiry times, or generating time-based identifiers.
Get Current Unix Timestamp
# Get current Unix timestamp
[int](Get-Date -UFormat %s)
# Output: 1706745600
# Alternative method
[DateTimeOffset]::Now.ToUnixTimeSeconds()Convert Timestamp to Date
Once you have a Unix timestamp, you often need to display it in a human-readable format. Converting a raw integer like 1706745600 into a formatted date string such as "2024-02-01 00:00:00" makes it meaningful to end users. The following PowerShell code demonstrates how to perform this conversion with proper timezone handling.
Convert to Date
# Convert Unix timestamp to DateTime
$timestamp = 1706745600
$date = (Get-Date "1970-01-01 00:00:00Z").AddSeconds($timestamp)
Write-Output $date
# February 1, 2024 12:00:00 AM
# Using .NET
[DateTimeOffset]::FromUnixTimeSeconds(1706745600).DateTimeConvert Date to Timestamp
The reverse operation is equally important. When users provide a date through a form or when your application reads dates from a file, you need to convert them into Unix timestamps for storage, comparison, or transmission via APIs. Here is how to convert a date or date string into a Unix timestamp in PowerShell.
Convert to Timestamp
# Convert DateTime to Unix timestamp
$date = Get-Date "2024-02-01 00:00:00"
$epoch = Get-Date "1970-01-01 00:00:00"
[int]($date - $epoch).TotalSeconds
# 1706745600Common Pitfalls in PowerShell
Working with timestamps can be error-prone, especially across different platforms and timezone configurations. Being aware of these common mistakes will help you write more robust PowerShell code and avoid subtle bugs that are difficult to trace in production.
- 1Get-Date -UFormat %s may be off by timezone offset — use [DateTimeOffset] methods instead
- 2[DateTimeOffset]::FromUnixTimeSeconds() is only available in .NET 4.6+ / PowerShell 5.1+
- 3Date arithmetic with Get-Date uses local timezone by default
- 4Cast to [int] for seconds — [long] for milliseconds to avoid overflow
Best Practices for Timestamp Handling
Regardless of the programming language, following a few best practices will keep your timestamp code reliable. Always store and transmit timestamps in UTC to avoid timezone ambiguity. Use seconds-based Unix timestamps unless your application requires sub-second precision, in which case milliseconds or microseconds are appropriate. When displaying dates to users, convert from UTC to their local timezone only at the presentation layer. Document whether your APIs expect seconds or milliseconds, as mixing the two is one of the most frequent sources of timestamp bugs.
Frequently Asked Questions
Related Tools
Timestamp Guides for Other Languages
Need Unix timestamp examples for a different programming language? Browse our complete collection of language-specific guides with copy-paste code snippets.