Rich text editor control in Power Apps

Allows end users to format text inside a WYSIWYG editing area. Output format is HTML.


The Rich text editor control provides the app user a WYSIWYG editing area for formatting text. Control's input and output format is HTML.

Control allows copied rich text (i.e from web browser or Word) to be pasted into the control.

Control's intended use is to format text and does not guarantee to preserve the integrity of the input HTML. All script, style, object and other potentially compromising tags will be removed by the editor. This means that if rich text was created outside of Power Apps, it may not look the same as in the product where it was created.

Currently supported features include:

  • Bold, Italic, Underline
  • Text color, highlight Color
  • Text Size
  • Numbered lists, bullet lists
  • Hyperlinks
  • Clear formatting

To use the control inside a form, select the "Edit multi-line text" card, and customize it by inserting the RTE control.

Key properties

Default – Input property for the initial text value shown in editor.

HtmlText – Output property for the resulting rich text in HTML format.

Additional properties

AccessibleLabel – Label for screen readers. Should describe the purpose of the attachments.

DisplayMode – Whether the control allows adding and deleting files (Edit), only displays data (View), or is disabled (Disabled).

EnableSpellCheck – Whether the browser spell checker is enabled. Note that the this functionality will provide spell checking only in the default language of the browser. Power Apps for Windows doesn't support this property.

Height – The distance between a control's top and bottom edges.

TabIndex – Keyboard navigation order in relation to other controls.

Visible – Whether a control is visible or hidden.

Width – The distance between a control's left and right edges.

X – The distance between the left edge of a control and the left edge of its parent container (or screen, if no parent container).

Y – The distance between the top edge of a control and the top edge of the parent container (or screen, if no parent container).

Accessibility guidelines

Screen reader support

Keyboard support

  • TabIndex must be zero or greater so that keyboard users can navigate to it.


Use Alt+0 while the editor is focused to learn about other keyboard shortcuts.


Can you tell us about your documentation language preferences? Take a short survey.

The survey will take about seven minutes. No personal data is collected (privacy statement).