Epoch2 knowledge base

Epoch time field guide

A practical reference for epoch units, date formats, timezone behavior and everyday conversion work.

Where Epoch2 fits into your work

Make created_at, expires_at, iat, nbf and exp values readable while testing REST endpoints, GraphQL data, JWT claims and webhook deliveries.

Translate times from application logs, telemetry, audit records, alerts and analytics into a timezone that makes incidents easier to follow.

Check epoch columns and date exports from PostgreSQL, MySQL, SQLite, SQL Server, warehouses, caches and document stores.

Confirm values produced by JavaScript, Python, Java, PHP, Go, Ruby, Rust, C#, Kotlin, Swift and other runtimes.

Decode shell output, cron schedules, container events, build pipelines, object metadata and infrastructure automation timestamps.

Normalize date fields for CSV files, spreadsheets, ETL flows, dashboards, reports and warehouse loading jobs.

Check session duration, token expiry, signed requests, security alerts and any rule that depends on an exact moment.

Turn block times, queue messages, transaction records and event-stream offsets into dates people can quickly understand.

Date and epoch representations available in Epoch2
Format	Sample	Typical role
Epoch seconds	`1704067200`	A compact 10-digit value commonly found in Unix tools, APIs and database fields.
Epoch milliseconds	`1704067200000`	A 13-digit value favored by JavaScript, Java and high-resolution event streams.
ISO 8601 / RFC 3339	`2024-01-01T00:00:00Z`	A portable text date for JSON, service payloads, logs and data interchange.
Local date and time	`2024-01-01 02:00:00`	A human wall-clock value whose exact instant depends on the chosen zone.
UTC, GMT and IANA zones	`UTC · GMT+2 · Europe/Sofia`	Fixed offsets and place-based rules, including daylight-saving changes.

Drop in an epoch number, verify its unit and choose the zone used for the readable result.
For the reverse calculation, enter a wall-clock date and identify the zone where it occurs.
Take the output you need: epoch seconds, epoch milliseconds, a local date or ISO 8601.

These phrases describe the date, epoch and developer workflows covered by the same two-way converter.