> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-forms/19.latest/developer/field-types.md).

# Field Types

Umbraco Forms comes with a number of Field Types to allow you to request certain data in the forms that you design & build. This documentation is to guide specific details about field types that we ship that require some detail in how they work.

## Date Picker

The Date field in the default theme renders a native HTML `<input type="date">`. The browser provides the date picker and shows the date in the visitor's own format. The submitted value is always in the `yyyy-MM-dd` format, so dates from different locales are stored the same way.

The **Minimum date** and **Maximum date** settings render as the input's `min` and `max` attributes.

The view is `/Views/Partials/Forms/Themes/default/Fieldtypes/FieldType.DatePicker.cshtml`. To use a different date picker component, override this view in a custom theme. For more information, see the [Themes](/umbraco-forms/19.latest/developer/themes.md) article.

### Date Picker configuration for custom themes

The default theme doesn't use the `DatePickerYearRange` and `DatePickerFormat` settings. They remain available for a custom theme that renders its own date picker.

For example, to show a range of 100 years, add the following to your `appsettings.json` file:

```json
  "Umbraco": {
    "CMS": {
        ...
    },
    "Forms": {
      "FieldTypes": {
        "DatePicker": {
          "DatePickerYearRange": 100
        }
      }
     }
    }
```


---

# 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://docs.umbraco.com/umbraco-forms/19.latest/developer/field-types.md?ask=<question>&goal=<user_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.