Quick reference
| Setting | Value / behavior |
|---|---|
| Epoch | 1970-01-01T00:00:00Z |
| 1 second | 1,000 milliseconds |
| Text input | explicit timezone |
How to use the result
Unix time measures elapsed time from 1970-01-01T00:00:00Z using the common POSIX convention. Many APIs use seconds, while JavaScript Date uses milliseconds. Choose the input unit explicitly rather than relying on the number of digits, because older dates and negative timestamps break simple length heuristics. For date text, enter an ISO timestamp with a visible Z or numeric timezone offset. A date with no timezone is intentionally rejected to avoid a hidden local-time assumption.
Limits and interpretation
The result includes UTC ISO text, integer Unix seconds, Unix milliseconds and the browser’s local representation. Negative values represent dates before the epoch. Date precision is limited to milliseconds, and the JavaScript Date range applies. The seconds output is rounded down with Math.floor, including for negative times. Leap seconds are not modeled. For future appointments, store the relevant civil timezone as well as an instant because daylight-saving rules and local schedules are separate from UTC timestamps.
Check against your destination
Run the supplied example first, then replace it with a representative input from your own workflow. Change one parameter at a time so the effect is easy to inspect. Copy or download the output and compare it with a small known case before using it in a larger system. A successful calculation establishes only the behavior described on this page; it cannot check the assumptions or access rules of a remote application. Errors are shown next to the workspace rather than silently returning an empty success.
Local processing and data handling
This tool runs in the browser and does not transmit the entered content to a processing service. No input is saved to local storage, added to the URL or synchronized to an account. The clear control removes the current field and displayed result from this page. Clipboard contents and downloaded files remain under your operating system’s control. Keep original inputs when exact byte preservation matters, and avoid including sensitive tokens or private text in screenshots that you later share.
Frequently asked questions
Does the tool contact my server?
No. It processes the provided input locally and does not execute commands on your systems.
Can I download the result?
Yes. Use the Download result control after a successful run.
What happens to my input?
It remains in this page until cleared or closed. It is not saved by the tool.
About this tool
Built and maintained by Mihai at Void Fabric. This page documents the behavior of the current implementation. Found an error or an unclear assumption? Send a reproducible example with sensitive values removed.
Reference: Void Fabric field notes · Testing and editorial policy