FIELDS

Rich Text field

Collect formatted answers with Logical Forms Pro Rich Text, choose a toolbar, configure readable-text limits and understand sanitized HTML output.

3 min read · Updated November 19, 2026

Use Rich Text when visitors should format a longer answer with paragraphs, emphasis, lists or links. It is a visitor answer field. Core Content is instead administrator-authored display material, and Paragraph collects plain text.

Availability: Pro.

Add and configure the field

  1. Open the form in Build and add Rich Text from Add fields.
  2. Select its canvas card to open Field options, then configure the controls below.
  3. Save the form and check its saved Preview and embedded page.

Field-specific settings

Setting What it does
Toolbar Basic is the default; Full offers the broader supported editing toolbar. Media upload buttons are not provided.
Rows Initial editor height in text rows. Defaults to 5 and must be positive; this is not an answer-length limit.
Show Code tab Off by default. Offers a Code tab for supported HTML, not arbitrary executable content.
Minimum characters Optional minimum readable-text character count after formatting/whitespace normalization. An empty optional answer remains valid.
Maximum characters Optional maximum readable-text character count. HTML markup itself is not counted as visible answer text.

Applicable shared options

This field also provides Description placement, Validation message placement, Label, Description, Required, Required message, Invalid value message, CSS classes, Hide label, Admin label, Visibility, Default value. See common field options for their behavior.

Review Visible, Hidden and Internal before changing presentation. Static hiding differs from conditional applicability.

Dynamic population offers Disabled, Parameter, Current user. Parameter name binds an external URL or embed value. User property selects the supported WordPress profile value. Submitted or cleared answers are not refilled.

Answers and behavior

The default-content editor provides the initial formatted answer. The public editor uses a native textarea enhanced by the WordPress Classic editor API; it is not the Block Editor. If enhancement fails or JavaScript is unavailable, the textarea remains usable. A repeated copy of the same form can retain an independent textarea where only the first editor instance is enhanced.

Saved content is one sanitized HTML string. Supported passive formatting includes paragraphs, emphasis, lists, headings, blockquotes, code and safe links. Scripts, active forms, media, embeds and shortcodes do not execute. Enabling Code does not bypass that policy.

Required and character counts use decoded readable text, with block/whitespace boundaries normalized. Formatting-only or nonbreaking-space-only content is empty. The HTML document also has a separate 128 KiB resource limit. No input mask or No duplicates control is provided.

Entry details and HTML all-fields notification summaries can preserve supported formatting. Ordinary individual-field tags, searches and CSV use readable plain text rather than exposing the HTML source as the answer.

Example and checks

For a formatted project brief, select Basic, keep Show Code tab off unless visitors need it, and set a maximum readable length that fits your review process. Explain which formatting is useful rather than requiring styling for its own sake.

Test formatted paragraphs, a safe link, an optional blank and a formatting-only answer on a required field. Check the saved entry, plain-text CSV and any HTML notification. Confirm that conditional hiding clears the editor along with its native submitted value.

Use the testing checklist to check validation and the saved entry. Explore all fields provides live examples.