Key takeaway
A Unix timestamp counts seconds (or milliseconds) since 1970-01-01 UTC. Systems love integers; humans love calendar dates — converters bridge them.
Time zones and seconds-vs-millis confuse beginners most.
What it means
Seconds vs milliseconds: 10 digits vs 13 digits roughly for modern dates.
UTC is the reference; local display applies offsets.
Leap seconds are rarely your day-to-day issue; offsets are.
When you would use it
Reading API logs, cookies, JWT-ish payloads, database fields, debug traces.
How to use the tool
Use the matching TCB Tools page and work top to bottom:
- Open Unix Timestamp Converter.
- Paste a timestamp or pick a date.
- Confirm seconds vs ms.
- Read UTC and local interpretations.
- Copy the form you need.
No account is required. Results update as you type.
How conversion works + example
Example: 0 → 1970-01-01T00:00:00Z.
Example: 1700000000 seconds is a date in 2023 UTC — convert live to see local.
If your number is ~1e12, try milliseconds.
How to read the result
Always label timezone in communications.
Scheduler bugs love DST edges — test.
Dev aid.
Common mistakes
- Seconds treated as ms. Check length.
- Silent local vs UTC. Label.
- Excel date serial confusion. Different epoch.
- Assuming all systems use seconds. Read docs.
Related ideas
Neighboring debugger tools: JSON and URL encoding.
Store UTC; display local.
Include the raw integer in bug reports.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit Unix timestamps weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure Unix timestamps; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about Unix timestamps, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions Unix timestamps.
If leadership wants only a headline, still keep working notes for Unix timestamps in your own folder.
Seasonality and promotions change Unix timestamps; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for Unix timestamps.
Revisit assumptions about Unix timestamps after tool, tracking or pricing changes.
A short checklist for Unix timestamps beats relying on memory during busy weeks.
Store UTC; display local.
Include the raw integer in bug reports.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit Unix timestamps weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure Unix timestamps; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about Unix timestamps, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions Unix timestamps.
If leadership wants only a headline, still keep working notes for Unix timestamps in your own folder.
Seasonality and promotions change Unix timestamps; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for Unix timestamps.
Revisit assumptions about Unix timestamps after tool, tracking or pricing changes.
A short checklist for Unix timestamps beats relying on memory during busy weeks.
Store UTC; display local.
Include the raw integer in bug reports.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit Unix timestamps weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure Unix timestamps; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about Unix timestamps, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions Unix timestamps.
If leadership wants only a headline, still keep working notes for Unix timestamps in your own folder.
Seasonality and promotions change Unix timestamps; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for Unix timestamps.
Revisit assumptions about Unix timestamps after tool, tracking or pricing changes.
A short checklist for Unix timestamps beats relying on memory during busy weeks.
Store UTC; display local.
Include the raw integer in bug reports.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Try the tools
Open the Unix Timestamp Converter.
