Skip to main content
Version: Divi 5

HTML Content Field

Purpose​

The HTML Content field type is a non-input field that displays static content inside the form. You can use plain text, WYSIWYG editor output, raw HTML/code, or a Divi layout. It does not submit a value; it is for instructions, terms, or embedded layout.

When to use​

  • Instructions, terms and conditions, or short legal text.
  • Custom HTML or a Divi layout block inside the form.

Key settings​

  • Field — Field Type: html_content, Field Title (optional for display).
  • HTML Content — HTML Content Type (text | editor | code | divi_layout), HTML Content Editor, HTML Content Code, HTML Content Divi Layout.

Top features to configure​

  • HTML content type — Switch between plain text, editor, code, or Divi layout output.
  • Editor mode — Use this for formatted instructions and rich content blocks.
  • Code mode — Use this for custom markup snippets you want embedded in the form.
  • Divi layout mode — Reuse saved layouts as reusable content blocks inside forms.
  • Display-only blocks — Add headings, guidance, or legal text without creating user input fields.

Validation behavior​

  • HTML Content is not a user-input field and does not submit a value.
  • Validation settings for data entry do not apply to this field type.
  • Content rendering depends on the selected content mode and source configuration.

Common mistakes​

  • Expecting HTML Content to appear in form submission data.
  • Placing critical required instructions only in styled content that may be missed on mobile.
  • Using complex custom code without checking front-end rendering and performance.

Verify it works​

  1. Confirm content displays exactly as expected on the front end.
  2. Submit the form and verify no unintended field value is saved for this block.
  3. Test responsive behavior for long text or embedded layout content.

What's Next​

  • Use Step field to organize long forms with instructional content between steps.
  • Review Multistep form for guided step-by-step experiences.
  • Visit FAQ for content-rendering troubleshooting.