Convert Unix Timestamps on Mac Without Mixing Up Units or Time Zones

When a log or API response contains a Unix timestamp, check whether the value uses seconds or milliseconds before converting it. Then check which time zone you are reading. In Frset, the Timestamp tool converts numeric timestamps into dates and local date strings back into seconds or milliseconds.

Separate the instant from its display

A Unix timestamp counts time relative to the Unix epoch. The same instant can be displayed differently in UTC and in your Mac's local time zone. Python's date and time documentation explains timestamp conversion and the role of time zones.

For example, 1704067200 seconds and 1704067200000 milliseconds represent the same instant: January 1, 2024 at 00:00:00 UTC. In Asia/Shanghai, that instant is January 1 at 08:00:00. An eight-hour difference between those displays does not mean either underlying timestamp needs eight hours added to it.

Convert a timestamp with Frset

1. Open Frset search and choose Timestamp, using the default /time keyword if unchanged.
2. Select timestamp-to-date mode.
3. Paste the numeric value by itself, without a field name or quotation marks.
4. Run the conversion and inspect the detected seconds or milliseconds unit.
5. Compare the local and UTC outputs, then copy the representation you need.

The tool's output settings can include local time, UTC, ISO 8601 and RFC 3339. If a useful representation is missing, check which outputs are enabled. Successful results are copied to the clipboard and added to history.

For current implementation limits, Frset accepts 9- or 10-digit second values and 12- or 13-digit millisecond values, within the supported range from January 1, 2000 to January 1, 2100 UTC. Negative values, decimal input and dates outside that range are not supported by this tool. Do not treat a rejected value as proof that the source data is invalid for every system.

Convert a local date back to a timestamp

Switch to date-to-timestamp mode and enter a date in yyyy-MM-dd HH:mm:ss form, for example 2024-01-01 08:00:00. Select seconds or milliseconds for the output, then run the tool.

This input is interpreted in the Mac's current time zone. If the Mac is set to Asia/Shanghai, the example corresponds to 1704067200 seconds. In another time zone, the same typed date can represent a different instant. Check the Mac's time zone before converting a scheduled time copied from a colleague.

This field is not a general date parser. Do not paste an ISO date with a Z suffix or an arbitrary natural-language date and assume it will be interpreted correctly. Use the required format and verify the intended time zone separately.

Check three things when a result looks wrong

• Unit: A system expecting milliseconds needs a different numeric value from one expecting seconds. Inspect the API documentation instead of relying only on digit count.
• Zone: Compare UTC and local output before editing the original number. A display offset is not necessarily a data error.
• Meaning: Confirm whether the field records creation, update, expiry or a scheduled event. Converting correctly does not identify the field's purpose.

Copy only the value the destination expects. If it needs a number, do not paste a whole result block containing labels and several date formats. Review an expiry or scheduled time before applying it to a real system.

Keep the source next to the conversion

When investigating a response, keep the field name, original value and expected unit in your working note. The JSON guide helps make the response readable, while clipboard history lets you find the copied source again.

Timestamp conversion runs locally and does not need an AI provider. Available tool usage depends on your Frset plan; the conversion's unit, range and time-zone rules remain relevant whichever plan you use.