A Unix timestamp may be correct and still look wrong in your app. That usually happens because the number is being interpreted in the wrong timezone.
If you want to inspect a timestamp quickly in both UTC and local time, use this Unix Timestamp Converter.
Why developers hit this bug
Unix timestamps are timezone-independent values based on elapsed seconds since the Unix epoch. The bug appears when the timestamp is displayed as local time in one place and UTC in another.
Common examples
- Logs show one time but the UI shows another
- Backend values match but frontend rendering is offset by hours
- Users report the “wrong date” even though the stored timestamp is valid
How to debug it
- Convert the timestamp to both UTC and local time.
- Check which timezone the app is using at display time.
- Verify whether the API contract expects UTC or a localized representation.
For format-length issues, see Unix timestamp seconds vs milliseconds: the bug that breaks date conversion.
Unix Timestamp FAQ
Why can a timestamp look wrong even when the math is right?
Because the stored value may be correct while the display layer is using the wrong timezone.
What is the easiest way to debug UTC vs local time issues?
Convert the same timestamp to both UTC and local time, then compare how the app is rendering it.
Are Unix timestamps themselves timezone-based?
No. Unix timestamps are timezone-independent values, but their displayed interpretation can vary.