Unixタイムスタンプ変換ツール

Unixタイムスタンプを人間が読める日付に即座に変換します。自動タイムゾーン検出、Discordタイムスタンプ対応、リアルタイム変換機能を備えた無料オンラインツールです。

現在のUnixタイムスタンプ
0
年間通算日 - 年間通算週 -

変換

type into any field - the others update live
秒単位(10桁)またはミリ秒単位(13桁)のタイムスタンプを入力してください
ISO calendar date
24-hour, local
自動検出

Formats

click any value to copy
完全な日付と時刻 long local format
-
Unixタイムスタンプ seconds, 10-digit integer
-
日付のみ YYYY-MM-DD
-
時刻のみ HH:MM:SS
-
年間通算日 1-366
-
年間通算週 ISO 8601 week
-
Unixタイムスタンプ(ミリ秒) Date.now()
-
相対時間 distance from now
-
ISO 8601 UTC, RFC 3339 compatible
-

Discordタイムスタンプ

これらの形式をコピーしてDiscordで使用できます。各ユーザーのローカルタイムゾーンで表示されます!
デフォルト 短い日付と時刻
<t:0>
January 1, 1970 12:00 AM
短い時刻 :t
<t:0:t>
12:00 AM
長い時刻 :T
<t:0:T>
12:00:00 AM
短い日付 :d
<t:0:d>
01/01/1970
長い日付 :D
<t:0:D>
January 1, 1970
短い日付/時刻 :f
<t:0:f>
January 1, 1970 12:00 AM
長い日付/時刻 :F
<t:0:F>
Thursday, January 1, 1970 12:00 AM
相対時間 :R
<t:0:R>
54 years ago
Unixタイムスタンプとは?

The integer that tells the truth about time.

Unixタイムスタンプ(エポック時間またはPOSIX時間とも呼ばれます)は、1970年1月1日00:00:00 UTC(Unixエポック)からの秒数のカウントとして時間を追跡するシステムです。この標準化された時間形式は、世界中のプログラミング、データベース、コンピュータシステムで広く使用されています。

Unixタイムスタンプはタイムゾーンに依存せず、世界中で同じ瞬間を表します。これにより、タイムゾーン変換が複雑になる可能性のあるデータベース、API、アプリケーションで日付と時刻を保存するのに最適です。

なぜ私たちのUnixタイムスタンプコンバーターを使うのですか?

即座に変換

ページの再読み込みなしでリアルタイム処理。入力するとすぐに結果が表示されます。

タイムゾーン検出

タイムゾーンを自動検出し、ローカル時間で変換結果を表示します。

信頼性の高い結果

完全な日付、Unix秒、ミリ秒、ISO 8601、相対時間をまとめてわかりやすく変換できます。

Unixタイムスタンプの一般的な用途

ソフトウェア開発

開発者はUnixタイムスタンプを使用して、イベントのログ記録、タスクのスケジューリング、ユーザーアクティビティの追跡、アプリケーション内の時間ベースの操作管理を行います。

データベース管理

Unix形式でタイムスタンプを保存することで、異なるシステム間で一貫した時間表現が保証され、日付計算がより効率的になります。

API統合

多くのAPIは日付と時刻のパラメータにUnixタイムスタンプを使用しているため、人間が読める日付とタイムスタンプの間の変換が不可欠です。

Discordボットとメッセージ

Discordは特別な書式のUnixタイムスタンプを使用して、各ユーザーのローカルタイムゾーンで時刻を自動的に表示します。

DiscordでUnixタイムスタンプを使用する方法

Unix timestamps let you display dates and times that automatically adjust to each viewer's local timezone. This is especially useful for event planning, deadlines, and announcements in international servers.

Use the Discord Timestamps section above to generate the exact tag you need: pick a date and time, then copy the format that matches your message - short time, long date, relative countdown, and more. Paste the tag directly into a Discord message and it will render as a localized timestamp for every viewer automatically.

よくある質問

What is a Unix timestamp?

A Unix timestamp is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC, not counting leap seconds. It is a single integer that represents an exact point in time, independent of any timezone, and is used across programming languages, databases, APIs, and operating systems.

How do I convert a Unix timestamp to a date?

To convert a Unix timestamp to a human-readable date, paste the timestamp into the Timestamp field above and the corresponding Date, Time, and Timezone fields will fill in instantly. The Formats card below shows the same instant in ISO 8601, RFC 2822, local time, UTC, milliseconds, and other common formats.

How do I convert a date to a Unix timestamp?

To convert a date to a Unix timestamp, enter the date and time into the Date and Time fields above, choose your Timezone, and the matching Unix timestamp will appear in the Timestamp field automatically. The conversion is bidirectional, so changing any field updates the others live.

What is the difference between Unix seconds and milliseconds?

Unix seconds count whole seconds since the epoch and produce a 10-digit number today (for example 1778750784). Unix milliseconds count thousandths of a second and produce a 13-digit number (for example 1778750784000). JavaScript's Date.now() returns milliseconds, while most server languages and databases default to seconds.

Are Unix timestamps timezone-aware?

No, Unix timestamps are not timezone-aware. A Unix timestamp represents the same instant in UTC everywhere on Earth - the timezone you select in this converter only affects how the timestamp is displayed in human-readable form, not the underlying integer value.

What is ISO 8601 format and how is it different from Unix time?

ISO 8601 is a human-readable date and time format that looks like 2026-05-14T09:26:24.746Z, whereas Unix time is a machine-readable integer such as 1778750784. ISO 8601 is preferred for logs and APIs where humans need to read the value, and Unix time is preferred for storage, math, and comparisons.

How do I use a Unix timestamp in Discord?

To use a Unix timestamp in Discord, wrap your seconds-precision timestamp in the format . Discord renders the timestamp in each viewer's local timezone automatically. The Discord Timestamps section above generates ready-to-paste tags for every supported format - default, short time, long date, relative time, and more.

What is the Year 2038 problem?

The Year 2038 problem is a bug where 32-bit signed Unix timestamps overflow on January 19, 2038 at 03:14:07 UTC (timestamp 2147483647) and wrap around to a negative number. Modern systems use 64-bit timestamps and are not affected, but older embedded devices, legacy software, and some file formats may need to be updated before that date.

Can a Unix timestamp be negative?

Yes, a Unix timestamp can be negative. Negative Unix timestamps represent dates before January 1, 1970 - for example -1000000 corresponds to December 20, 1969. This converter accepts negative timestamps and handles them the same way as positive values.

How accurate is Unix time?

Unix time is accurate to the second by default and to the millisecond, microsecond, or nanosecond depending on the platform. Standard Unix time ignores leap seconds, so it is not strictly equal to UTC during a leap second event, but for almost every application this difference is irrelevant.

Why Unix Timestamps Exist

Computers store time as a single integer because human date formats are inconsistent and ambiguous. Different regions use different orderings - 12/05 means May 12th in the United States and December 5th in most of Europe. Calendars handle leap years and daylight saving time differently across regions, and parsing a string like 'March 3, 2026 at 5 PM' is meaningless without knowing the timezone. A Unix timestamp sidesteps the entire problem because 1778787000 refers to the same exact instant in Tokyo, Berlin, and São Paulo. Storage is cheap (4 or 8 bytes), comparison is a single integer operation, and arithmetic like 'one hour from now' is just adding 3600.

This is why almost every operating system, programming language, database, and protocol uses Unix time internally. File modification times, HTTP cache headers, JWT expiration claims, session cookies, log entries, cron schedulers, blockchain block times, and message queues all store seconds since the 1970 epoch. When a date appears in a human-friendly format anywhere in a system, it was almost certainly converted from a Unix timestamp at the last possible moment for display purposes only.

The choice to count seconds from January 1, 1970, 00:00:00 UTC was made by Bell Labs engineers designing early Unix systems. It was arbitrary at the time but has since become the most universally agreed-upon way to talk about time in computing. Reading and converting Unix timestamps is a fundamental skill for backend developers, system administrators, API integrators, and anyone debugging logs in a cloud environment - which is why a fast, accurate converter is one of the most-used tools in a developer's daily workflow.