# Tradeoffs/issues with using multiple Rich Text fields?

**URL:** <https://community.fibery.io/t/tradeoffs-issues-with-using-multiple-rich-text-fields/6328>\
**Category:** Misc\
**Created:** [June 27, 2024, 8:59pm UTC](https://community.fibery.io/t/tradeoffs-issues-with-using-multiple-rich-text-fields/6328 "2024-06-27T20:59:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Dejaegher](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ryan_dejaegher/32/8050_2.png) [@Ryan\_Dejaegher](https://community.fibery.io/u/Ryan_Dejaegher)\
**Post date:** [June 27, 2024, 8:59pm UTC](https://community.fibery.io/t/tradeoffs-issues-with-using-multiple-rich-text-fields/6328/1 "2024-06-27T20:59:53Z")

</div>

How many people here are using multiple rich text fields in their databases?

I’m finding them useful as more explicit fields that I can then use formulas with.

For example I have a code snippets database where the **Description** rich text field is a quick overview, but then there is a dedicated rich text field for the actual code snippet. Then I have formula/checkbox that toggles if the code snippet field is empty or not.

Curious how others might be using Rich Text fields and if there are potential performance issues if you use too many

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [June 28, 2024, 10:30am UTC](https://community.fibery.io/t/tradeoffs-issues-with-using-multiple-rich-text-fields/6328/2 "2024-06-28T10:30:07Z")

</div>

No performance issues with this approach. It is a matter of conveniency mainly.

---

<div class="post-metadata">

**Author:** ![Ryan\_Dejaegher](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ryan_dejaegher/32/8050_2.png) [@Ryan\_Dejaegher](https://community.fibery.io/u/Ryan_Dejaegher)\
**Post date:** [July 11, 2024, 5:17pm UTC](https://community.fibery.io/t/tradeoffs-issues-with-using-multiple-rich-text-fields/6328/3 "2024-07-11T17:17:47Z")

</div>

Forgot to follow up on this, but I’d be curious to hear about the origins of multiple rich text fields. To my knowledge Fibery is the only tool that has this concept.

I can see the multiple text fields being useful as a pipeline:

1. Outline
2. Draft
3. Public/Published

Combined with formulas you’d have database entries that can update automatically (has outline? has draft? etc.)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [July 11, 2024, 7:07pm UTC](https://community.fibery.io/t/tradeoffs-issues-with-using-multiple-rich-text-fields/6328/4 "2024-07-11T19:07:08Z")

</div>

> [@Ryan\_Dejaegher](#):
>
> Forgot to follow up on this, but I’d be curious to hear about the origins of multiple rich text fields. To my knowledge Fibery is the only tool that has this concept.

Indeed. Well, initially we designed Fibery closer to Airtable, with connected tables and entities with fields. For us Rich Text was just a field type to add. And when we added it we just made it as with all other fields — you can add many of them. Nothing too fancy 🙂