Skip to main content
Back to Developer Tools

Timestamp Converter

Unix timestamp and date time conversion, supports multiple timezones

Conversion Settings

Second-level timestamp (10 digits)

Example Timestamps
Conversion Results

Enter timestamp or date time to start conversion

Timestamp Knowledge

What is Unix Timestamp?

Unix timestamp is the total seconds from January 1, 1970 00:00:00 UTC to the specified time. It is a standard way to represent time, widely used in computer systems and programming.

Timestamp Types

Common timestamps include second-level (10 digits), millisecond-level (13 digits), and microsecond-level (16 digits). This tool uses second-level timestamps, which is the most commonly used format.

Timezone Handling

Timestamps are timezone-agnostic and always based on UTC. When converting to local time, timezone offset needs to be considered. Different regions may have different daylight saving time rules.

Application Scenarios

Timestamps are commonly used in database storage, logging, API communication, cache expiration, and other scenarios. They facilitate time calculations, comparisons, and storage, serving as a universal standard for time processing.

Timestamp conversion formula
Unix timestamps count elapsed seconds since the Unix epoch. This page treats numeric timestamp input as seconds.
Unix timestamp = floor(milliseconds since 1970-01-01T00:00:00Z / 1000)
Date object milliseconds = Unix timestamp * 1000
UTC date/time = format Date object in UTC
Local date/time = format Date object in selected timezone
epoch
1970-01-01T00:00:00Z
The UTC reference point used by Unix time.
timestamp
Elapsed seconds
Most APIs store Unix timestamps in seconds, while JavaScript Date uses milliseconds.
timezone
Display context
The timestamp itself is timezone-neutral; timezone only changes the formatted display.
How this timestamp converter works
The converter is designed for API debugging, log analysis, database checks, and timezone-safe copy/paste workflows.
  1. Parse numeric timestamp input as Unix seconds, or parse a date/time string into a JavaScript Date.
  2. Convert seconds to milliseconds for JavaScript Date operations.
  3. Format the same instant as UTC, ISO 8601, local time, and the selected timezone where supported.
  4. Calculate a relative label by comparing the timestamp with the current browser time.
  5. Keep conversion local in the browser so pasted timestamps are not sent to a server.

Important notes

  • Check whether your source system uses seconds, milliseconds, microseconds, or nanoseconds.
  • Timezone labels change display only; they do not change the underlying instant.
  • Ambiguous local date strings can parse differently across browsers, so ISO-style input is safer.
Timestamp examples
These examples cover common debugging cases where seconds, milliseconds, and timezones are easy to mix up.

API response timestamp

A REST API returns an event time as Unix seconds.

  • Timestamp: 1704067200
  • Timezone: UTC

UTC time: 2024-01-01T00:00:00.000Z

Use UTC for logs and API comparisons so local timezone settings do not hide ordering problems.

JavaScript milliseconds

A browser event stores Date.now() output.

  • Milliseconds: 1704067200000
  • Convert to seconds by dividing by 1000

Unix timestamp: 1704067200

A 13-digit value is usually milliseconds; a 10-digit value is usually seconds.

Timezone display check

A database stores UTC while the product UI displays local time.

  • Timestamp: 1704067200
  • Compare UTC and local timezone output

Same instant, different displayed clock time

Store instants in UTC and apply timezone formatting only at the display layer.

Timestamp FAQ
Common timestamp issues in APIs, databases, and frontend debugging.