Timestamp Converter

Convert between Unix timestamps and human-readable dates with timezone support

Input & Settings

Enter timestamp in seconds

Conversion Result

Conversion result will appear here

Time Information

Now: —
Unix: —
UTC: —
UTC (Coordinated Universal Time)
Offset: +00:00

• Unix timestamp: Seconds since Jan 1, 1970

• JavaScript timestamp: Milliseconds since epoch

• ISO 8601: Standard date/time format

• UTC: Coordinated Universal Time

Unix Epoch:0
Y2K:946684800
32-bit limit:2147483647

Timestamp Examples & Use Cases

Standard Format

The international standard for exchanging date and time data.

2023-11-15T14:30:00Z

With Timezone Offset

Includes offset from UTC.

2023-11-15T09:30:00-05:00

    Examples

    Unix seconds → human date in local and UTC

    Input
    1700000000
    Output
    Unit       seconds
UTC        2023-11-14T22:13:20Z
RFC 2822   Tue, 14 Nov 2023 22:13:20 +0000
Local      2023-11-14 17:13:20 EST  (UTC-5)

    The same instant in time, written three ways; the UTC form is stable across machines while the local form reflects the viewer's timezone.

    Human date → Unix seconds and milliseconds

    Input
    2024-01-15 14:30:00 UTC
    Output
    Unix (s)   1705329000
Unix (ms)  1705329000000

    Pick the unit your database or API uses — milliseconds are JavaScript's `Date.now()` default; seconds are what `date +%s` and most Unix tooling emit.

    Same instant, different timezones

    Input
    2024-06-01T12:00:00Z
    Output
    UTC        12:00
New York   08:00  (UTC-4, EDT)
Tokyo      21:00  (UTC+9)
Sydney     22:00  (UTC+10)

    A timestamp is a single point on the UTC timeline — converting it to a timezone is formatting, not a data change.

    About this tool

    A Unix timestamp is the number of seconds (or milliseconds) elapsed since January 1, 1970 UTC — the universal way programs represent an instant in time. Every API response, database row and log line uses them, but a raw number like 1700000000 tells a human nothing. This converter bridges that gap, translating in both directions between timestamps and readable dates.

    Paste a timestamp to see the corresponding date and time in your local timezone and in UTC, or pick a calendar date to get its Unix value — with support for seconds vs. milliseconds, multiple timezones, and over a dozen output formats including ISO 8601 and RFC 2822. All conversion is client-side.

    How to use

    1. Enter a timestamp or date

      Paste a Unix timestamp, or choose a calendar date and time.

    2. Pick seconds or milliseconds

      Tell the tool which unit your timestamp uses so the conversion is exact.

    3. Choose the output format

      View the result as ISO 8601, RFC 2822, a custom pattern, or in a specific timezone.

    4. Copy the value

      Copy the timestamp or the formatted date for use in your code or logs.

    Use cases

    Reading API and log timestamps

    A log line shows `1700000000` — paste it to see the wall-clock time in your local zone without doing math in your head.

    Generating test fixtures

    Pick a specific instant (e.g. the start of 2024) and convert it to the seconds-or-milliseconds form your seed file or API contract expects.

    Scheduling across timezones

    Translate a "midnight on Jan 1" claim into the actual Unix seconds for a particular region so a cron job fires at the intended local moment.

    Validating a JWT `exp` or `iat` claim

    Decode a Unix timestamp from a token claim, view it as ISO 8601 in UTC, and instantly see whether the token is expired or how long it has left.

    Common output formats

    FormatExample
    Unix seconds1700000000
    Unix milliseconds1700000000000
    ISO 86012023-11-14T22:13:20Z
    RFC 2822Tue, 14 Nov 2023 22:13:20 +0000
    Local & UTCShown side by side for the same instant

    All conversion happens locally in your browser.

    Common mistakes

    Mistake:Treating seconds and milliseconds as interchangeable.

    Fix:They differ by a factor of 1000. JavaScript's `Date.now()` and `new Date().getTime()` return milliseconds; `Math.floor(Date.now() / 1000)` is seconds — pick one and label it explicitly.

    Mistake:Computing in local time and then storing as if it were UTC.

    Fix:A timestamp is timezone-independent by definition; only its *display* changes. Use the Date object's UTC methods (or a library) when serializing so DST and host zone never leak into the value.

    Mistake:Parsing strings with `new Date('2024-01-15')` and assuming ISO behavior across browsers.

    Fix:Bare date strings are implementation-defined — always send an explicit ISO-8601 string with an offset or `Z`, then parse with the same library on both ends.

    Mistake:Ignoring leap seconds in scheduling.

    Fix:POSIX Unix time skips leap seconds, so 23:59:60 UTC never appears in a timestamp. For wall-clock accuracy around a leap-second event, store an ISO-8601 string instead of a Unix number.

    Frequently asked questions

    References & standards

    Related tools

    Base64 Toolbox

    Professional Base64 workspace for text, files and images with Base64URL, MIME, Data URI, strict validation, image preview and ready-to-use snippets.

    CSV to Chart

    Paste or upload CSV data and generate bar, line, pie, or doughnut charts. Export as PNG.

    CSV to JSON Converter

    Paste CSV data and convert it to pretty-printed JSON instantly — supports custom delimiters, header row toggling, and value trimming.

    cURL to Code Converter

    Convert cURL commands to code snippets in multiple languages. Parse cURL and generate JavaScript, Python, PHP, and more.

    Diff Checker

    Compare two text blocks and highlight differences side-by-side

    GraphQL Formatter & Validator

    Format, validate and beautify GraphQL queries with syntax highlighting