Plan availability | All plan types |
Platform(s) | Web/Browser, Mac app, and Windows app |
Related reading | |
Airtable terminology | Base - a collection of data in Airtable, designed to contain all of the information a user needs for a project or workflow. Bases can have multiple tables, each containing data; within each table, there are records, with data for each record stored in fields. |
This article details best practices for effectively structuring Airtable bases to ensure the best performance possible.
How can I improve base performance in Airtable?
Create individual views that use filters and hidden fields that only display individual collaborators and associated information.
Delete any unused records.
Remove non-essential formulas, linked records, or rollup fields .
Reduce API usage or insert pauses between calls, when possible.
Refer to to this section of the base performance article where you will learn more about how automations and syncs can affect base performance.
What base design behaviors degrade Airtable performance?
Base performance, including things like speed, collaboration, and usability, is often related to redundant tables—all living in the same base. The following behaviors should be avoided whenever possible:
Creating multiple tables in the same base with similar fields that don’t use linked records.
Creating multiple tables in the same base with similar structures and uses.
Creating tables that summarize information in other tables without using linked records in the same base.
Creating multiple tables in the same base, tracking different stages of projects.
Creating individual tables for different time-frequencies (weeks, months, quarters).
Creating individual tables for categories (products, projects, types of events).
Creating individual tables for each collaborator.
What base design behaviors improve usability?
Creating collaborator, text, or select fields to assign tasks to individual collaborators and group records to keep them separate instead of creating tables for each collaborator.
Using views to section out related data instead of having data unnecessarily spread across multiple tables.
How can I reduce the amount of information I see or share in bases?
Check out our Limiting linked record selection to a view article to learn how limit what information is viewable.
How can I customize my base’s appearance?
Check out our Creating and managing Airtable bases to learn how customize base appearance.