Max characters in text

Hi, I am interested by the answer of this topic also. What is the max length of a text field in table ?
Continuing the discussion from Max Characters in Text Field:

Hi @Fiora thanks for bumping this. There isn’t a max character count, but there is a max storage size.

Text Sequence of characters: Max size: 2.5kB in Tulip Tables; 50kB in other case. Truncated to 600 characters for analytics.

You can find the rest in the KB here.

Hi @Fiora,

in UTF-8 each character has 1 - 4 Byte.

That means, in a table field there is space for 640 to 2560 characters. (2,5kB * 1024B/kB = 2560B)

The fierst 128 characters use 1 Byte each. That means standard Latin character text with the most common symbols ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ { | } ~ and 0-9 can reach up to 2560 characters in a table or up to 51200 characters in other cases…

@John did I do the math wrong? I managed to save exactly 50000 characters in a Table field, which is eqivalant to ~48.8 Kilobytes
I would count that as 50kB but way more than 2.5kB

Hey all,

While there is some technical size limit, I want to flag that there might be another question worth answering here.
Could you share what you might be storing into a field that could potentially reach somewhere near either of these limits? If this much data is needed in one table field, it may be worth taking a look into how data is being stored more generally in these tables, and if there is a more appropriate table architecture that could be utilized to maximize efficiency / reduce size concerns.


In my case I don’t have any use cases yet, but I think its good to know the limits.

One use case, could be to save a JSON file, to put an object array in a table.
As long as you need do loop through a table to save and get an object array this might be a workaround.
For instance, I have a measurement result with x an y values for a line chart.
I have it like this:


I do have those values beside a whole bunch of other values in a table, but I neet to loop through it to get an object array for usig it in app.
So saving this as an extra value in a measurements table could be a use case for long strings.

As mentioned, this is just a workaround!