Unix Timestamp Converter
Paste an epoch time from a log, database or API and see the date in UTC, in your own time zone and relative to now. Or type a date to get its Unix time. Seconds and milliseconds are told apart automatically.
- Free
- No upload
- No sign-up
CSV to JSON and JSON to CSV
Quoted fields, line breaks inside cells, semicolon CSV from Excel and JSON Lines are handled.
Base64 encoder and decoder
UTF-8 safe for accents and emoji. Decoding ignores line breaks and missing padding.
Color converter: HEX, RGB and HSL
Type or paste a color in any field, or use the picker. All formats update together.
WCAG contrast
AA needs 4.5:1 for normal text and 3:1 for large text (24px, or 19px bold). AAA needs 7:1 and 4.5:1.
Number base converter
Binary, octal, decimal and hexadecimal. Very large and negative whole numbers are supported.
Spaces and underscores are ignored, and the prefixes 0b, 0o and 0x are accepted. Negative numbers keep a minus sign; for values that fit in 8 to 128 bits the two’s complement form is shown too.
Text case converter
Accented letters such as á, ž and ľ are kept, and ß becomes ẞ in capitals. Code cases are applied line by line.
URL encoder and decoder
Percent-encode text for links and query strings, or decode %20-style text back.
Component encodes every reserved character (/ ? & = #), for a single query value or path part. Full URL keeps the URL structure readable.
Unix timestamp converter
Seconds or milliseconds are detected automatically from the number of digits.
Current Unix time: —
Without Z or an offset such as +02:00, the date is read in your time zone (local).
- Unix time (seconds)
—- Unix time (milliseconds)
—- ISO 8601, UTC
—- ISO 8601, your time zone
—- Readable, your time zone
—- Relative
—
Runs entirely in your browser. Your data, files and text are never uploaded.
Seconds, milliseconds and time zones
A Unix timestamp counts the time since 1 January 1970, 00:00 UTC. Most systems use seconds (10 digits today, such as 1700000000), JavaScript and Java use milliseconds (13 digits), and some databases and tracing tools use microseconds or nanoseconds. The unit is detected from the number of digits, and you can set it yourself.
The same moment is shown as ISO 8601 in UTC, which is what you should store and send between systems, and in your browser's time zone with its offset, which accounts for daylight saving time on that date. A relative line such as "3 hours ago" helps when reading logs.
Microsecond and nanosecond values are divided exactly with big integers, so the millisecond shown is never off by one through floating-point rounding. Signed 32-bit timestamps end on 19 January 2038; this converter handles dates far beyond that.
How to use the Unix Timestamp Converter
- The current Unix time is filled in when the page opens; press Now at any time to refresh it.
- Paste a timestamp; the unit is detected, or choose seconds, milliseconds, microseconds or nanoseconds.
- Or type a date such as 2024-05-01T14:30:00Z; without Z or an offset it is read in your time zone.
- Copy any of the results: seconds, milliseconds, ISO 8601 in UTC or local time, or the readable date.
Frequently asked questions
How do I tell seconds from milliseconds?
Count the digits: a current time in seconds has 10 digits and in milliseconds 13. The converter does this automatically and shows which unit it used.
Is a Unix timestamp in UTC?
Yes. A Unix timestamp has no time zone; it always counts from midnight UTC on 1 January 1970. Time zones only matter when the moment is shown as a date.
What is the year 2038 problem?
Systems that store seconds in a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC. Modern 64-bit systems and this converter are not affected.
Can I convert negative timestamps?
Yes. Negative values are moments before 1970; for example -86400 is 31 December 1969, 00:00 UTC.
More conversions
Code & data
Other categories