# Max length of text field

**URL:** <https://community.fibery.io/t/max-length-of-text-field/1858>\
**Category:** Bugs & Issues\
**Created:** [July 30, 2021, 4:43pm UTC](https://community.fibery.io/t/max-length-of-text-field/1858 "2021-07-30T16:43:36Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [July 30, 2021, 4:43pm UTC](https://community.fibery.io/t/max-length-of-text-field/1858/1 "2021-07-30T16:43:36Z")

</div>

It seems like the Text field cannot take more than 1000 characters.  
Although I can imagine someone reasonably arguing that no-one should need more than 1000 characters for a simple text string 🙄 I have found myself writing formulas that generate text strings (including URLs) that are more than 1000 characters.  
Can the limit be increased? or is there any workaround?

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [March 13, 2026, 9:37am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/2 "2026-03-13T09:37:14Z")

</div>

I was just bitten by this limitation as well.

(Even the User Guide says it should be 5000 characters:  
[Fibery](https://the.fibery.io/@public/User_Guide/Guide/Fields-15/anchor=What's-the-character-limit-for-the-text--c13c0419-0407-440f-b923-974f9d734902))

I hit this limitation in Formula field where it’s output is a text field. Specifically a formula that joins all related entity’s public ids in order to check for “contains”. Using this trick: ["Contains" formula function - #3 by RonMakesSystems](https://community.fibery.io/t/contains-formula-function/10178/3)

After there were 300 related entities, this business critical functionality is now broken…

I think i will edit it to use | instead of {} to reduce character count for the time being, but it’s just a problem waiting to show up again…

1000 characters is really quite small when it comes to data amount… it’s like 1kb… Is there any chance to bump this value up to like 10,000 characters? 10kb? I know everything needs some kind of upper limit, heck even rich text fields have an upper limit (2.7mb), but if we could bump this up, at least until there’s a proper “contains” function in formulas, that would be very appreciated!!

---

<div class="post-metadata">

**Author:** ![philipp](https://avatars.discourse-cdn.com/v4/letter/p/46a35a/32.png) [@philipp](https://community.fibery.io/u/philipp)\
**Post date:** [June 4, 2026, 7:07am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/3 "2026-06-04T07:07:40Z")

</div>

are there plans to increase that limit?

for context, I am fetching content from connected pages via JS, string in text fields, and then creating PDF - currently need to split across 16 text fields so that it works (due to hitting length limit in the text field)

probably not very elegant - how else could I accomplish creating one PDF report accumulating data from connected entities?

---

<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 4, 2026, 7:37am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/4 "2026-06-04T07:37:56Z")

</div>

why you use text fields? why not rich text fields?

---

<div class="post-metadata">

**Author:** ![philipp](https://avatars.discourse-cdn.com/v4/letter/p/46a35a/32.png) [@philipp](https://community.fibery.io/u/philipp)\
**Post date:** [June 4, 2026, 8:12am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/5 "2026-06-04T08:12:28Z")

</div>

tried that

1. the script threw “Cannot parse “” entity “” field” with updateEntity on rich text fields (but not on text fields)
2. I’m injecting each field’s raw string straight into the HTML template, so plain text is what I want. I need the literal HTML string, not a structured doc. My script builds that HTML by collecting and formatting table views from connected entities, which is why it gets large enough to need splitting.

it does work and the created PDF looks beautiful and custom, but well, split across 16 text fields

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 4, 2026, 8:45am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/6 "2026-06-04T08:45:42Z")

</div>

> [@philipp](#):
>
> 1. the script threw “Cannot parse “” entity “” field” with updateEntity on rich text fields (but not on text fields)

You need to read how to update rich text fields - they don’t use updateEntity, they make use of setDocumentContent instead.  
There are a few examples here in the community.

> [@philipp](#):
>
> 1. I’m injecting each field’s raw string straight into the HTML template, so plain text is what I want

Rich text fields will happily take plain text. Although they allow formatting, it’s not mandatory 😊

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [July 12, 2026, 9:51am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/7 "2026-07-12T09:51:06Z")

</div>

A post was split to a new topic: [Showing rich text in mentions](https://community.fibery.io/t/showing-rich-text-in-mentions/11062)

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [September 8, 2026, 4:45pm UTC](https://community.fibery.io/t/max-length-of-text-field/1858/8 "2026-09-08T16:45:22Z")

</div>

Ran into this again… Now I need to make a more proper solution somehow… Still working it out, will share when done.

For now, wondering if it’s possible to throw an error when a formula field is MEANT to resolve to more than 1000 characters, but the field limits it. Because now its failing silently and things are breaking.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 8, 2026, 5:00pm UTC](https://community.fibery.io/t/max-length-of-text-field/1858/9 "2026-09-08T17:00:11Z")

</div>

I think the only solution is to wrap the formula in a length check, and return some text to indicate if over 1000 chars

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [September 8, 2026, 5:14pm UTC](https://community.fibery.io/t/max-length-of-text-field/1858/10 "2026-09-08T17:14:21Z")

</div>

In my case the formula is not to be viewed by the user. It is a solution to the lack of “Contains” function in formulas.

I’ll share the full case.

Databases:  
Document has many categories  
Document has one supplier

Category has many documents  
Category has many relevant suppliers

Supplier has many documents  
Supplier has many relevant categories

The formula should be on the Document DB, and answer the question: **Are there any categories on this document which are not part of this document’s supplier’s relevant categories?**

The solution I found needs to check if a collection “Contains” an entity from another place. But to do this, I need to convert the collection to a string of public ids, then use “Find” to check if contains.

When it gets to over 1000 characters, this check breaks silently. If it were to just print to the formula something different, it would also still break silently… Since no one is actively looking at this formula, its used for a different formula.

Still looking for a solution for this. But hopefully understanding the use case can help understand the solution.

For reference, this is the old solution:

```auto
If(
  Categories.Filter(
    Find(
      [Suppliers IDs],
      "|" + [This Source Document].Supplier.[Public Id] + "|"
    ) = 0
  ).Count() > 0,
  "| Contains category not present in supplier's relevant categories |",
  ""
)

```

Update:

Fixed by going the the other way. There are less categories linked to a supplier than suppliers linked to categories. So going the other way solves it.

There will be cases where this is impossible though, if both sides of the relation have many linked entities.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 8, 2026, 9:28pm UTC](https://community.fibery.io/t/max-length-of-text-field/1858/11 "2026-09-08T21:28:36Z")

</div>

If I understand your use case, this sounds like a problem which shouldn’t be solved by making simple text fields accommodate more than 1000 characters, but by providing functions for set comparisons.  
You need to know if the set of Categories for a Document is a subset of the set of Categories for the owning Supplier, right?

I’m not saying we’ll implement that feature any time soon, but I think it is worth thinking about what is the root cause problem to be solved.

---

<div class="post-metadata">

**Author:** ![Joshua\_Erdman](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/joshua_erdman/32/14808_2.png) [@Joshua\_Erdman](https://community.fibery.io/u/Joshua_Erdman)\
**Post date:** [October 2, 2026, 7:02am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/12 "2026-10-02T07:02:13Z")

</div>

as I am working with text fields in fibery, it appears that the standard text fields hold more than 1000 characters now. Is that corect?

---

<div class="post-metadata">

**Author:** ![Joshua\_Erdman](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/joshua_erdman/32/14808_2.png) [@Joshua\_Erdman](https://community.fibery.io/u/Joshua_Erdman)\
**Post date:** [October 2, 2026, 8:20am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/13 "2026-10-02T08:20:19Z")

</div>

I just spoke with support - it is 5,000 characters now and has been like that for over a year.

They are updating the documentation.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [October 2, 2026, 8:44am UTC](https://community.fibery.io/t/max-length-of-text-field/1858/14 "2026-10-02T08:44:38Z")

</div>

Welcome to the community Joshua :))

That’s funny because the user guide said 5,000 back March, but then was changed to back to 1,000 when i reported on this issue…

I dug deeper into it and found out why. When using an editable text field, the limit is 5,000 characters, but when using a formula which outputs a text data type, it only returns the first 1,000 characters. Not sure if this is intentional or slipped through the cracks when changing the character limit over a year ago.

Tagging @Polina_Zenevich since we spoke about this back in March on intercom.

Sidenote, the error when there are more than 5,000 characters in a text field is not so helpful: `Cannot parse "Space/Database" entity "Space/Field" field.` So maybe the error message here could be more descriptive.