Unix Timestamp Scientific Notation – Why 1.7e9 Is Rejected

Local only

Document the converter's deliberately narrow numeric timestamp input grammar.

Multi-row timestamp converter

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

Row 1Timestamp -> Date
Enter a valid Unix timestamp or ISO 8601 date

Unsupported numeric notation

Why does 1.7e9 not parse as a Unix timestamp?

Although JavaScript can represent 1.7e9 as a number, VetaTool's timestamp input grammar accepts plain decimal digits with an optional sign and decimal fraction. Exponent notation is not part of that grammar, so expand the value before converting it. 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. Identify the exponent-form timestamp.
  2. Expand it to ordinary decimal digits in the source or preprocessing step.
  3. Convert the expanded Unix value and verify its unit.

Numeric meaning and accepted text syntax are different

The converter intentionally recognizes a narrow plain-decimal timestamp pattern before falling back to supported date formats. This avoids silently accepting every JavaScript numeric spelling.

Scientific notation example

1.7e9 is rejected as text; use 1700000000 instead.

Timestamp

1.7e9

Converter result

Enter a valid Unix timestamp or ISO 8601 date

Common questions

Frequently asked questions

Is scientific notation an invalid number?

No. It is valid numeric notation in many contexts; it is simply not accepted by this converter's timestamp text grammar.

Would 1700000000 work?

Yes. Plain decimal digits are accepted as Unix timestamp input.

Debugging a specific Timestamp issue? Browse Timestamp troubleshooting.