# Datagrid limited to 1000 records

**URL:** <https://community.weweb.io/t/datagrid-limited-to-1000-records/20037>\
**Category:** Ask us anything\
**Created:** [September 24, 2025, 1:13am UTC](https://community.weweb.io/t/datagrid-limited-to-1000-records/20037 "2025-09-24T01:13:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![arnaldo.zyl](https://avatars.discourse-cdn.com/v4/letter/a/a5b964/32.png) [@arnaldo.zyl](https://community.weweb.io/u/arnaldo.zyl)\
**Post date:** [September 24, 2025, 1:13am UTC](https://community.weweb.io/t/datagrid-limited-to-1000-records/20037/1 "2025-09-24T01:13:09Z")

</div>

### 

I’m facing a limitation with the Datagrid component connected to Supabase. My table has 11,000 records, but the Datagrid can only display the first 1,000 records.

**Problem:**

- The table in Supabase has 11,000 records

- The Datagrid displays only the first 1,000 records

- Even when applying filters to search for records at the end of the table, I still only get the first 1,000 records

- This prevents me from viewing and filtering the complete data

**Question:** Is there any way to:

1. Increase this limit of 1,000 records?

2. Configure server-side pagination to load all records as needed?

3. Make the filters search across the entire database (11,000 records) and not just the first 1,000?

I appreciate any guidance on how to solve this limitation.

---

<div class="post-metadata">

**Author:** ![sam1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/sam1/32/6724_2.png) [@sam1](https://community.weweb.io/u/sam1)\
**Post date:** [September 24, 2025, 1:38am UTC](https://community.weweb.io/t/datagrid-limited-to-1000-records/20037/2 "2025-09-24T01:38:12Z")

</div>

not 100% sure but I don’t think there is a limit on the datagrid but on supabase instead [JavaScript API Reference | Supabase Docs](https://supabase.com/docs/reference/javascript/select) so if you increase your limit then you can display more. But know that this will be slower to call and can be a large amount of data for your browser to hold.

---

<div class="post-metadata">

**Author:** ![andreas.schaefer](https://avatars.discourse-cdn.com/v4/letter/a/cab0a1/32.png) [@andreas.schaefer](https://community.weweb.io/u/andreas.schaefer)\
**Post date:** [September 24, 2025, 2:32am UTC](https://community.weweb.io/t/datagrid-limited-to-1000-records/20037/3 "2025-09-24T02:32:37Z")

</div>

You should probably come up with a better query or if you really need to filter thru all data with an rpc. Loading 11k records into the browser is not a good idea. Performance wise and security wise

---

<div class="post-metadata">

**Author:** ![arnaldo.zyl](https://avatars.discourse-cdn.com/v4/letter/a/a5b964/32.png) [@arnaldo.zyl](https://community.weweb.io/u/arnaldo.zyl)\
**Post date:** [September 24, 2025, 10:40am UTC](https://community.weweb.io/t/datagrid-limited-to-1000-records/20037/4 "2025-09-24T10:40:05Z")

</div>

Imagine that from those 11,000 records I need to filter 2,000 - it won’t work anymore. I also did a test with sorting the 1,000 records that it displays on screen and right at the first record it shows one out of order. Perhaps this is a bug that the technical team should look into.

---

<div class="post-metadata">

**Author:** ![andreas.schaefer](https://avatars.discourse-cdn.com/v4/letter/a/cab0a1/32.png) [@andreas.schaefer](https://community.weweb.io/u/andreas.schaefer)\
**Post date:** [September 24, 2025, 11:17am UTC](https://community.weweb.io/t/datagrid-limited-to-1000-records/20037/5 "2025-09-24T11:17:33Z")

</div>

You need to solve this on the database level. Loading that much data into the browser won’t work at all on a lot of devices.

---

<div class="post-metadata">

**Author:** ![Aasif](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/aasif/32/7517_2.png) [@Aasif](https://community.weweb.io/u/Aasif)\
**Post date:** [September 24, 2025, 1:52pm UTC](https://community.weweb.io/t/datagrid-limited-to-1000-records/20037/6 "2025-09-24T13:52:02Z")

</div>

@arnaldo.zyl  
I handled this in Supabase itself. Loading all 11k rows to the frontend is bad practice, so I set up server-side pagination with .range() and applied filters directly in the Supabase query. This way the Datagrid only loads what’s needed, stays fast, and filters always apply across the full dataset.

---

<div class="post-metadata">

**Author:** ![arnaldo.zyl](https://avatars.discourse-cdn.com/v4/letter/a/a5b964/32.png) [@arnaldo.zyl](https://community.weweb.io/u/arnaldo.zyl)\
**Post date:** [September 25, 2025, 11:51am UTC](https://community.weweb.io/t/datagrid-limited-to-1000-records/20037/7 "2025-09-25T11:51:43Z")

</div>

I managed to get the pagination range working. I need help on how to build a filter using query string with bind. It looks like it’s an array. Can you show me the layout of this array?
