Timestamp Generator Online
Unix time ↔ human time.
At a glance
- Processing:
- Runs locally in your browser
- Privacy:
- Nothing you type is sent to a server
Last updated: 2026-10-07
Common use cases
- Decoding an API epoch field while debugging server logs
- Stamping incident notes with both UTC and local time for handoffs
- Converting a release date into epoch seconds for app config
- Checking millisecond feed values from a sensor export file
About this tool
See the current Unix time, convert any timestamp to readable UTC and local dates, and convert dates back to epoch seconds or milliseconds — a unix timestamp converter and epoch converter in one page, with no uploads.
How to use it
- Read 'now' instantly.
- Paste a timestamp to decode.
- Or pick a date to encode.
Practical tips
- Paste seconds or milliseconds as-is. The tool detects 10-digit versus 13-digit input. A 10-digit value means seconds.
- Read both UTC and local lines to avoid zone mix-ups. Compare the two lines before logging.
- Press Refresh on the now card to update the current epoch before copying. The card shows seconds plus millis.
Common mistakes
- Typing commas in the number and seeing an error. Enter plain digits only. Strip spaces first.
- Reading only one zone line. UTC and local can sit on different dates. Note both when filing tickets.
- Expecting seconds precision in the picker. It takes minutes, so add seconds in code if needed. Millis output derives from the minute mark.
How this compares
Server time converters send each value out for parsing, which adds round trips. This tool decodes and encodes in your tab with the browser clock and shows both zones. You give up shared conversion history across devices. You keep instant private time math with no upload. There is no lookup log to clear.
Good to know
- Decode expects plain numbers. Text or commas show a warning.
- Seconds versus milliseconds is guessed from digit count.
- Encode uses a minute-precision picker. There is no seconds field.
Frequently asked questions
Is my data uploaded?
No. Timestamp conversion runs entirely in your browser — nothing leaves your device.
Seconds or milliseconds?
Both: the tool auto-detects 10-digit (seconds) vs 13-digit (milliseconds) input and converts each way, always showing UTC and your local zone.
What timezone are results shown in?
Both: every decoded timestamp displays the UTC (ISO) time and your browser's local time, so timezone confusion is impossible.
Why does my timestamp show two different dates?
UTC and your local zone can straddle midnight. The tool shows both lines so you can see the shift. Trust UTC for logs and local for display. Date math in code should use the epoch value, not the shown string.
How do I get the current timestamp in code?
JavaScript: Math.floor(Date.now() / 1000) for seconds, Date.now() for milliseconds. Python: int(time.time()). PHP: time(). MySQL: UNIX_TIMESTAMP(); PostgreSQL: EXTRACT(EPOCH FROM NOW()). All produce UTC epoch values — paste any of them here to decode.

