11-Digit Unix Timestamp – Seconds or Milliseconds?

Local only

Show a valid 11-digit Unix-seconds value and explain VetaTool's unit threshold.

Multi-row timestamp converter

Compare timestamps and ISO 8601 dates. Inputs without an offset use UTC.

Row 1Timestamp -> Date
1/1/3000, 12:00:00 AM
ISO: 3000-01-01T00:00:00.000ZSeconds: 32503680000Milliseconds: 32503680000000

Unix timestamp magnitude

Can an 11-digit Unix timestamp still be seconds?

Yes. Digit count is only a heuristic. VetaTool interprets absolute numeric values below 100,000,000,000 as seconds, so 32503680000 converts to 3000-01-01T00:00:00Z. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Unix seconds and milliseconds conversion
  • ISO 8601 parsing
  • Explicit timezone interpretation
  • Fractional and negative Unix timestamps
  • Browser-local processing

Steps

  1. Paste the 11-digit value into Timestamp to Date.
  2. Read the ISO result and both unit details.
  3. Confirm the producer's documented unit before relying on digit count.

Timestamp units are semantic, not a fixed digit format

Modern seconds happen to be around ten digits and modern milliseconds around thirteen, but future dates and historical ranges can break that shortcut.

11-digit seconds example

32503680000 seconds is the start of year 3000 UTC.

Timestamp

32503680000

UTC ISO

3000-01-01T00:00:00.000Z

Common questions

Frequently asked questions

Does VetaTool decide units only by digit count?

No. It uses a numeric magnitude threshold of 100,000,000,000.

Should I rely on that heuristic in an API contract?

No. Prefer the producer's documented unit whenever it is available.

Debugging a specific Timestamp issue? Browse Timestamp troubleshooting.