Is there a limit on fields per table?
Yes. Your plan sets how many fields a table can have, and the database limits how much one record holds, so many large fields reach the limit sooner.
- Verified Nov 22, 2026
- Classic builder
- Tadabase AI
On this page
Yes. Your plan sets how many fields one table can have, and the database also limits how much a single record can hold, so a table with many large fields can reach the limit before the plan number. At either limit the builder refuses the new field; the fields you already have keep working.
The two limits #
- Fields per table is part of your plan. The published numbers are on Plans & limits; an older or custom plan has its own.
- Record size comes from the database. Each field takes space in every record, and some types take more than others. When a new field no longer fits, adding it shows You've exceeded the number of fields that can be added to this data table, even if your plan allows more fields.
When you reach it #
- Delete fields nobody uses. Field Usage lists the fields that are Unused.
- Split the table: move a group of related fields, such as billing details or survey answers, into their own table and link it with a connection field. This is usually faster and easier to keep tidy than one very wide table.
Was this page helpful?
Something wrong or missing on this page? Tell us.