Skip to content
World Cup Kickoff Time Converter is liveSee kickoff times in your time zone and add calendar reminders.

Timestamp Converter

Convert Unix timestamps and date-times in both directions, with automatic seconds/milliseconds detection, Local/UTC/city timezone output, and ISO or SQL-style formatting for logs and database work.

Enter Unix Timestamp

Supports seconds and milliseconds with automatic detection

Timezone

Format

Enter your own format

Timestamp Input

Current Time

Timestamp (seconds)

1704067200

Timestamp (ms)

1704067200000

Timestamp Converter

Quick Start

1
Choose direction: Timestamp → Date or Date → Timestamp
2
Enter a timestamp or date: 10 digits usually mean seconds, 13 digits usually mean milliseconds; ISO such as 2024-01-01T12:00:00Z works best.
3
Pick timezone and format: Local, UTC, city timezones, and ISO/API/SQL-style templates.
4
Copy results: the selected date format, seconds, or milliseconds.

Common Scenarios

Log tracing

convert timestamps in backend logs to readable date-time to locate issues

Token/session expiry

check JWT exp/iat (issued at) and validate the validity period

DB import/export

convert between timestamps and date fields in SQL/CSV

Frontend display

backend passes seconds/milliseconds; format by the user's timezone on the frontend

Cross-timezone debugging

switch city timezones to observe differences (including DST)

Scheduling

verify triggers match expectations (UTC vs local)

API parameters

validate request/response time units (seconds/ms) and formats

Audit/compliance

convert between ISO and timestamps for manual review

Units, Timezones & Formats

Supported formats: ISO 8601, RFC 2822, YYYY‑MM‑DD HH:mm:ss, YYYY/MM/DD HH:mm:ss, HTTP/SQL, etc
Custom format: common templates supported (e.g. YYYY‑MM‑DD HH:mm:ss.SSS)
Auto-detect: common 10-digit seconds and 13-digit milliseconds
Timezone: select UTC or city timezones; DST and UTC offsets are handled by the timezone rules.

Timestamp Rules & Boundaries

Unix timestamps count from 1970-01-01 00:00:00 UTC; leap seconds are not modeled separately
Seconds/milliseconds: common 10-digit values are seconds and 13-digit values are milliseconds; ambiguous values follow the converter's numeric threshold.
Timezone: a timestamp represents one absolute moment; date inputs without an offset are interpreted in the selected timezone
Formats: To Date shows one selected output format; choose ISO/API/SQL-style templates from the format menu when needed.
Precision: output covers seconds and milliseconds only; microsecond or nanosecond timestamps need a dedicated parser
Copying: copy the current timestamp, formatted date, seconds, or milliseconds; CSV, batch export, and one-click all-results copy are not included.

Usage Advice

Store in UTC and display in the user's timezone to avoid applying timezone conversion twice
Logs/API debugging: trace timelines, verify token expiry (exp), validate time params
Intervals: for time differences, copy the two results and compute externally
Real‑time: header shows current time and timestamp (milliseconds update)

URL Quick Fill

Put supported parameters after # in the address to prefill this tool when the page opens.
view: Tool view (optional)
timestamp: Timestamp (required for To Date)
datetime: Date and time (required for To Timestamp)
tz: Timezone (optional)
format: Format
/timestamp-converter#view=to-date&timestamp=1700000000&tz=UTC
URL parameters are only used in your browser to prefill the tool; CrateX.app does not record them.
Do not put sensitive content in URL parameters because the address bar and browser history can expose them.

Limitations & Compatibility

Precision: JavaScript Date is millisecond‑precision; use libraries/strings for µs/ns
Leap seconds: not displayed explicitly; most systems align to UTC transparently
Year 2038: 32‑bit Unix time will overflow on 2038‑01‑19 03:14:07 (UTC); prefer 64‑bit timestamps
Input rules: full-width digits and common symbols are normalized; use ISO with an offset or a matching custom format for ambiguous dates.

Privacy & Security

All processing happens locally in your browser. You can replace, clear, and re-run the current content at any time.

FAQ

7

Continue with these related tools for the next step.

All tool processing happens locally in your browser.