What Is a Timestamp?
A timestamp is a value that records when something happened, such as 1735689600 or 2025-01-01T00:00:00Z. Computers attach one to log lines, database rows, files and messages so events can be ordered and compared. To read one now, go back to Unix Epoch Converter's main tool.
This article is part of learn Unix time. It explains the main kinds of timestamp, shows real examples from production systems, and how to read each one.
Timestamp Meaning in Plain English
The timestamp meaning is simple: a label that says “this happened at that moment”. A short timestamp definition is “a recorded point in time attached to a piece of data”. The word comes from rubber stamps that printed the date and time on paper documents, and computers took over the idea.
What separates a good timestamp from a bad one is how precisely it names the moment. 2025-01-01 names a whole day that starts at different times around the world. 2025-01-01T00:00:00Z names a single second, in UTC, for everyone. Most timestamp bugs come from values that leave out the time zone, so two systems read them differently.
The word also has meanings outside data systems. A video timestamp such as 1:23 marks a position inside a recording, not a moment in history. A trusted timestamp, defined in RFC 3161, is a signed statement from a timestamping authority proving that a document existed at a certain time, which is how code signing and legal records prove their dates. This article is about the first kind: timestamps that record when an event happened in software.
Types of Timestamps: Unix, ISO 8601, Database and Log
There are four types of timestamps you will meet again and again:
| Type | Example | Where it lives |
|---|---|---|
| Unix timestamp | 1735689600 | APIs, JWT tokens, file systems, metrics |
| ISO 8601 / RFC 3339 | 2025-01-01T00:00:00Z | JSON payloads, logs, config files |
| Database date-time | 2025-01-01 00:00:00 | SQL DATETIME, TIMESTAMP and timestamptz columns |
| Log and header dates | 01/Jan/2025:00:00:00 +0000 | Web server access logs, email and HTTP headers |
A Unix timestamp counts seconds (or milliseconds) since 1 January 1970 UTC. It is one integer, so it is compact and easy to compare. Read more in what epoch time is.
An ISO 8601 string writes the same moment as readable text, with the offset built in. It sorts correctly as plain text, which makes it popular in logs and JSON.
A database value depends on the column type. Some types store an instant in UTC; others store a wall-clock time with no zone at all. The timestamp formats guide compares them side by side.
Timestamp Examples You Will Meet in Real Systems
Here are timestamp examples taken from the kinds of systems developers work with every day. All of them describe the same instant, the start of 2025 in UTC.
203.0.113.7 - - [01/Jan/2025:00:00:00 +0000] "GET / HTTP/1.1" 200 512 { "id": 42, "created_at": "2025-01-01T00:00:00Z", "updated": 1735689600 } { "sub": "user-42", "iat": 1735689600, "exp": 1735693200 } Last-Modified: Wed, 01 Jan 2025 00:00:00 GMT {"level":"info","ts":1735689600123,"msg":"order created"} Notice how the JWT's exp is one hour after iat: 1735693200 − 1735689600 = 3,600 seconds. Doing arithmetic like that is the main reason systems store Unix numbers. For JavaScript-heavy stacks, the 13-digit form needs care; the milliseconds to date converter handles those.
How to Read and Convert Any Timestamp
Reading any timestamp comes down to three questions:
- Is it a number or text? A plain integer is almost always Unix time. Text is a formatted date.
- If it is a number, what unit? Count the digits: 10 for seconds, 13 for milliseconds, 16 for microseconds, 19 for nanoseconds.
- If it is text, where is the zone? Look for
Z, an offset like+05:00, or a name likeGMT. If there is none, find out which zone the system that wrote it uses before trusting it.
Once you have those answers, conversion is mechanical. Our Unix timestamp converter answers the first two questions for you, and the current epoch time page shows what “now” looks like for comparison.
Timestamp FAQ
What does a timestamp mean in a log file?
It is the moment the program wrote that line, usually down to the second or millisecond. Log timestamps are most often ISO 8601 strings in UTC, such as 2025-01-01T00:00:00.123Z, or Unix numbers. Check the logging configuration or the line format to see which time zone was used before comparing lines from different servers.
Is a timestamp the same as a date?
Not quite. A date names a calendar day, such as 1 January 2025, which starts at a different moment in every time zone. A timestamp names a single instant, so 2025-01-01T00:00:00Z or the Unix value 1735689600 means exactly one moment worldwide. You can turn a timestamp into a date once you pick a time zone.
Why do some timestamps have a Z at the end?
The Z means the time is in UTC, with zero offset. It comes from ISO 8601 and is read aloud as “Zulu” in aviation and the military. 2025-01-01T00:00:00Z and 2025-01-01T00:00:00+00:00 describe the same instant. A timestamp with no Z and no offset is ambiguous, because the reader has to guess the zone.