Computers do not think about time the way people do. People think in dates and clock times, with months, weekdays, and time zones. Computers, for most purposes, think in a single number: the count of seconds since 1 January 1970, at midnight UTC, an instant known as the Unix epoch. That number is called a Unix timestamp, or epoch time, and it appears everywhere in software: in database records, in log files, in web addresses, in file metadata, and in the data exchanged between systems. The Unix Timestamp Converter on FreeToolZones translates between that number and human-readable dates in both directions, handling seconds and milliseconds, local time and UTC.
This article explains what a Unix timestamp is, how to use the converter in both directions, and how developers, analysts, and curious users apply it to debugging, log reading, and data checking. It also covers the important distinction between seconds and milliseconds, the role of your local time zone in the conversion, the tool’s honest limitations, and answers to the questions people ask most often. The tool has a timestamp field, a unit selector, a date and time field, and four buttons: Convert Timestamp, Convert Date, Use Current Time, and Copy Result.
What Is the Unix Timestamp Converter?
The Unix Timestamp Converter is a free online tool that converts between Unix timestamps and readable dates. A Unix timestamp is the number of seconds, or in some systems milliseconds, that have elapsed since the Unix epoch: 00:00:00 UTC on 1 January 1970. The epoch is a fixed reference point, and every moment since then has a unique timestamp. Because a timestamp is a single number with no time zone attached, it unambiguously identifies a moment, and systems in different time zones can agree on it exactly. The readable date for that moment differs by time zone, but the timestamp is the same everywhere.
The tool is organized in two sections. The first section, labeled “Timestamp to Date,” takes a Unix timestamp and a unit choice, seconds or milliseconds, and converts it to a readable date. The timestamp field begins with the current timestamp in seconds, so the tool is ready to demonstrate itself immediately. The second section, labeled “Date to Timestamp,” takes a date and time, understood to be in your browser’s local time zone, and converts it to a timestamp. The date and time field begins with the current local date and time. A hint under that field explains that the conversion uses your browser’s local time zone, which is an important detail, explained further below.
The Timestamp to Date result is a table with five rows: the local time, the UTC time in ISO 8601 format, the UTC string, the seconds since the epoch, and the milliseconds since the epoch. Showing both the local and UTC forms side by side is the heart of the tool, because it makes the time zone relationship visible: the same moment has one UTC reading and a different local reading, and the timestamp is the same for both. The Date to Timestamp result shows three figures: the seconds since the epoch, the milliseconds since the epoch, and the UTC time in ISO 8601 format.
The Use Current Time button fills both sections with the current moment: it sets the timestamp field to the current epoch seconds, sets the unit to seconds, sets the date and time field to the current local date and time, and immediately runs the Timestamp to Date conversion. It is the fastest way to see the current timestamp and its readable forms, and it is useful as a reference point when comparing a timestamp from a log with the present moment. The Copy Result button copies a summary of the most recent conversion, with the local and UTC readings for a timestamp conversion, or the seconds and milliseconds for a date conversion.
How to Use the Unix Timestamp Converter
The tool works in two directions. Use the direction that matches the value you already have.
Converting a timestamp to a date
- Find the “Timestamp to Date” section. Enter the Unix timestamp in the Unix timestamp field. The field begins with the current timestamp in seconds; replace it with the value you want to convert.
- Choose the unit in the Unit selector: “Seconds since epoch” or “Milliseconds since epoch.” This choice matters enormously, as explained below. Most Unix timestamps in logs and databases are in seconds, while timestamps from JavaScript and many web systems are in milliseconds.
- Click the Convert Timestamp button. A table appears showing the local time, the UTC ISO 8601 time, the UTC string, and the timestamp in both seconds and milliseconds.
- Read the row you need. Use the local time row for what the moment looked like on your clock, and the UTC rows for the zone-independent reading. The seconds and milliseconds rows let you convert the value between units.
Converting a date to a timestamp
- Find the “Date to Timestamp” section. Pick a date and time in the field labeled “Date and time (your local time).” The field begins with the current local date and time.
- Remember that the entered date and time is read as your browser’s local time, as the hint explains. If you mean a time in another zone, convert it to your local time first with the Time Zone Converter, or interpret the result accordingly.
- Click the Convert Date button. Three figures appear: seconds since the epoch, milliseconds since the epoch, and the UTC ISO 8601 time.
- Use the seconds figure for most Unix systems and the milliseconds figure for JavaScript and systems that expect milliseconds. The UTC figure confirms the moment in zone-independent form.
Here is a worked example in each direction. Suppose a log file contains the timestamp 1700000000. Enter it, leave the unit on seconds, and click Convert Timestamp. The table shows the corresponding date in November 2023, in both local and UTC forms, with the milliseconds value of 1700000000000 alongside. Now suppose you need the timestamp for 1 January 2025 at midnight local time. Enter that date and time in the Date to Timestamp section and click Convert Date. The seconds figure is the timestamp for that local moment, and the UTC figure shows the same moment in UTC, which may fall on 31 December 2024 if your zone is ahead of UTC.
If you see an error message asking for a numeric timestamp, the timestamp field holds something that is not a number. If the message says the timestamp is out of range, the value is too large or too small for the browser’s date handling. For the date direction, an error asking for a valid date and time means the field is empty or unreadable. Fix the input and convert again. The tool runs in your browser with no sign-up, and nothing is saved.
Key Features of the Unix Timestamp Converter
The tool’s features address the real difficulties of timestamp work: the seconds-versus-milliseconds confusion, the local-versus-UTC distinction, and the need for a current reference value.
Two-way conversion
The tool converts in both directions, timestamp to date and date to timestamp, on a single page. That matters because timestamp work usually involves both: reading a timestamp from a log to understand when something happened, and creating a timestamp to query a system, set an expiry, or test a function. Having both directions together means the output of one can be checked by running it through the other.
Seconds and milliseconds support
The unit selector distinguishes seconds since the epoch from milliseconds since the epoch. This distinction is the single most common source of timestamp errors. A milliseconds value read as seconds gives a date tens of thousands of years in the future, and a seconds value read as milliseconds gives a date in January 1970. The tool’s table always shows both units for a timestamp conversion, so you can see the relationship: milliseconds are seconds multiplied by 1,000. If a conversion gives a wildly wrong date, the unit is almost always the cause, and switching the selector fixes it.
Local time and UTC shown together
The Timestamp to Date table shows the local time, the UTC ISO 8601 time, and the UTC string for the same moment. Seeing all three together prevents the classic error of treating a UTC reading as a local reading, or the reverse. The ISO 8601 UTC form, ending in Z, is the standard form for exchanging moments between systems, and the UTC string is the familiar human-readable form used in email headers and HTTP dates.
Use Current Time button
The Use Current Time button fills both sections with the present moment and runs the conversion immediately. It provides a live reference: the current timestamp in seconds, the current local time, and the current UTC time, all consistent with each other. It is the fastest way to answer “what is the current Unix timestamp” and the easiest way to check whether a timestamp from a log is recent or old.
Copy-ready summaries
The Copy Result button copies a summary of the latest conversion. For a timestamp conversion, the summary gives the local and UTC readings. For a date conversion, it gives the seconds and milliseconds. The summaries are short enough to paste into a chat message, a bug report, or a code comment, and they carry enough context to be understood without the tool open.
Practical Use Cases With Concrete Examples
Unix timestamps are the working language of time in software. The examples below show where conversion between timestamps and dates is a daily task.
Reading logs and debugging
Server logs, application logs, and database records often store times as timestamps. When a user reports a problem “around 2 PM,” a developer finds the relevant log entries by converting 2 PM local time to a timestamp range, or converts the timestamps in the log to readable times to find the matching entries. The converter’s local and UTC rows help here, because logs may be written in UTC while the report is in local time. Converting both ways and comparing the UTC figures resolves the discrepancy.
Working with web APIs and databases
Many web APIs accept or return timestamps. An API that takes a “since” parameter in epoch seconds needs a timestamp for the cutoff date, which the Date to Timestamp direction provides. An API response containing a timestamp needs conversion to a readable date for display or for a report, which the Timestamp to Date direction provides. Databases that store epoch values, rather than date columns, need the same translations when records are inspected or exported. The milliseconds support matters here, because JavaScript-based systems commonly use milliseconds, while many server systems use seconds.
Setting expiries, schedules, and countdowns
Tokens, sessions, cookies, and scheduled jobs often carry expiry times as timestamps. To set an expiry 24 hours from now, find the current timestamp with Use Current Time, add 86,400 seconds, and use the result. To check when a token expires, convert its timestamp and read the local time. Countdowns and timers in code are often computed by subtracting the current timestamp from a target timestamp, and the Date to Timestamp direction gives the target value for a chosen date and time.
Forensic and record-checking work
File timestamps, message timestamps, and transaction records are sometimes presented as raw epoch values in exports. Converting them to readable dates is the first step in understanding a sequence of events. The converter’s UTC rows are important in this work, because records from different systems should be compared in UTC to avoid time zone confusion. Note the date direction’s local-time reading: when reconstructing a timeline, convert every timestamp to UTC and compare the UTC figures, rather than mixing local readings from different zones.
Learning and teaching how computers handle time
The converter is also a teaching tool. Entering round timestamps, such as 0, 1,000,000,000, and 2,000,000,000, and reading the resulting dates, makes the epoch system concrete: zero is the epoch itself, one billion seconds is September 2001, and two billion seconds is May 2033. Students learning programming can use the tool to check their own timestamp calculations before running code, and to understand why the same moment has different clock readings in different zones but only one timestamp.
Tips and Best Practices
- Check the unit first. Before converting, ask whether the value is in seconds or milliseconds. A 10-digit value is usually seconds, and a 13-digit value is usually milliseconds. If the converted date is wildly wrong, switch the unit and try again.
- Compare moments in UTC. When comparing timestamps from different systems or zones, use the UTC rows, because UTC has no daylight saving changes and no local offset. Local readings are for human context, UTC readings are for comparison.
- Remember the date direction uses local time. The date and time you enter is read as your browser’s local time. If you mean a UTC time, convert it to local time first, or account for your offset when reading the result.
- Use Use Current Time as a sanity check. Before converting an unfamiliar timestamp, note the current timestamp. If the unfamiliar value is close to it, the event is recent; if it is far smaller, the event is old; if it is far larger, check the unit.
- Keep seconds and milliseconds labeled in your own notes and code. Write “epoch seconds” or “epoch ms” next to every timestamp value you record, so a future reader, including yourself, does not have to guess.
- Verify round trips. After converting a date to a timestamp, convert the timestamp back to a date and confirm you get the original date and time. The tool makes this check quick, and it catches unit and zone mistakes.
- Copy the summary with its labels. The copied text includes the local and UTC labels or the seconds and milliseconds labels, which keeps the numbers meaningful when pasted into a bug report or message.
Limitations to Know Before You Rely on the Result
The Unix Timestamp Converter works with the timestamp systems it labels: seconds and milliseconds since the Unix epoch. It does not handle microseconds, nanoseconds, or other epoch systems, such as the Windows file time epoch or the Excel date system, and values in those systems will convert to meaningless dates if entered here. The date direction reads the entered date and time as your browser’s local time, so it cannot directly convert a date and time stated in another zone; convert that time to your local time first with the Time Zone Converter.
The tool’s range is limited by your browser’s date handling. Extremely large or small timestamps produce an out-of-range error rather than a date. The tool does not account for leap seconds, because Unix time, as implemented in browsers, treats every day as exactly 86,400 seconds and does not insert leap seconds. For most software work, that is the expected behavior, matching how systems actually store Unix time, but it means Unix timestamps are not a precise measure of elapsed physical seconds across leap-second boundaries. The tool does not save results or keep a history; use Copy Result to keep a conversion.
Frequently Asked Questions
What is the Unix epoch?
The Unix epoch is 00:00:00 UTC on 1 January 1970. It is the reference point from which Unix timestamps count. A timestamp of zero is that exact moment, a timestamp of 1 is one second later, and negative timestamps represent moments before the epoch, although negative values are less common in everyday use.
Should I use seconds or milliseconds?
It depends on the system that produced or will consume the value. Traditional Unix systems, many databases, and many APIs use seconds. JavaScript’s Date methods and many web systems use milliseconds. Check the digit count as a clue: 10 digits usually means seconds, 13 digits usually means milliseconds. When in doubt, try seconds first and check whether the date is sensible.
Why does the same timestamp show different local and UTC times?
Because local time is UTC plus your zone’s offset, which varies by zone and by daylight saving rules. The timestamp identifies a single moment; the clock reading for that moment depends on where you are. The UTC reading is the same everywhere, and the local reading is the UTC reading shifted by your offset.
What time zone does the Date to Timestamp conversion use?
It uses your browser’s local time zone, as the hint under the field explains. The date and time you enter is interpreted as local time. To convert a time stated in another zone, first convert it to your local time with the Time Zone Converter.
What does the Use Current Time button do?
It fills the timestamp field with the current epoch seconds, sets the unit to seconds, fills the date and time field with the current local date and time, and immediately converts the timestamp to a date. It gives you the current moment in all the tool’s formats at once.
Can timestamps represent dates before 1970?
In principle, negative timestamps represent moments before the epoch, and the browser’s date handling supports a range of negative values. In practice, pre-1970 timestamps are uncommon, and very old dates may behave inconsistently across systems. For historical dates, use the date calculators on this site rather than timestamps.
Related Tools
These related tools on FreeToolZones cover neighboring date and time questions:
- Epoch Time Converter – another converter for epoch time values.
- Date Format Converter – rewrite a date and time in fourteen formats, including a Unix timestamp.
- Time Zone Converter – convert a date and time between twenty-five time zones.
- JS Date Formatter – format dates for JavaScript work.
- World Clock – see the current time and date in major cities, updating every second.