# When to go in for Big Tables?

**URL:** <https://community.glideapps.com/t/when-to-go-in-for-big-tables/71730>\
**Category:** Ask for Help\
**Tags:** big-tables\
**Created:** [March 16, 2024, 1:44pm UTC](https://community.glideapps.com/t/when-to-go-in-for-big-tables/71730 "2024-03-16T13:44:15Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)\
**Post date:** [June 2, 2025, 12:23pm UTC](https://community.glideapps.com/t/when-to-go-in-for-big-tables/71730/12 "2025-06-02T12:23:44Z")

</div>

Using regular Glide tables works fine for most cases. However, if your app makes frequent API calls, the Big Tables API can significantly reduce costs… 100x cheaper. Additionally, the new API includes several new functionalities that may be beneficial depending on your use case.

> [@Public Beta: Glide API v2.0 for Big Tables](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382):
>
> Glide API v2.0 lets you work with Glide Big Tables programmatically. The new and improved API consumes significantly fewer updates than v1. We’ve also introduced [stashes](https://apidocs.glideapps.com/api-reference/v2/stashing/put-stashes-serial) to let you easily import thousands of rows at a time. [Try it for yourself in our interactive API docs.](https://apidocs.glideapps.com/api-reference/v2/general/introduction) Note: API support for regular Glide Tables is coming soon. Pricing Add, Edit, or Delete rows = 0.01 updates per row changed (100x cheaper) Get rows = 0.001 updates per row (no more rounding to 1 update per 1k rows) Walkt…

---

_[View the full topic](https://community.glideapps.com/t/when-to-go-in-for-big-tables/71730)._