Timestamp / Base64 / URL Encode-Decode

Q: Is the Unix timestamp in seconds or milliseconds?

Standard Unix timestamps are seconds (10 digits); milliseconds are 13 digits. The tool auto-detects: 10 digits as seconds, 13 as milliseconds, 19 as microseconds.

Q: What if Base64 decoding fails?

First check for stray newlines or whitespace; if needed use URL-safe Base64 (- and _ replacing + and /, with = padding). The tool attempts standard decoding and reports input problems.

Q: Difference between URL encoding and encodeURIComponent?

URL encoding is often for query params; encodeURIComponent also encodes reserved chars like / ? &. The tool uses encodeURIComponent semantics, good for encoding a parameter value.

Q: Why is my timestamp conversion off by hours?

That's the UTC vs local-timezone (e.g. UTC+8) difference. The tool shows local time by default; account for the offset if you need UTC.

Pure frontend: pick a mode, type, and the result updates instantly. Nothing leaves your browser.

Convert

Pick a mode, enter content, and the result updates live.

Mode Input

Use cases

Timestamp: what time is 1767225600 in the log? Pick "timestamp to date".
Base64: pass binary or a token in a config/API — encode/decode.
URL encoding: turn &, =, or non-ASCII in a query param value into a safe form.

Log pattern extractor — pair with log extraction
TCP/IP state machine & troubleshooting — server time, timestamps and network basics

Timestamp / Base64 / URL Encode-Decode

Convert

Use cases

Related tutorials