We’re bringing tabbed views to Coda!
Tabbed views let you organize multiple views of the same data source—tables, calendars, boards—as tabs within a single component. Great for keeping related views together without cluttering your doc.
See it in action:
Join the waiting list to try it out early! We’ll be rolling out early access starting in December and would love your feedback.
What’s the first use case that comes to mind for tabbed views 
? Drop a comment!
WOW!!! Finally… One of the biggest resources needed to organize our docs…
This is awesome! I’ve been hoping for this functionality for a long time.
One enhancement that I think would complement this well is allowing table views to expand to the exact width of the page/container like other view types. Within a tabbed view, this would allow the top-right controls to remain in the same position when navigating to and from tables. UX-wise this would probably be preferred. It would also look much better to me aesthetically.
Thank you for your hard work!
Does this mean any action I set using will show up in one place?
THAT would be incredible!
Great! This can drasticly lessen all the fields that filter tables! Just tabs with the filters I want for a specific thing would be amazing.
OMG FInally! Thank you….. I almost switch back to notion as my main collab tool because of this! having to be looking at a separate table each time i wanted a different view of the same data was is so infuriating. This is a great step forward.
This is amazing!! Been waiting for this one for a long time.
One question – how does the UI distinguish the tabs from the filter bar? I could see that getting confusing. And, do canvas filters apply to all the tabs, or do you set them independently for each tab view?
Huge thanks to the team 
Thanks!
Astha
Joined the waiting list. This one could unlock many cases, if implemented right.
Displaying different views for same data or referenced column data would make this super powerful. From one page we could add data not only to the viewed table but also to other related tables.
This could act like a menu if used in Display view (besides pages).
And many more
hi @Mikhail_Ramsay , can you elaborate on the notion experience in this context?
cheers, christiaan
That can really enable a lot of new experiences.
I can see, as a next step, the ability to select or show the view using a formula.
Cheers,
Felipe Arnhold
Well I’ve signed up for the beta because I’m curious, but I’m not going to follow the hype on that one… Since switching from Notion, I’ve missed that feature exactly 0 times. From what I see here, I fear two things:
Alas, the way I structure my Docs, such a feature would only be useful if:
Then I could find some useful scenarios, such as putting “contextualized helper tables” in tabs for a given view (instead of putting them as collapsed views above or below). For instance, if I’m looking at a view from my “DB Tasks” base table, then maybe I’d like to have a tab explaining the various options for the “Status” field of said tasks, with some reporting.
But I’m afraid that’s not what lies ahead.
I’ve said it before on other occasions (not later than today), but if you’re taking inspiration from Notion, PLEASE take the good stuff, such as proper localization for instance 
Nice question. I signed up to check also this because, to be honest, I expect some half-baked feature again.
It would be best if it works on levels - first is the tabs and then filters/search per tab. At least this seems logical to me - every data view has its own needs of filters
Filters, sorting, grouping, searching feel like user-specific features that every viewer should have the option to use for their personal needs. (Coda still catches up on 1985 Excel sorting, though)
Many in community would love that.
With certainly few years ago neither Coda, nor Grammarly, nor Superhuman had the knowledge to do it properly. Hopefully that changed but it does feel so, yet.
Saying this as the person whose company localized the Grammarly’s content (text, videos, etc) as subcontractor and we did all - from the dubbing to the strategy (or what could’ve been salvaged after the lack of localization strategy at the start). And used superhuman for good number of years. Coda is clear.
That’s a great suggestion! We’re focused on the core experience for the initial release, but this is really helpful feedback as we think about what comes next.
Love to hear that! We’re working to make the tabs and filter bar feel distinct, but consistent and complementary. Filters will be per tab so that you can easily navigate through tabs with different cuts of the same data.
Excited for your feedback on the UI once the beta kicks off!
I’m not sure I’m following—could you explain a bit more? I want to make sure I understand your question!
Appreciate the thorough feedback! You’re right that tabs will be different views/filters of the same base table, not different tables. But you should be able to keep your base table on a “back office” page and use tabbed views on your “client facing” pages.
We’re designing this feature as a way to organize multiple views of one data source, rather than combining different tables. Your helper tables in tabs example is useful context. We’re not tackling it with this feature, but it’s helpful to consider as we think about different ways people want to organize information. And heard on localization
Thanks for the honest and thorough answer! I really appreciate the opportunity to have a genuine discussion, even though I probably won’t be using that feature given its limitations.
And that brings us back to a broader topic: I get it that Coda wants to attract Notion users by making them feel more “at home” from a UI perspective. But I honestly believe that strategy could backfire if you don’t sort out more pressing issues first. Localization is indeed one of those issues. I’m really curious about what you mean by “And heard on localization ” because for the past few years a lot of people in this (amazing) community have been asking for better localization (myself included). And the only thing we got was a half-baked release for currency formatting without any follow-up to obvious shortcomings. And something seemingly as trivial as customizing the “Submit” button of a form is still nowhere to be found in 2025. And even Enterprise clients can’t get any support from Support outside of California office hours. Or servers in the EU (that one is soooo overdue). I know I sound harsh but I speak up because I love your product. I think it’s far superior to Notion, no questions asked. But if took me some time to realize that. It takes time to tame Coda and realize how awesome it is. By not fixing the “pressing issues”, you won’t allow many more people to come to the same conclusion. May be they’ll give Coda a go because they saw that shiny new feature that they know and love in Notion. But if they stumble upon one or more of the “pressing issues”, do you think they’ll speak up like I do? Nope: they won’t say a word, they’ll just go back to Notion, and they’ll never try out Coda ever again. That’s a lose / lose situation. And what’s even more a pity is that the (amazing) Coda Community has been VERY vocal about those “pressing issues” for YEARS. Localization. Cross-doc shortcomings. Lack of confirmation modal for deletion. Mobile app. Native Coda AI. You name it. Every single power user out there knows about them. So I urge you: if you hear why I - what we say, please make it happen
Here here! Well said.
This is amazing and can’t wait to use it!