What is the current Unix timestamp?

It changes every second. Open the Timestamp Converter — it shows the live current timestamp. As of early 2026, Unix timestamps are in the 1.77 billion range (10 digits).

How do I convert epoch time to a readable date?

Paste the timestamp into the Timestamp Converter. It auto-detects seconds vs milliseconds and displays the date in multiple formats and timezones. Works in your browser — no account needed.

What is the difference between Unix time and epoch time?

They are the same thing. "Epoch" refers to the starting point (January 1, 1970 UTC). "Unix time" refers to the counting system. Both describe seconds since that epoch. The terms are interchangeable.

How do I make a Discord timestamp?

Get the Unix timestamp for your date from the converter. Then use the format in your Discord message. Replace TIMESTAMP with the number. The F format shows a full date and time that auto-adjusts to each reader's timezone.

Why is my timestamp 13 digits instead of 10?

A 13-digit timestamp is in milliseconds (JavaScript standard). A 10-digit timestamp is in seconds (Unix standard). Divide by 1000 to convert milliseconds to seconds. The converter handles both automatically.

How do I get the Unix timestamp in SQL?

MySQL: UNIX_TIMESTAMP() for current time, UNIX_TIMESTAMP(date_column) for existing dates. PostgreSQL: EXTRACT(EPOCH FROM NOW()) for current time, EXTRACT(EPOCH FROM timestamp_column) for existing dates.

What happens after the Year 2038 problem?

32-bit systems interpreting timestamps as signed integers will overflow on Jan 19, 2038. 64-bit systems are unaffected. Most modern operating systems and databases already use 64-bit timestamps. Legacy embedded systems are the primary concern.

Can I convert timestamps on my phone?

Yes. The browser-based converter works on any device. Useful when debugging API responses or Discord timestamps on mobile.

Unix Timestamp & Epoch Time — Complete Developer Reference (2026)

Last updated: March 20269 min readDeveloper Tools

Quick Reference: Common Epoch Values

Unix timestamp is the number of seconds since January 1, 1970 (UTC). Here are reference points:

Date	Unix Timestamp	Milliseconds
Jan 1, 2000 00:00 UTC	`946684800`	`946684800000`
Jan 1, 2020 00:00 UTC	`1577836800`	`1577836800000`
Jan 1, 2025 00:00 UTC	`1735689600`	`1735689600000`
Jan 1, 2026 00:00 UTC	`1767225600`	`1767225600000`
Jan 19, 2038 03:14 UTC	`2147483647`	Y2K38 — 32-bit overflow

Seconds vs milliseconds: If the number is 10 digits (starts with ~17 in 2026), it is seconds. If 13 digits (starts with ~17xx in 2026), it is milliseconds. JavaScript uses milliseconds. Most APIs use seconds. The Timestamp Converter auto-detects which format you paste.

Timestamp vs Date — Why Both Exist

A common confusion: "Why not just store dates as dates?"

Timestamps are a single integer — 1711843200. No timezone ambiguity. Universally comparable. Sortable. Mathematically manipulable (add 86400 = add one day).
Date strings are human-readable — 2026-03-31T00:00:00Z. But "March 31" means different absolute times in New York vs Tokyo. Formatting varies by locale. Sorting requires parsing.

Use timestamps in databases, APIs, and backend logic. Convert to human-readable dates only at the display layer. This avoids the entire category of timezone bugs that plague applications.

Discord Timestamps — The Most Common Use Case

Discord uses Unix timestamps for dynamic time display. Format: <t:TIMESTAMP:FORMAT>

Format	Code	Example Output
Short time	`<t:1711843200:t>`	12:00 AM
Short date	`<t:1711843200:d>`	03/31/2026
Long date + time	`<t:1711843200:F>`	March 31, 2026 12:00 AM
Relative	`<t:1711843200:R>`	in 2 hours (dynamic)

The beauty: each reader sees the time in their own timezone. No "3pm EST / 12pm PST" confusion. Get the timestamp for any date with the Timestamp Converter and paste the Discord format code into your message.

Batch Conversion and Common Operations

Working with timestamps in bulk — log files, database exports, API responses:

Add time: timestamp + 3600 = +1 hour. timestamp + 86400 = +1 day. timestamp + 604800 = +1 week.
Time difference: subtract two timestamps = difference in seconds. Divide by 3600 for hours, 86400 for days.
Batch convert: paste multiple timestamps into the converter to see all dates at once
SQL conversion: FROM_UNIXTIME(timestamp) in MySQL, to_timestamp(epoch) in PostgreSQL

The Y2K38 Problem

On January 19, 2038 at 03:14:07 UTC, 32-bit Unix timestamps overflow. The value 2147483647 (max 32-bit signed integer) rolls over to a negative number, which 32-bit systems interpret as December 13, 1901.

This is not hypothetical — embedded systems, IoT devices, and legacy databases using 32-bit timestamps will break. 64-bit timestamps extend the range to the year 292 billion, effectively solving the problem. Most modern systems already use 64-bit timestamps, but if you encounter a system that stores timestamps as 32-bit integers, plan the migration before 2038.

Try Timestamp Converter — free, private, unlimited.

Open Timestamp Converter

Unix Timestamp & Epoch Time — Complete Developer Reference (2026)

Quick Reference: Common Epoch Values

Timestamp vs Date — Why Both Exist

Discord Timestamps — The Most Common Use Case

Batch Conversion and Common Operations

The Y2K38 Problem

Related Posts

Epoch Converter for Developers

Cron Expression Guide