JSON Timestamp Converter

How fields get flagged

The parser walks every key in the JSON (including nested objects and arrays) and flags a field as a likely timestamp if its value is either a 10 or 13-digit number in a plausible date range, or a string matching ISO 8601. It's a heuristic, not a guarantee — a field like "user_id": 1752762721 would technically match the number pattern too, so always sanity-check the field name against what gets flagged rather than trusting it blindly.

Working with a single value instead of a full payload? The Timestamp ⇄ Date Converter is faster for that. For finding timestamps in non-JSON text like log output, use the Log Timestamp Finder.