TIME & DATA · LOCAL PROCESSING
Unix Timestamp Converter
Convert Unix timestamps and ISO dates without losing digits. Inspect one value or a full list, see another time zone, and download every result.
Seconds, milliseconds, microseconds and nanoseconds stay exact. Your input stays on this device.
Convert timestamps
Choose the unit used by your data. Units are never guessed from the number of digits.
UTC is always included. Named-zone views show the exact offset at each instant; time-zone rules come from your browser.
Paste up to 10,000 nonblank lines. Blank lines are skipped; reports retain the original line numbers and text.
0 / 2,000,000 text units
Import replaces the input after successful UTF-8 decoding. One value per line; CSV columns are not parsed. File limit: 8 MB, then 2,000,000 text units.
Ctrl + Enter or ⌘ + Enter converts the current input.
Add timestamps, choose their unit, then select Convert.
Conversion results
JSON preserves exact strings. CSV prefixes nonempty text cells with an apostrophe to prevent spreadsheet formulas and digit loss. The apostrophe remains part of the CSV cell.
| Line | Original input | UTC date / error | Display time zone | Unix seconds | Details |
|---|
Exact row values
Copy the complete JSON report
Clipboard access was unavailable. Use your device copy action on the selected report.
Formats, limits and privacy
Epoch input uses an explicit unit and decimal notation. Seconds allow up to 9 fractional digits, milliseconds 6, microseconds 3; nanoseconds are integers. Extra fractional digits, exponents and separators are rejected. Values before 1970 and after 2038 are supported. The range is ±100,000,000 days from the epoch, subject to the selected zone being displayable.
ISO input requires a date, time with seconds, and Z or a known numeric offset, for example 2026-10-29T14:15:12.123456789+10:00. A single named-zone annotation is allowed, such as [Australia/Brisbane]. Numeric offsets must match that zone exactly. Historical named-zone displays can include offset seconds; use the always-present UTC date for ISO re-input. ISO input offsets use HH:mm. Z identifies an absolute UTC instant; its named-zone annotation is a view. Offset-free wall times, unknown offset -00:00, leap seconds and other annotations are rejected. Calendar scheduling is available in the Calendar Event Generator.
Each line supports 256 text units; input supports 2,000,000 UTF-16 units and 10,000 nonblank rows. Some characters use two units. Blank lines are skipped, and surrounding spaces and tabs are ignored for parsing. Errors remain in the report beside successful rows. Each complete JSON or CSV report supports 8,000,000 text units. A report-limit failure produces no partial export. The preview shows at most 100 rows and 256 text units per cell. Row details show up to 1,000 units per value. Downloads include all rows and complete original inputs.
Worker loading allows 15 seconds; a started conversion has no fixed time limit. Cancel, clear or edit to stop pending work. The copy fallback supports reports up to 1,000,000 units; use Download for larger reports. Inputs, imported files and reports are never uploaded or saved to browser storage. Named time-zone rules can change and depend on the browser's time-zone data.