RFC 3339 Date-Time Converter

RFC 3339 standardizes a profile of ISO 8601 for internet timestamps: `2026-08-13T14:30:00Z` or `2026-08-13T14:30:00+00:00`. It is the de-facto timestamp format for JSON APIs, cloud SDKs, OpenAPI schemas and configuration files because it is readable, sortable and unambiguous about timezone.

This converter outputs your date-time in RFC 3339 with `Z` (UTC) and with the explicit numeric offset, so you can paste whichever variant your API contract or schema validator expects.

Timezone:
Enter a date-time above to see the conversion results.

RFC 3339 Date-Time Converter Quick Reference

FormatPattern / DescriptionExample 1Example 2
ISO 8601 (UTC)Standard ISO format2026-08-13T14:30:00Z2026-01-01T00:00:00Z
RFC 3339 (UTC)yyyy-MM-dd'T'HH:mm:ss'Z'2026-08-13T14:30:00Z2026-01-01T00:00:00Z
RFC 3339 (with offset)yyyy-MM-dd'T'HH:mm:ssXXX2026-08-13T14:30:00Z2026-01-01T00:00:00Z

* Examples are rendered in UTC for the fixed sample instants above.

When to Use RFC 3339 Date-Time

API request/response timestamps

OpenAPI and JSON API specs commonly require RFC 3339. Generate the exact string (Z or offset) your validator expects before sending requests.

Cloud SDK & CLI usage

AWS, Google Cloud and Azure CLIs accept RFC 3339 for scheduled actions. Convert local times to the required form.

Configuration & data files

Terraform, Kubernetes manifests and CI YAML use RFC 3339 timestamps. Verify generated values match schema constraints.

Frequently Asked Questions

What is the RFC 3339 timestamp format?

`YYYY-MM-DDTHH:mm:ssZ` (UTC) or `YYYY-MM-DDTHH:mm:ss±HH:MM` (offset), e.g. 2026-08-13T14:30:00Z. Seconds are required; fractional seconds are optional.

What is the difference between RFC 3339 and ISO 8601?

RFC 3339 is a profile of ISO 8601: it allows only the calendar date with time and a timezone designator. ISO 8601 additionally defines week dates, ordinal dates and intervals.

Is Z the same as +00:00?

Yes — both mean UTC. `Z` is compact and most common; `+00:00` is required by XML Schema `dateTime` and some strict validators. Use the offset output when a schema demands it.

Does RFC 3339 require UTC?

No — any offset is valid, but UTC (`Z`) is strongly recommended because it makes timestamps independent of server location and comparable across systems.

Related Time Format Converters

ISO 8601 Date & Time Converter
Convert any date-time to ISO 8601 format: extended, basic and interval forms. Free converter with pattern reference, examples and FAQ. UTC & local timezone support.
Unix Timestamp Converter (Epoch Time)
Free Unix timestamp converter. Convert epoch seconds, milliseconds, microseconds and nanoseconds to human-readable dates instantly. UTC & local time, one click copy.
UTC Time Converter (Coordinated Universal Time)
Convert any local time to UTC (Coordinated Universal Time) instantly. See the UTC string, Z-suffixed ISO form and GMT equivalent. Free UTC converter.
RFC 2822 Date Converter
Convert any date to RFC 2822 format (Sat, 13 Aug 2026 14:30:00 +0000) for email headers, HTTP headers and RSS. Free online converter with examples.

All Format Guides

Unix TimestampISO 8601ISO Week DateISO Ordinal DateMilitary TimeDecimal TimeRFC 2822RFC 3339SQL DatetimeJulian DateHTTP DateExcel Serial DateGPS TimeUTC TimeCron Expression
Browse all 50 format guides →

Need to Convert Between All Formats?

Use the main Time Format Converter for instant conversion across 100+ formats — epoch, ISO 8601, RFC 3339, SQL datetime, military time and more in one click.

Open Time Format Converter