Published at: 2026-09-17
Rich text
Overview
The rich text field provides mixed text and image editing capabilities, suitable for business scenarios that require formatted display, such as product descriptions, announcements, and contract terms. Compared with collaborative rich text, rich text focuses more on single-user editing scenarios. If you need team collaboration editing or CRM object data references, use the collaborative rich text field.
Basic specifications
| Attribute | Description |
|---|---|
| Applicable scenario | Product descriptions, announcements, contract terms, text-and-image content |
| Maximum characters | 131,072 characters |
| Mixed text and image | Supported |
| Platform support | Full support on web, partial support on mobile |
When to use rich text vs. collaborative rich text
| Scenario | Recommended field type | Reason |
|---|---|---|
| Product descriptions, announcements, and other display-only text-and-image content | Rich text | Only requires basic formatting, no collaboration editing needed |
| Contract terms, policies, and other formatted text | Rich text | Requires font color, alignment, and other fine formatting capabilities |
| Team-edited proposal documents | Collaborative rich text | Requires cloud drive files, polls, CRM object references, and other collaboration features |
| Content that references CRM data | Collaborative rich text | Rich text does not support CRM object references |
| Content that embeds cloud drive files or polls | Collaborative rich text | Rich text does not support these two features |
[!TIP] Quick rule: If you only need “attractive text-and-image formatting”, choose rich text. If you need “team collaboration + CRM data references”, choose collaborative rich text. See Collaborative rich text.
Rich text editing capabilities
The following capability matrix is based on the source document and is organized by platform:
| Feature | Web | Mobile (ShareCRM app) | Third-party app |
|---|---|---|---|
| Upload images | Supported | Not supported | Not supported |
| Tables | Supported | Not supported | Not supported |
| Links | Supported | Not supported | Not supported |
| Strikethrough | Supported | Not supported | Not supported |
| Left, right, and justify alignment | Supported | Supported | Supported |
| Font color | Supported | Supported | Supported |
| Bold | Supported | Supported | Supported |
| Italic | Supported | Supported | Supported |
| Emoji | Supported | Supported | Supported |
| Ordered list | Supported | Supported | Supported |
| Unordered list | Supported | Supported | Supported |
| Cloud drive files | Not supported | Not supported | Not supported |
| Polls | Not supported | Not supported | Not supported |
| CRM object references | Not supported | Not supported | Not supported |
| Location | Not supported | Not supported | Not supported |
| Voice | Not supported | Not supported | Not supported |
| Voice to text | Not supported | Not supported | Not supported |
| OCR | Not supported | Not supported | Not supported |
[!NOTE] Rich text provides full editing capabilities on the web, but on mobile and in third-party apps, only basic formatting is supported (bold, italic, lists, emoji, alignment, and font color). For image uploads, tables, and links on mobile, use collaborative rich text.
Configuration highlights
- Default value: Supports fixed text only. Formulas are not supported.
- Filtering limitation: Rich text fields cannot be used as filter conditions for roll-up summary fields or lookup relationship fields.
- Field name: Must be unique within the object.
- API name: Auto-generated by the system. Do not modify unless necessary.
Default values and required settings
Default value
The rich text field default value supports fixed text input only. Formula calculations are not supported.
[!NOTE] The default value is auto-filled when creating a new record in the front end. Users can modify it after pre-filling. After modifying a default value, historical data is not recalculated.
Required configuration
- Field-level required: On the field configuration page, set “Required” to “Yes”. This applies across all scenarios (front-end entry and back-end import). Missing values prevent saving.
- Layout-level required: If the field is required only in specific business scenarios, set it as not required in the field properties. Then, in the specific page layout editor, check “Required”.
- Conditional required: If the required condition depends on the value of another field, configure validation rules.
FAQ
Rich text content is not fully displayed
Cause: The content may have been copied from other pages and carries incompatible text styles.
Solution: Copy the text content out, clear the formatting, and paste it back into the rich text field.