Skip to content
Docs navigationBrowse tools →

Tool docs

Timestamp Converter

Convert Unix timestamps and browser-local datetimes without leaving the tab. This guide explains what the tool treats as display-only timezone state, how datetime-local input is interpreted, and where auto-detection can still require a quick sanity check.

Tool

Overview

01

Timestamp Converter

Use the timestamp converter when you need to flip between Unix seconds or milliseconds and a readable datetime fast. Birdor keeps the workflow local, shows the same instant in multiple timezones, and makes the browser-local interpretation of datetime-local inputs explicit.

Guide

Common usage patterns

01

Quick conversion workflow

  • Paste a Unix timestamp and leave unit detection on auto unless your data source is ambiguous.
  • Switch to Datetime → Unix when you have a local datetime from a browser form or UI.
  • Use the timezone controls to compare how the same instant looks in local time, UTC, and a custom IANA zone.
  • Copy the exact seconds, milliseconds, ISO 8601, or human-readable output back into logs, code, or incident notes.

Guide

Edge cases & common pitfalls

01

Interpretation limits to keep in mind

  • datetime-local values do not contain a timezone offset, so Birdor interprets them in the browser local timezone unless you paste a full ISO or RFC3339 string elsewhere.
  • Timezone switching changes display output, not the underlying Unix timestamp.
  • Auto-detection is a heuristic; for unusual historical or far-future values, force seconds or milliseconds explicitly.
  • An invalid custom timezone falls back to UTC display and is called out in the UI instead of silently pretending the zone is valid.

Internals

How it works internally

01

Local parsing and timezone-aware formatting

Birdor parses numeric timestamps locally, validates datetime-local calendar values strictly, formats timezone views with Intl, and keeps recent custom IANA zones in local preference storage. Nothing is sent to a server.