Explain that display-oriented thousands separators are not part of the accepted timestamp grammar.
Multi-row timestamp converter
Compare timestamps and ISO 8601 dates. Inputs without an offset use UTC.
Row 1Timestamp -> Date
Formatted numeric input
Why does a Unix timestamp with commas fail to convert?
Thousands separators are useful for display but are not part of VetaTool's accepted Unix timestamp text format. A value such as 1,700,000,000 must be supplied as 1700000000 before conversion. 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
Remove commas or other thousands separators from the copied value.
Keep the sign and decimal point only when they are part of the actual timestamp.
Convert the clean digits and verify the unit.
Display formatting should be removed before parsing
The timestamp matcher accepts an optional minus sign, digits, and an optional decimal fraction. Commas do not match that grammar and the value is not treated as a date string either.
Comma-separated timestamp example
The formatted display value is rejected until the separators are removed.
Timestamp
1,700,000,000
Converter result
Enter a valid Unix timestamp or ISO 8601 date
Common questions
Frequently asked questions
Can I just delete every comma?
Only when the commas are presentation thousands separators. Preserve the source data's actual decimal conventions and contract.
Does VetaTool auto-strip separators?
No. The current converter requires plain numeric timestamp text.