> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/data/collections/field-types/date.md). # Date Fields Learn about Date fields in Noloco tables Date fields specialize in storing date values and are beneficial for incorporating date-specific information such as event days or birthdates. An example value could be '2023-09-25'. These fields provide diverse date formatting options like YYYY-MM-DD and come with a user-friendly date picker for input. ## Date Field Formats * **Date** Store only a date, this is useful for things like birthdays or multi-day events, where time doesn't come into play * **Date & Time** This is the default behavior, store a date and time. Date times will be displayed in the user's local timezone as described in [Dates & Timezones](/field-formatting/dates-and-time-zones.md) * **Use a consistent Timezone** When using a Date & Time field you can specify that all of your dates use the UCT timezone, which is useful if you need a consistent time across all devices, regardless of location ## Use Cases Date fields are ideal for: * Event scheduling and deadlines * Birth dates and anniversaries * Created and updated timestamps * Project milestones * Appointment booking ## Working with Timezones When using Date & Time fields, Noloco automatically handles timezone conversion based on each user's location. For applications requiring consistent global time, enable the "Use a consistent Timezone" option to store all dates in UTC. ## Integration with Views Date fields work seamlessly with: * [Calendar views](/views/display/calendar.md) for scheduling * [Timeline views](/views/display/timeline.md) for project tracking * Filtering and sorting options in all view types --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guides.noloco.io/data/collections/field-types/date.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.