> 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-cms/17.latest/model-your-content/property-editors.md).

# Property Editors

Overview of Property Editors in Umbraco, how they work, the built-in editors available, and how to create custom ones.

A Property Editor is what content editors use to input data on a Document Type. When you create a Data Type in the backoffice, you choose a Property Editor and configure it. Umbraco ships with a wide range of built-in Property Editors, and you can create custom ones.

{% hint style="info" %}
**Are you looking for the Grid Layout or Nested Content?**

These Property Editors were removed in Umbraco version 14:

* Grid Layout
* Nested content

Use the [Block Editor](/umbraco-cms/17.latest/model-your-content/property-editors/built-in-umbraco-property-editors/block-editor.md) or [Rich Text Editor blocks](/umbraco-cms/17.latest/model-your-content/property-editors/built-in-umbraco-property-editors/rich-text-editor/blocks.md) instead.
{% endhint %}

## In this section

* [Built-in Property Editors](/umbraco-cms/17.latest/model-your-content/property-editors/built-in-umbraco-property-editors.md) - the full list of Property Editors that ship with Umbraco.
* [Umbraco Flavored Markdown](/umbraco-cms/17.latest/model-your-content/property-editors/umbraco-flavored-markdown.md) - a Markdown dialect with Umbraco-specific extensions for rich content editing.

## Related Resources

* [Customizing Data Types](/umbraco-cms/17.latest/model-your-content/content-types-and-structure/data/data-types.md)
* [Creating a custom Property Editor](/umbraco-cms/17.latest/extend-your-project/tutorials/creating-a-property-editor.md)


---

# 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-cms/17.latest/model-your-content/property-editors.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.