Increase character limit for text boxes

Thank you @Ralf Ehlert and everyone on the thread.

Thank you for sharing your thoughts and feedback. We appreciate your patience as we evaluate and process each Wish List Idea submission. We will be sure to share your feedback with our team and update this thread if this feature becomes available.In the meantime, for those coming across this idea, if you feel this would be helpful for you or your business, please be sure to vote for it and leave a comment about your use case to help our team scope this request!

Hi @ElvaMiro Are there any other workarounds you can suggest, other than breaking it up into multiple text components?

Do you know where the 6.000 character limit comes from, maybe a temp fix could be just to increase it some. Maybe just 12.000 characters. That would probably sove a big chunk of the issues.

This is a super important feature for me. Actively seeking alternative methods for my workflows in miro until the limit is increased to way way higher.

Please add a limit much closer to 20-30k characters! 

This is a huge issue that seems intuitive for the collaboration between developers and UI/UX teams. Can we get support on this?

Ran into this issue today. The limit is surprisingly low. I would hope they’ll increase this massively. 6,000 characters is very small.

Same issue… blocking the brainstorming sessions when doing a list of projects for instance. 6000 gets reached very fast..!
I think I spotted a bug there also: copy / pasting in excel, the number of characters of this list seems not to be 6000, but 700+. Maybe only because of formatting / indentation. Hence in the end it’s quite small..!

Hi!  I’m an Internet Systems Engineer and I have started seeing a lot of movement recently toward Miro for network diagramming.  Initally it was great.  Pop out a picture to describe an abstract Internetworking concept visually?  Awesome!

But, in case you haven’t heard, networks don’t always function the way people expect and intend for them to.   Because networks are controlled by and full of packets, sometimes (often) it helps to be able to get all the way down to that level to understand/explain what needs to change to make things work as intended.  So, at the intersection of “here’s a picture of a large and complex system that you can understand at a glance” and “here’s 1500-9000 bytes of data from a single packet that traverses that system and does [something]” it helps to put text boxes with the dumped contents (explanations) of those packets into the illustration.   Here’s four bytes of packet data explained, but it takes 190 bytes:
    Flags: 0x4000, Don't fragment

        0... .... .... .... = Reserved bit: Not set

        .1.. .... .... .... = Don't fragment: Set

        ..0. .... .... .... = More fragments: Not set

So this is the long way to say that in a market niche screaming for a universal platform to diagram networks this limitation of a text area is a dealbreaker.

This seems like an arbitrary limit that has no basis on technology limits.  Why was this limit implemented at all?

It also really hinders my workflow. Please, remove the limit.

Example of use case: I have a board where I’m optimizing prompts and responses from LLM AIs. I want to see it next to each other, together with annotation. Now I need to split it into many textboxes or do screenshots.

Someone actually gave the ok to assign story points to a feature no user is wanting? Where does the arbitrary 6000 char limit come from anyway?

Only reason I’m using MIRO is to get everything I use in one place. This problem causes me to have to keep things in more than one place. Fundamentally breaks the single value that drew me to the platform.