# Converting Glide Tables to Big Tables

**URL:** <https://community.glideapps.com/t/converting-glide-tables-to-big-tables/85876>\
**Category:** Feature Requests\
**Created:** [January 3, 2026, 5:23pm UTC](https://community.glideapps.com/t/converting-glide-tables-to-big-tables/85876 "2026-01-03T17:23:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rien\_Dumore](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rien_dumore/32/79283_2.png) [@Rien\_Dumore](https://community.glideapps.com/u/Rien_Dumore)\
**Post date:** [January 3, 2026, 5:23pm UTC](https://community.glideapps.com/t/converting-glide-tables-to-big-tables/85876/1 "2026-01-03T17:23:28Z")

</div>

This feature should exist in 2024. Does anybody has a clue when this will come?

> [@Glide Big Tables Plan coming years](https://community.glideapps.com/t/glide-big-tables-plan-coming-years/74397/3):
>
> Converting Glide Tables to Big Tables is coming this year. We will eventually make Glide Tables and Big Tables equivalent / the same thing. More features from Glide Tables (e.g. live updating) are coming to Big Tables this year.

Every app that was/is build on regular glide tables cannot scale above 25.000 rows per app until tables with a lot of rows are moved to big tables (or external high scale databases) but now this requires replacing all the logic, interfaces and workflows. This is very prone to mistakes, takes a lot of time, and poses problems for live apps. A function converting Glide Tables to Big Tables would solve this.

I would love this functionality, especially since big tables has gained a lot of functionality since. Anyone else that would love to see this?

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [January 5, 2026, 5:02am UTC](https://community.glideapps.com/t/converting-glide-tables-to-big-tables/85876/2 "2026-01-05T05:02:09Z")

</div>

Agreed.

---

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [February 4, 2026, 3:55am UTC](https://community.glideapps.com/t/converting-glide-tables-to-big-tables/85876/3 "2026-02-04T03:55:29Z")

</div>

Or…..let Glide Tables support 100,000 or 500,000 rows. Just sayin’

---

<div class="post-metadata">

**Author:** ![Rien\_Dumore](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rien_dumore/32/79283_2.png) [@Rien\_Dumore](https://community.glideapps.com/u/Rien_Dumore)\
**Post date:** [February 4, 2026, 11:53am UTC](https://community.glideapps.com/t/converting-glide-tables-to-big-tables/85876/4 "2026-02-04T11:53:22Z")

</div>

Big tables are for high scale, because normal glide tables can’t handle those amounts of data without slowing down the app significantly.

---

<div class="post-metadata">

**Author:** ![rayo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rayo/32/91372_2.png) [@rayo](https://community.glideapps.com/u/rayo)\
**Post date:** [February 22, 2026, 7:26am UTC](https://community.glideapps.com/t/converting-glide-tables-to-big-tables/85876/5 "2026-02-22T07:26:46Z")

</div>

Have you tested having an app with 2 or more Big Tables over 5-6k rows and relations?  
Interested to know if anyone has and doesn’t see the related screens not significantly slow

---

<div class="post-metadata">

**Author:** ![Rien\_Dumore](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rien_dumore/32/79283_2.png) [@Rien\_Dumore](https://community.glideapps.com/u/Rien_Dumore)\
**Post date:** [March 1, 2026, 4:40pm UTC](https://community.glideapps.com/t/converting-glide-tables-to-big-tables/85876/6 "2026-03-01T16:40:31Z")

</div>

I have no problem with this, still pretty fast.
