Enter any date format: ISO8601, Unix timestamp, RFC2822, or common date strings
Convert the date to a specific timezone
Supported Input Formats
- • ISO8601: 2024-11-29T18:30:22+07:00
- • Unix timestamp: 1638316800
- • RFC2822: Tue, 07 Feb 1984 12:34:56 GMT
- • Common formats: 07/11/2024, 2024-11-29
Output Formats
Enter a date or timestamp to see formatted outputs
ISO 8601 Formatter converts dates to and from ISO 8601 standard format (YYYY-MM-DDTHH:mm:ss.sssZ)—the international date/time interchange format used by APIs, databases, and JSON. Enter a date in any common format (MM/DD/YYYY, DD-MM-YYYY, natural language like 'yesterday' or '3 days ago') and get ISO 8601 output, or paste ISO 8601 to convert to readable local format. I use this when preparing data for REST APIs (most APIs expect ISO 8601 in request bodies), debugging API responses with timestamps, converting database dates for JavaScript Date() constructor, and ensuring timezone consistency in distributed systems. The tool handles UTC, local time, and custom timezone conversions with DST awareness.
Tips & Best Practices
**API integration tips**: Always store dates as ISO 8601 in databases and APIs—it's unambiguous, sortable as strings, and supported everywhere. JavaScript's toISOString() outputs UTC with Z suffix (e.g., 2024-12-26T12:00:00.000Z); some APIs require timezone offset instead (+00:00 format)—check API docs. Common gotchas: user's local time vs server time—always clarify timezone expectations. ISO 8601 without Z or offset is ambiguous. For date-only (no time), use YYYY-MM-DD format; don't include time if precision not needed (avoids midnight edge cases). Remember: ISO 8601 week dates (YYYY-Www-D) are different from month dates—W01 can be in December or January. For scheduling/calendars, consider iCalendar format (RFC 5545) instead.
iso8601-formatter/example.js