Timestamp and date tools for Unix time, APIs, logs, and tokens
Time bugs often come from unit confusion, timezone assumptions, or values copied from tokens and logs without context. These tools help convert the value first, then connect it to the API, JWT, or log workflow where it appeared.
Tools in this workflow
Converters
OpenTimestamp Converter
Convert Unix seconds, Unix milliseconds, and ISO date strings with readable UTC and local output.
API & Auth
OpenJWT Expiry Checker
Show whether a JWT is expired, valid, or missing expiry claims with readable timestamps.
Dev Debug Helpers
OpenLog Prettifier
Format JSON logs and semi-structured log lines into cleaner readable output for debugging.
Dev Debug Helpers
OpenCron Expression Reader
Interpret common cron expressions, validate input, and explain schedules in human language.
Related guides
How to convert Unix timestamp to date
Convert Unix seconds or milliseconds into readable dates and understand timezone differences in API logs and JWT claims.
How to prettify application logs for debugging
A practical workflow for cleaning log output, extracting stack traces, formatting JSON logs, and sharing useful debugging notes safely.
How to decode a JWT token
Learn how to decode JWT header and payload claims in the browser, read exp and iat values, and avoid common token mistakes.
Cron Expression Examples for Developers
Common cron examples for developer jobs, backups, reports, retries, and operational schedules, with cautions about timezone behavior.
FAQ
How do I know whether a timestamp is seconds or milliseconds?
Unix seconds are usually 10 digits for current dates, while milliseconds are usually 13 digits. Convert both when the source system is unclear.
Why do readable dates differ between tools?
Timezone display settings can differ. Keep UTC and local time visible when debugging API, database, or token expiry issues.