Trexmi
Converter Ready

Timestamp Converter

Convert Unix seconds, milliseconds, microseconds and date-time text to UTC, ISO 8601 and selected timezones.

Auto-detect common Unix timestamp units Force seconds, milliseconds or microseconds Convert to UTC and selected timezones Return Unix seconds, milliseconds and microseconds together
Numeric input can be auto-detected or forced to seconds, milliseconds, or microseconds. Date-time text without an explicit offset is interpreted in the selected timezone.
INPUT Timestamp or date-time value *
0 chars0 words0 lines
Paste the source value for this specific transformation. Example: Trexmi developer sample

Tool settings

Ctrl / ⌘ + Enter
Timestamp conversion UTC, local ISO 8601, Unix seconds, milliseconds, microseconds, RFC 2822 and calendar details.
About the tool

What Timestamp Converter does

Timestamp Converter converts Unix epoch values and readable date-time text into developer-friendly date formats. Numeric input can be treated as seconds, milliseconds or microseconds, with auto-detection available for common modern timestamps.

The result includes local ISO 8601, UTC ISO 8601, Unix seconds, milliseconds and microseconds, RFC 2822, weekday, ISO week and timezone offset. This makes the tool useful for API debugging, log analysis, databases, JWT claims and cross-timezone troubleshooting.

How to use

  1. Enter a value. Use a Unix number such as 1767225600 or a date such as 2026-01-01T00:00:00Z.
  2. Choose the unit. Auto detect works for typical epoch magnitudes; force a unit when the source format is known.
  3. Select timezone. UTC is safest for interchange; choose a local zone when investigating displayed time.
  4. Convert. Review all equivalent representations together.
  5. Check ambiguous input. Date-time text without an explicit offset is interpreted in the selected timezone.
Built for the task

Why use Timestamp Converter?

Focused controls, predictable output, and a workflow designed around this exact transformation.

01

Seconds, ms and µs

Common Unix timestamp precisions are supported in one converter.

02

Auto detection

Typical numeric magnitudes can be detected automatically, with an override when needed.

03

Timezone conversion

See UTC plus a selected IANA timezone representation.

04

Developer outputs

ISO 8601, RFC 2822 and multiple epoch units are returned together.

Useful answers

Questions about Timestamp Converter

Practical details about input, output, privacy, limits, and the best way to use this tool.

01 How do I know if a timestamp is seconds or milliseconds?

Current Unix seconds usually have about 10 digits, milliseconds about 13, and microseconds about 16. Force the unit if the source specification is known.

02 What is the Unix epoch?

Unix time counts elapsed seconds from 1970-01-01 00:00:00 UTC, excluding leap-second representation.

03 Why does timezone matter for readable dates?

A numeric Unix timestamp represents an instant. A displayed calendar date/time depends on the selected timezone.

04 What happens to a date without Z or an offset?

It is interpreted in the output timezone selected in the tool. Include Z or an explicit offset when the source timezone matters.

05 Can this convert JWT exp values?

Yes. JWT NumericDate values are normally Unix seconds. For a full token, the JWT Expiration Checker is more convenient.

Continue this workflow

Related tools for Timestamp Converter

Open the next relevant utility without returning to the main directory.

Related toolJSON to Zod Schema Related toolcURL to Go net/http Related toolJSON to TypeScript Related toolJSON to YAML Related toolcURL to PHP cURL Related toolcURL to Python Requests Related toolJSON to OpenAI Function Schema Related toolJSON Flatten

Examples

Convert Unix seconds

A ten-digit epoch value is interpreted explicitly as seconds.

Input 
Value: 1767225600
Unit: seconds
Timezone: UTC
Output 
UTC: 2026-01-01T00:00:00.000000Z
Unix milliseconds: 1767225600000
Day: Thursday

Convert Unix milliseconds

The same instant can be represented at different numeric precision.

Input 
Value: 1767225600000
Unit: milliseconds
Timezone: UTC
Output 
UTC: 2026-01-01T00:00:00.000000Z
Unix seconds: 1767225600

Convert an offset date

The explicit +03:00 offset identifies the instant before UTC conversion.

Input 
Value: 2026-09-04T12:30:00+03:00
Timezone: Europe/Kyiv
Output 
Local: 2026-09-04T12:30:00.000000+03:00
UTC: 2026-09-04T09:30:00.000000Z
Unix seconds: 1788514200

Unix seconds, milliseconds, and microseconds

All three units count from the Unix epoch but use different precision. Around 2026, Unix seconds normally contain 10 digits, milliseconds 13, and microseconds 16. Auto detection uses numeric magnitude; force the documented unit when an API or database contract specifies it.

Timestamp conversion examples

Unix seconds to UTC

Input: 1767225600
Unit: Unix seconds
Timezone: UTC
UTC ISO 8601: 2026-01-01T00:00:00.000000Z
Unix milliseconds: 1767225600000

The same instant in milliseconds

Input: 1767225600000
Unit: Unix milliseconds
Timezone: UTC
UTC ISO 8601: 2026-01-01T00:00:00.000000Z
Unix seconds: 1767225600

The same instant in microseconds

Input: 1767225600000000
Unit: Unix microseconds
Timezone: UTC
UTC ISO 8601: 2026-01-01T00:00:00.000000Z

Date-time with an explicit offset

Input: 2026-09-04T12:30:00+03:00
Timezone: Europe/Kyiv
Local ISO 8601: 2026-09-04T12:30:00.000000+03:00
UTC ISO 8601: 2026-09-04T09:30:00.000000Z
Unix seconds: 1788514200

Date text without an offset

Input: 2026-09-04 12:30:00
Selected timezone: UTC
Interpretation: 2026-09-04T12:30:00.000000+00:00

UTC, explicit offsets, and local display

A numeric Unix timestamp represents one instant. The selected timezone changes its readable local representation, not the instant. Date-time text containing Z or an explicit offset carries its own source offset. Text without an offset is interpreted in the timezone selected in the workspace.

Use UTC or an offset-bearing RFC 3339 string for interchange. Convert to a named IANA timezone for display, log comparison, and daylight-saving analysis.

Common timestamp conversion mistakes

Treating milliseconds as seconds produces a date far outside the expected range. Floating-point numeric input can also carry fractional seconds, while an integer loses that fraction. Negative Unix values represent instants before 1970 when the runtime supports them.

JWT iat, nbf, and exp are normally Unix seconds. Decode the complete token with JWT Decoder. Format timestamp objects copied from API responses with JSON Formatter, or inspect encoded timestamp parameters with Query String Parser.

Reference

For interoperable date-time strings, see RFC 3339.