What is a Unix timestamp?

Seconds (or milliseconds) since 1970-01-01 00:00:00 UTC, commonly used in APIs, logs, and databases.

Can I convert both ways?

Yes. Epoch → date/time and date/time → epoch.

Does timezone matter?

Yes. Always confirm the timezone when converting human-readable datetimes to epoch.

Ctrl+K

Unix Timestamp Converter

Convert Unix timestamps (epoch time) to human-readable dates — and back. Supports 21 formats including ISO 8601, MySQL DATETIME, RFC 3339, milliseconds, and regional formats. Auto-detects input format. IANA timezone support. Runs entirely in your browser.

Input

Please enter date/time string

You can enter various formats such as ISO 8601, Unix timestamp, Japanese format, etc.

Detected Format

Input Timezone

Output

Output Timezone

Date Separator

Custom Format

Enter a custom format to display only that format. Example: Y-m-d H:i:s → 2026-01-16 19:11:05

Enter a date/time string to see conversion results

How to use

About this tool

This Unix timestamp converter helps you translate epoch time into human-readable dates and convert dates back to Unix timestamps. Use it when debugging APIs, reading logs, checking database values, or confirming scheduled jobs. Work in either direction: epoch → date/time or date/time → epoch. Common formats are supported, including ISO 8601, MySQL-style datetime, RFC 3339, and millisecond timestamps. Always confirm the timezone when converting human-readable values—timezone mistakes are a frequent source of off-by-hours bugs. The converter runs in your browser, is free, and does not require signup. If you need the same conversions repeatedly from scripts or an AI agent, you can automate them with Thousand API MCP.

How to use

1. Enter a date/time in the input field in any supported form (e.g. ISO 8601, Unix seconds, MySQL DATETIME, regional formats). The format is auto-detected and shown as "Detected format". 2. Select input and output timezones (IANA, e.g. Asia/Tokyo) to see all formats in that zone. 3. Optionally set a custom format (e.g. Y-m-d H:i:s) in "Custom format" to show only that format in the result. Use the copy button next to each result to copy to the clipboard.

Options

Input: date/time string (any of 21 formats) or default Unix seconds (now). Input format is auto-detected. Input/output timezone: IANA (e.g. Asia/Tokyo, America/New_York). Date separator: - or /. Custom format: PHP-style tokens (Y=year, m=month, d=day, H/i/s=time, etc.) for custom output.

Use cases

• Interpreting log timestamps • Matching API date formats • Debugging • Multi-timezone checks

Code Examples

PHP (epoch seconds → ISO 8601 UTC)

Read Only

1<?php
2// Example: 1700000000 is Unix seconds
3echo gmdate('c', 1700000000);

JavaScript (seconds → Date)

Read Only

1// Convert Unix seconds to milliseconds
2const sec = 1700000000;
3new Date(sec * 1000).toISOString();

Python 3 (UTC)

Read Only

1from datetime import datetime, timezone
2
3sec = 1700000000
4datetime.fromtimestamp(sec, tz=timezone.utc).isoformat()

How it works

Conversion is done in the browser with date-fns and date-fns-tz; nothing is sent to a server. The input string is matched against 21 format patterns, parsed to a Date, then formatted with formatInTimeZone in the chosen IANA timezone. Custom format tokens (Y-m-d H:i:s style) are mapped to date-fns format strings for output. ■ Supported formats • ISO 8601: International standard. e.g. 2026-01-16T19:11:05+09:00 • ISO 9075: SQL standard date/time (DATE, TIME) • RFC 3339: Internet date-time (subset of ISO 8601). e.g. 2026-01-16T19:11:05+09:00 • RFC 7231: HTTP Cookie Expires. e.g. Wed, 21 Oct 2026 07:28:00 GMT • Unix timestamp (seconds): Seconds since 1970-01-01 00:00:00 UTC • Unix timestamp (ms): Same, in milliseconds • Unix timestamp (µs): Same, in microseconds • LDAP Timestamp: 100-nanosecond intervals since 1601-01-01 UTC (used in Active Directory, etc.) • Windows FileTime: 100-nanosecond intervals since 1601-01-01 UTC (Windows API) • Excel date/time: Serial date from 1900 epoch (decimal for time. e.g. 46038.4240) • Japanese: e.g. 2026年01月16日 19時11分05秒 • American: e.g. Jan 16, 2026 or Jan-16-2026 10:10:49 • American numeric: e.g. 1/16/2026 (month/day/year) • British: e.g. 16-01-2026 (day first) • European: e.g. 16.01.2026 • Chinese: e.g. 2026年1月16日 • JavaScript Date: Output of new Date().toString() or toISOString() • JSON: ISO 8601 string (dates in JSON are strings) • MySQL DATETIME: YYYY-MM-DD HH:MM:SS • MySQL TIMESTAMP: Same format (MySQL TIMESTAMP type) • PostgreSQL: ISO-style or YYYY-MM-DD HH:MM:SS+09

Privacy and data

All parsing and conversion is done in the browser; no input or results are sent to a server.

FAQ

Q: What is a Unix timestamp?: A: Seconds (or milliseconds) since 1970-01-01 00:00:00 UTC, commonly used in APIs, logs, and databases.
Q: Can I convert both ways?: A: Yes. Epoch → date/time and date/time → epoch.
Q: Which formats are supported?: A: Common formats including ISO 8601, MySQL-style datetime, RFC 3339, and millisecond epoch.
Q: Does timezone matter?: A: Yes. Always confirm the timezone when converting human-readable datetimes to epoch.