What a Unix timestamp is
A Unix timestamp counts the number of seconds (or milliseconds, depending on the system) that have elapsed since the "Unix epoch" — midnight UTC on January 1, 1970. Because it's a single number with no time zone attached, it's the format most programming languages, databases, and APIs use internally to store a moment in time unambiguously.
Seconds vs. milliseconds
Unix (POSIX) time is defined in seconds, but JavaScript's Date.now() and many web APIs use milliseconds instead — which is why the same moment can look like 1735689600 in one system and 1735689600000 in another. Always check which unit an API expects before feeding it a raw timestamp.
Worked example
The timestamp 1704067200 (seconds) corresponds to January 1, 2024, 00:00:00 UTC — but converts to a different wall-clock time depending on which time zone you view it in, which is exactly why storing timestamps as raw numbers rather than formatted local strings avoids a whole class of time zone bugs.