# Glide App limits for user data

**URL:** <https://community.glideapps.com/t/glide-app-limits-for-user-data/36891>\
**Category:** Ask for Help\
**Created:** [January 9, 2022, 2:33pm UTC](https://community.glideapps.com/t/glide-app-limits-for-user-data/36891 "2022-01-09T14:33:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![B\_A](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/b_a/32/6601_2.png) [@B\_A](https://community.glideapps.com/u/B_A)\
**Post date:** [January 9, 2022, 2:33pm UTC](https://community.glideapps.com/t/glide-app-limits-for-user-data/36891/1 "2022-01-09T14:33:51Z")

</div>

It is my understanding that Glide Pro app has limit of 25000 rows. Which means if I am going to have signed in users than I can have 25000:users. Question- for each user, how many columns can I use for storing data into columns (push) and also pulling data from columns and displaying in user app page?

Thanks  
Bimal

---

<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:** [January 9, 2022, 3:27pm UTC](https://community.glideapps.com/t/glide-app-limits-for-user-data/36891/2 "2022-01-09T15:27:26Z")

</div>

The 25k is a suggestion not a hard limit. You can go past the 25k. It will depend on the structure and complexity of your app.

Generally speaking apps will slow down as they approach 25k (even well before if it’s very complex)

I’d suggest having a look at row owners.

> **[Row Owners](https://docs.glideapps.com/all/topics/security-and-user-data/row-owners)**
>
> A secure way to restrict access to certain rows

Here’s an example…  
100k Users each with 1 row of data.

Using a filter - All 100k rows would first need to be downloaded to the user devices and only then it would filter down to one row. (This would make the app very slow or not usable at all)

Using Row Owners - Each of the 100k users would only download 1 row of data to his or her device (Making the app very fast and usable) 👍

Taking the example above this means we could have 25k users and our Glideapp would only consume 1 row of data. That is if we apply row owners correctly.

---

<div class="post-metadata">

**Author:** ![B\_A](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/b_a/32/6601_2.png) [@B\_A](https://community.glideapps.com/u/B_A)\
**Post date:** [January 10, 2022, 11:35am UTC](https://community.glideapps.com/t/glide-app-limits-for-user-data/36891/3 "2022-01-10T11:35:42Z")

</div>

Thank you Eric. Appreciate your reply very much. This clears half of my issue. I am going to use row,owners as explained in document. Now I have information on my website blog that gets updated / new blog added every few days. I am trying to link specific blog post to my glideapp so that users can see it in their app. It’s going to be public so all users can see it in their app. Any thoughts and suggestions?

Thank you very much,  
Bimal

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [January 10, 2022, 12:03pm UTC](https://community.glideapps.com/t/glide-app-limits-for-user-data/36891/4 "2022-01-10T12:03:55Z")

</div>

> [@B\_A](#):
>
> It’s going to be public so all users can see it in their app.

Then you should not apply row owners for that specific table where you store these blogs.

Do you just want to put a link in the app and the users will click that to go to your blog?

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [January 11, 2022, 12:04pm UTC](https://community.glideapps.com/t/glide-app-limits-for-user-data/36891/5 "2022-01-11T12:04:47Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
