Advanced Timestamp Converter

Convert between Unix timestamp, ISO 8601, RFC 2822 and relative dates ("3 days ago"). Supports IANA timezones with DST.

Come utilizzare Convertitore Timestamp Avanzato

Insert a timestamp or date

Paste Unix timestamp (in seconds or milliseconds), ISO 8601, RFC 2822 date or relative expression like "3 days ago". You can also use the "Now" button for current instant.

Choose reference timezone

Select IANA timezone from list (e.g., Europe/Rome, America/New_York): will be used to calculate local time and daylight saving status.

Read all converted formats

The tool shows Unix, ISO 8601, RFC 2822, relative date, UTC time and selected timezone with indication of DST activation.

Copy the format you need

Use "Copy" button next to each line to quickly copy value into notes ready for pasting in code, log or documentation.

Suggerimenti

  • For API debugging and logging, always prefer comparing timestamps in UTC: avoid ambiguities related to DST and timezone differences between servers and clients.
  • If a timestamp seems "1000 times off", check if it's in seconds or milliseconds: this is the most common error when integrating different systems.
  • Use relative expressions ("3 days ago") for quickly verifying deadlines or TTL without having to manually calculate exact date.

Domande frequenti

What's difference between Unix timestamp in seconds and milliseconds?

Unix timestamp in seconds typically has 10 digits (e.g., 1713956400), while in milliseconds it has 13 (e.g., 1713956400000 used by JavaScript Date.now()). The tool automatically recognizes length and interprets number accordingly.

Which date formats can I paste as input?

You can insert Unix timestamp (9-13 digits), ISO 8601 dates (e.g., 2025-04-24T10:00:00Z), RFC 2822 dates, or relative expressions like "3 days ago", "2 hours ago" or "5 min ago". Parser tries these formats in sequence until it finds a valid one.

What does DST status indicate?

Indicates whether for selected timezone and inserted date daylight saving time is active or not: useful to understand potential 1-hour discrepancies between systems handling time zones differently.

Why use UTC besides local time?

UTC is an absolute reference, without timezone nor DST, and it's the standard recommended for system logs, APIs and databases. Local time in selected timezone serves instead for communication with users or teams in specific geographic area.

Where does calculation occur: browser or server?

Entire conversion occurs client-side in browser using Intl and Date native JavaScript APIs; no timestamp nor date inserted is sent to external server.