How to Keep Record Order Consistent Across All Airtable Views
You carefully arrange your records in one view. The order looks exactly right. Then you open another view of the same table and the records appear in a completely different order.
No sort is applied in either view, so the order should be the same.
This is one of the more confusing parts of Airtable’s view system, and understanding why it happens is the first step to fixing it.
Why Airtable Shows Different Record Orders Across Views
Airtable does not have a single global record order for a table. Each view stores its own independent sort state.
When you create a new view, Airtable usually shows records in creation order. But if you sort a view and later remove that sort, Airtable does not reset the records back to their original order. The records stay in the last sorted position even after the sort condition is removed.
This is why two views can show completely different record orders even when neither has an active sort. One view may have been sorted by Name at some point in the past, while another still reflects creation order.
Manual drag-and-drop ordering also works per view, not globally across the table.
Filtering can make the difference even more noticeable because it only shows a subset of records from that underlying order.
Solution 1: Use an Autonumber Field
The most reliable way to keep the same order across views is to add an Autonumber field and sort every view by it.
An autonumber field assigns a sequential value to each record when it is created. The first record gets 1, the second gets 2, and so on. Because the value is stored directly on the record, every view can sort records identically.
- Add a new field and choose Autonumber
- In each view, apply a sort on the autonumber field
- Save the sort
All views now display records in the same sequence.
If you want the newest records first, sort descending instead of ascending.
Solution 2: Use Created Time for Chronological Order
If you care about the exact creation timestamp rather than just sequence, use a Created time field.
Created time automatically stores when each record was created. Sorting by this field keeps views aligned chronologically.
Autonumber vs Created Time
| Field | Best For |
|---|---|
| Autonumber | Stable record sequence |
| Created time | Exact creation timestamp |
Autonumber is usually more reliable for strict ordering during large imports because every record gets a unique sequence number. With Created time, imported records can share nearly identical timestamps.
Solution 3: Create a Manual Order Field
If you want a custom order unrelated to creation time, use a number field such as Order or Position.
Assign values like 10, 20, and 30 so you can insert records later without renumbering everything.
For example, if you need a record between 20 and 30, you can give it 25.
Apply a sort on this field in every view where you want the same order.
This method requires manual maintenance, but it gives you full control over the sequence.
If you want to reorder records by dragging them directly in a grid view, see how to reorder records in Airtable grid view, which covers both drag-to-reorder and number-based ordering in detail.
How to Keep New Views in the Same Order
Sorting is configured per view, so you must apply the sort individually in every view.
A good workaround is to create a template view with the correct sort already applied. Whenever you need a new view, duplicate the template instead of creating a blank one.
The duplicated view inherits the same sort configuration automatically.
In Airtable, record order is not a table-level setting. The only reliable way to keep views aligned is to sort them using the same field.