Date inputs

Quick Decision Rules

• Use DateField for one date in a form-like field.
• Use DateRangeField when one control owns start and end dates.
• Use DateTimeField when one stored value is a timestamp.
• Use TimeField for time-only values.
• Use Calendar when the experience should be visibly calendar-first.

By Data Shape

• Single date: DateField
• Start and end date pair: DateRangeField
• Single timestamp: DateTimeField
• Time only: TimeField
• Visual date browsing and picking: Calendar

Common Misclassifications

• Do not split one timestamp into separate date and time fields unless the workflow truly treats them independently.
• Do not use Calendar when the UI really needs a compact field in a form row.
• Do not use DateField for a connected range concept.
• Do not use TimeField when the stored value is actually date-time.

Start Here

• Filters and settings forms: DateField, DateRangeField
• Scheduling or booking flows: DateTimeField, DateRangeField
• Always-visible visual picking: Calendar
• Non-Gregorian calendars, locale, and the ISO date value contract: Dates and calendar systems