Runs in your browser. Nothing you enter is uploaded or stored.
To convert a Unix timestamp to a date, paste it into the free Unix Timestamp Converter above and press Convert. It detects whether the number is in seconds, milliseconds, microseconds or nanoseconds, then shows the UTC time in ISO 8601, the time in the zone you choose and how long ago or how far ahead it is. It also works the other way: type a date such as 2026-11-11 04:38:00 and get the timestamp. Paste up to 2,000 lines, one per line, and download the results as a CSV.
Last updated: 11 November 2026. Written by Saad Raza.
Key takeaways
- A Unix timestamp counts the seconds since 1 January 1970 at 00:00:00 UTC. It has no time zone and no daylight saving, which makes it a reliable way to store and compare moments in time.
- Ten digits is a timestamp in seconds, thirteen digits is milliseconds, sixteen is microseconds and nineteen is nanoseconds. Mixing them up gives dates in 1970 or in the distant future.
- The same moment can be written in any time zone. The timestamp stays the same and only the displayed clock time changes.
- When you type a date without an offset, the tool reads it in the time zone you select, so choose the right one.
- Dates before 1970 give negative timestamps.
- The tool runs in your browser. Log lines and event data are not uploaded.
Where timestamps turn up in SEO and marketing work
Timestamps are everywhere once you look at raw data. Server logs and crawl exports record the time of each request. Analytics and tag manager events carry an event time. APIs return created and updated times as numbers. Cookies, tokens and cache headers use expiry times. Structured data and feeds use dates that need to be consistent. When you debug a tracking problem, a failed crawl or a cache that will not clear, one of the first questions is what time a number really means.
Reading them by eye is not possible, and doing the sum in your head across time zones is a good way to make a mistake. A converter gives a quick, checked answer, and the bulk mode lets you convert a whole column at once.
How to use the Unix Timestamp Converter
- Paste timestamps or dates, one per line. You can mix them in the same list.
- Choose the time zone for display, and for reading dates that have no offset. The list includes UTC, Asia/Karachi, Asia/Dubai, Asia/Kolkata, Europe/London, Europe/Berlin, America/New_York, America/Chicago, America/Los_Angeles and Australia/Sydney.
- Press Convert. For each line you see the unit it detected, the seconds and milliseconds, the UTC time in ISO 8601 form, the time in your chosen zone and the relative time.
- Use the Use current time button to fill in the present moment, or Load example to see the tool work.
- Copy the table or download it as a CSV.
How the unit is detected
| Digits | Unit | Example |
|---|---|---|
| Up to 11 | Seconds | 1794353880 |
| 12 or 13 | Milliseconds | 1794353880000 |
| 14 to 16 | Microseconds | 1794353880000000 |
| 17 to 19 | Nanoseconds | 1794353880000000000 |
JavaScript and many web tools use milliseconds. Unix systems, databases and most server languages use seconds. Some tracing and database tools use microseconds or nanoseconds. If the detection is wrong for a very early or very late date, the unit shown in the results tells you what the tool assumed.
A worked example
The example has six lines. The first is 1794353880, which the tool reads as seconds. It is 23:38:00 UTC on 10 November 2026, which is 04:38 on 11 November 2026 in Karachi, where the time zone is five hours ahead of UTC. The second line, 1794353880000, is the same moment in milliseconds, and gives the same result. The third, 2026-11-11 04:38:00, has no time zone, so with UTC selected it is read as 04:38 UTC, which is 1794371880 in seconds, five hours later than the first line.
Switch the time zone to Asia/Karachi and re-run: the same text now means 04:38 Karachi time, so it converts to 1794353880, the same moment as the first line. That is the whole point of the zone setting. The fourth line, 2026-01-01T00:00:00Z, has an explicit Z for UTC, so it is read as UTC whatever you select, and equals 1767225600. The fifth, 0, is 1 January 1970 at 00:00:00 UTC. The last, 4102444800, is the start of 2100.
Time zones and daylight saving
A timestamp is the same everywhere, but people read local clocks. The converter uses the standard time zone database of your browser to work out the offset on the date in question, so it applies daylight saving correctly for zones that use it. For example, New York is five hours behind UTC in winter and four hours behind in summer, and the same date typed in each season gives a different timestamp.
When a local time does not exist, because the clocks jump forward, or occurs twice, because they go back, the result can be an hour out. For anything that must be exact, such as a scheduled campaign launch or a log from a daylight-saving changeover, use UTC or include the offset in the date, for example 2026-03-29T01:30:00+01:00.
Practical tips
- Debug a tracking gap. Convert the first and last event times in an export to confirm whether a gap is a real outage or a time zone mismatch between reports. For percentage changes between two periods, use the percentage calculator.
- Check cache and token expiry. A header or token with an expiry number can be converted to see exactly when it stops working. Inspect headers with the HTTP header checker.
- Schedule jobs. If you run a job on a schedule, read the schedule in plain English with the cron expression explainer, then confirm the run time here.
- Read log files. Paste a column of timestamps from a log and convert them all at once, then sort in a spreadsheet. Clean up the list first with the remove duplicate lines tool.
- Parse API data. Many APIs return dates inside JSON. Format the response with the JSON formatter and validator or turn it into a table with the JSON to CSV converter, then convert the time column here.
- Use dates in structured data. Schema dates should be in ISO 8601 form with an offset. The ISO column in the results is ready to copy, and you can validate the block with the JSON-LD validator.
For more serious data problems, such as analytics that do not match across tools, an SEO and analytics audit traces where the numbers diverge.
Limits
The converter reads whole or decimal numbers as timestamps and a set of common date formats: year-month-day with an optional time and an optional offset or Z, and anything else your browser’s date parser accepts. Formats that depend on local conventions, such as 03/04/2026, are ambiguous and may be read differently from what you meant, so write dates in year-month-day form. Dates are supported within the range JavaScript can represent, about 270,000 years either side of 1970. Leap seconds are not counted, as in standard Unix time. The relative time is calculated from the moment you press Convert and is rounded. Up to 2,000 lines are converted per run, and any line that cannot be read is marked with an error and does not stop the rest. Everything is processed in your browser, and nothing is sent to a server.
Questions about the Unix Timestamp Converter
What is a Unix timestamp?
It is the number of seconds that have passed since 1 January 1970 at 00:00:00 UTC. It is a simple, time zone free way for computers to record a moment.
How do I know if a timestamp is in seconds or milliseconds?
Count the digits. Ten digits is seconds and thirteen is milliseconds in the present era. The tool detects this for you and shows the unit it used.
What does 0 mean as a timestamp?
It is the Unix epoch: 1 January 1970 at 00:00:00 UTC. Seeing 1970 in a report often means a missing date was stored as zero.
Why is my converted time off by a few hours?
Usually a time zone mismatch. Check which zone the date was written in and which zone you selected. If the source did not say, ask, or compare with a time you know.
Is my data uploaded?
No. Conversion happens in your browser, so log lines and event data stay on your device.
If you want help with analytics and technical SEO, see my SEO services or ask for a free audit. You can also browse the other free technical SEO tools.
Request received
Thank you! Saad will contact you within the next 24 hours.
Keep an eye on your phone and inbox.
