> To build a Wix site agentically, or add Wix features like bookings or a store to a site you already have, follow https://www.wix.com/headless/skill.md
> 
> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - If a reference page seems to be missing its schema (parameters, return types, or type definitions), append `?schema=true` to its `.md` URL (e.g. `https://dev.wix.com/docs/contexts/contexts/stores/category-info/use-category-info-context.md?schema=true`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: RichTextInputArea Component

## Article: RichTextInputArea Component

## Article Link: https://dev.wix.com/docs/wix-design-system/components/form/rich-text-input-area-component.md

## Article Content:

# RichTextInputArea

_Components/Form_

Interactive docs page: <https://wix-pages.com/design-system-documentation/#/component/richtextinputarea>

## Overview

```jsx
<Box align="center">
  <Box width="50%">
    <FormField label="Description">
      <RichTextInputArea initialValue="It’s important to warm up before tennis. Here's a list of warm-ups to try. They shouldn't take more than five minutes. <strong><em>Rest for 10 seconds between each one.</em></strong><br/> <ol> <li>Jumping jacks</li> <li>Push-ups</li> <li>Crunches</li> <li>Step ups</li> <li>Squats</li> <li>Side plank (15 sec on each side)</li> </ol> <em>Finally, give yourself a pat on the back and start your tennis match.</em>" />
    </FormField>
  </Box>
</Box>;
```

Rich text input areas let users insert and format long sections of text, and add lists and links.

### Do

- Let users add multiple sentences or paragraphs.
- Let users format the text they write.

### Don't

- Don't use for text inputs that are a single line. Use `<Input/>` instead.

### Feature examples

#### Height

Control the height of the text area (excluding the toolbar):

- `minHeight` sets a minimum height in pixels.
- `maxHeight` sets a maximum height in pixels. Once the maximum height is reached, an inner scroll appears.

If undefined, the text area height is dynamic and grows or shrinks based on the user input.

```jsx
<RichTextInputArea minHeight="120px" maxHeight="400px" />;
```

#### Status

Control this component's status by using a `status` prop.

- `error` demonstrates that required input is missing something or the entry was invalid.
- `warning` highlights an input value that might have a significant impact to a user.
- `loading` shows that text is being saved.

```jsx
<StorybookComponents.Stack flexDirection="column">
  <RichTextInputArea status="error" placeholder="Error" />
  <RichTextInputArea status="warning" placeholder="Warning" />
  <RichTextInputArea status="loading" placeholder="Loading" />
</StorybookComponents.Stack>;
```

#### Status message

Add text that explains the status or what action the user should take with the `statusMessage` prop.

Showing the status message inline, directly below the input area is preferred in all default cases.

- To add an accessible inline message, wrap the component in a `<FormField/>` and add the `statusMessage`.
- To add a status message in a tooltip that requires users to hover on the icon, use the `statusMessage` prop.

View more inline status message examples in `<FormField/>`.

```jsx
<StorybookComponents.Stack flexDirection="column">
  <StorybookComponents.Stack flexDirection="column" gap="12px">
    <Text secondary>For all default cases:</Text>
    <FormField status="error" statusMessage="This is an error message.">
      <RichTextInputArea placeholder="See message below" />
    </FormField>
  </StorybookComponents.Stack>
  <StorybookComponents.Stack flexDirection="column" gap="12px">
    <Text secondary>For narrow layouts only:</Text>
    <RichTextInputArea
      placeholder="Hover on status icon"
      status="error"
      statusMessage="This is an error message."
    />
  </StorybookComponents.Stack>
</StorybookComponents.Stack>;
```

#### Text format

This component supports the following formatting:

- Bold
- Italic
- Underline
- Link
- Bullet list
- Numbered list

```jsx
<StorybookComponents.Stack flexDirection="column">
  <RichTextInputArea initialValue="<strong>Bold text</strong>" />
  <RichTextInputArea initialValue="<em>Italic text</em>" />
  <RichTextInputArea initialValue="<u>Underline text</u>" />
  <RichTextInputArea initialValue='<a target="_blank" href="http://www.wix.com">Link</a>' />
  <RichTextInputArea initialValue="<ul><li>Bullet list item</li><li>Bullet list item</li><li>Bullet list item</li></ul>" />
  <RichTextInputArea initialValue="<ol><li>Numbered list item</li><li>Numbered list item</li><li>Numbered list item</li></ol>" />
</StorybookComponents.Stack>;
```

#### Custom button labels

Customize the label for each of the formatting buttons by using a `toolbarButtons` prop.

```jsx
<RichTextInputArea
  placeholder="Hover on the toolbar items to view the custom button labels."
  texts={{
    toolbarButtons: {
      boldButtonLabel: 'Bold',
      italicButtonLabel: 'Italic',
      underlineButtonLabel: 'Underline',
      linkButtonLabel: 'Link',
      bulletedListButtonLabel: 'Bulleted list',
      numberedListButtonLabel: 'Numbered list',
    },
  }}
/>;
```

#### Spell check

Enable standard browser spell check functionality with the `spellCheck` prop. This doesn't work on the IE browsers.

```jsx
<RichTextInputArea
  spellCheck
  initialValue="This text is mispeled. Click here to see the error underlined in red."
/>;
```

#### Disabled

You can disable the whole RichTextInputArea with `disabled` property

```jsx
() => (
  <Box gap="20px" direction="vertical">
    <FormField label="Enabled">
      <RichTextInputArea
        initialValue="<p>Edit this content</p>"
        placeholder="Write something..."
      />
    </FormField>

    <FormField label="Disabled">
      <RichTextInputArea
        disabled
        initialValue="<p>This content is read-only</p>"
        placeholder="Write something..."
      />
    </FormField>
  </Box>
);
```

### Common use case examples

#### Form

The rich text input area is often used when there are multiple paragraphs of text.

When content is longer than a sentence or two, text formatting greatly improves readability and allows people to scan easily.

```jsx
<Card>
  <Card.Header title="Event description" />
  <Card.Divider />
  <Card.Content>
    <FormField label="Add more details about the event">
      <RichTextInputArea
        minHeight="120px"
        placeholder="Add details dates, schedule and speakers."
      />
    </FormField>
  </Card.Content>
</Card>;
```

## Code

```jsx
import { RichTextInputArea } from '@wix/design-system';
```

### Props

| Name | Type | Default | Description |
| --- | --- | --- | --- |
| `backgroundColor` | `string` | — | Sets the background color of the editor. Accepts any CSS color value. |
| `converters` | `RichTextInputAreaConverters` | — | Extends how HTML is turned into editor content and back, so that markup the editor has no model for survives editing. Also applied to pasted HTML. |
| `customButtons` | `{ tooltipText?: string \| undefined; icon?: ReactNode; onClick?: (() => void) \| undefined; disabled?: boolean \| undefined; active?: boolean \| undefined; dataHook?: string \| undefined; }[]` | — | An array of custom toolbar button configs to append after the built-in buttons. |
| `dataHook` | `string` | — | Applies a data-hook HTML attribute that can be used in the tests. |
| `disabled` | `boolean` | `false` | Whether this specific button is disabled (toolbar-level `disabled` also applies) |
| `hiddenActions` | `RichTextInputAreaAction[]` | — | Sets which built-in toolbar actions to turn off, so that their buttons aren't rendered. Existing formatting in `initialValue` or in pasted content isn't affected. |
| `initialValue` | `string` | `'<p/>'` | Sets the initial value to be displayed in the editor. Read once, when the component mounts. To replace the value later, such as after an edit made elsewhere, hold a ref and call `setValue`. |
| `maxHeight` | `string` | — | Defines a maximum height for the editor (it grows by default) |
| `minHeight` | `string` | — | Defines a minimum height for the editor (it grows by default) |
| `onChange` | `(htmlText: string, params: { plainText: string; }) => void` | — | Defines a standard callback function for changes: `onChange(htmlText, { plainText })` |
| `onLinkRequest` | `(currentLink: RichTextInputAreaLinkData \| undefined, selection: { selectedText: string; }) => RichTextInputAreaLinkData \| Promise<...> \| null \| undefined` | — | Replaces the built-in link form with a flow of your own, such as a link picker panel. Receives the link at the selection, if there is one, and the text the selection covers — the same text the built-in form offers for editing. Resolve with link data to apply it — over the whole of a link the selection touches, over the selected text, or as text written at a caret — with `null` to detach, or with `undefined` to leave the content untouched. The data replaces the link's rather than adding to it. |
| `placeholder` | `string` | — | Sets a placeholder message to display. |
| `size` | `"small" \| "large"` | `'large'` | Sets the size of the toolbar icons. |
| `spellCheck` | `boolean` | — | Enables browsers spell checking. Doesn't affect IE. In Safari, autocorrects by default. |
| `status` | `"error" \| "warning" \| "loading"` | — | Specifies the status of a field. |
| `statusMessage` | `ReactNode` | — | Defines the message to display on status icon hover. If not given or empty, no tooltip is displayed. |
| `texts` | `texts` | — | Defines text styles to be shown. |

## Testkit

No testkit for this component — it doesn't expose a unidriver testkit.

## Changelog

- **1.340.0** (2026-10-21) — maintenance release, no component-specific changes
- **1.339.0** (2026-10-19) — maintenance release, no component-specific changes
- **1.338.0** (2026-10-15) — maintenance release, no component-specific changes
- **1.335.0** (2026-10-12) — maintenance release, no component-specific changes
- **1.331.0** (2026-10-01) — maintenance release, no component-specific changes
- **1.330.3** (2026-09-29) — maintenance release, no component-specific changes
- **1.330.0** (2026-09-28) — maintenance release, no component-specific changes
- **1.329.0** (2026-09-24) — maintenance release, no component-specific changes
- **1.328.0** (2026-09-22) — maintenance release, no component-specific changes
- **1.326.0** (2026-09-17) — fix: release the minimum width in a narrow container ([#17088](invalid-url)) — has visual changes
- **1.325.0** (2026-09-17) — maintenance release, no component-specific changes
- **1.324.0** (2026-09-14) — maintenance release, no component-specific changes
- **1.323.0** (2026-09-10) — maintenance release, no component-specific changes
- **1.312.0** (2026-08-14) — maintenance release, no component-specific changes
- **1.310.0** (2026-08-10) — maintenance release, no component-specific changes
- **1.309.0** (2026-08-06) — feat: a new `hiddenActions` prop turns off built-in toolbar buttons — `'bold'`, `'italic'`, `'underline'`, `'link'`, `'bulletedList'` and `'numberedList'`. Formatting already present in `initialValue` or in pasted content is kept. ([#16743](invalid-url)) — has visual changes
- **1.300.0** (2026-07-20) — feat: add size prop ([#16573](invalid-url)) — has visual changes
- **1.295.0** (2026-07-03) — maintenance release, no component-specific changes
- **1.292.0** (2026-06-22) — maintenance release, no component-specific changes
- **1.291.0** (2026-06-19) — maintenance release, no component-specific changes
- **1.282.0** (2026-05-27) — fix: insert link popover behind modal ([#16300](invalid-url)) — has visual changes
- **1.279.0** (2026-05-13) — maintenance release, no component-specific changes
- **1.273.0** (2026-04-30) — maintenance release, no component-specific changes
- **1.271.0** (2026-04-22) — maintenance release, no component-specific changes
- **1.270.0** (2026-04-20) — fix: made more mobile friendly ([#16158](invalid-url))
- **1.266.0** (2026-04-07) — maintenance release, no component-specific changes
- **1.261.0** (2026-03-24) — maintenance release, no component-specific changes
- **1.260.0** (2026-03-17) — maintenance release, no component-specific changes
- **1.258.0** (2026-02-23) — feat: allow to pass custom buttons to the toolbar ([#15949](invalid-url))
- **1.250.0** (2026-01-27) — fix: added focus box shadow ([#15865](invalid-url))
- **1.247.2** (2026-01-21) — maintenance release, no component-specific changes
- **1.241.0** (2025-12-17) — maintenance release, no component-specific changes
- **1.220.0** (2025-09-29) — maintenance release, no component-specific changes
- **1.212.0** (2025-08-11) — maintenance release, no component-specific changes
- **1.138.1** (2024-10-30) — maintenance release, no component-specific changes
- **1.129.0** (2024-09-25) — maintenance release, no component-specific changes
- **1.127.0** (2024-09-12) — fix: do not prepend communication links with http ([#14122](invalid-url))
- **1.116.0** (2024-07-22) — feat: add focus/blur public API ([#13971](invalid-url))
- **1.115.0** (2024-07-17) — maintenance release, no component-specific changes
- **1.102.0** (2024-04-16) — maintenance release, no component-specific changes
- **1.93.0** (2024-02-08) — maintenance release, no component-specific changes
- **1.92.1** (2024-02-05) — maintenance release, no component-specific changes