Skip to content


In this article, we explain how to:

  • Style the Paginator element
  • Filter a collection in the frontend using the Paginator element
  • Filter a collection in the backend using the Paginator element

Styling the Paginator

You can style any element inside the Paginator, change the style of the arrows or change the color of the active page number for example.

To change the color of the active page number:

  • select the "Text" element inside the Paginator,
  • create an active state in the style section of this element,
  • select the active state and style it like you would any other state.

In the example below, we styled the Paginator's "Text" element so that the active page number appears blue and bold:

Frontend pagination

Before we go any further, note that when you add pagination in the frontend, all your collection items loaded in the user's browser, even if only 10 items are displayed on the page.

If you do not want this to happen, consider adding pagination in your backend before fetching the collection in WeWeb.

Learn more about server-side (backend) vs client-side (frontend) pagination here.

If you do want to add pagination in the frontend, here's how you do it in WeWeb:

  • drag-and-drop the Paginator element on the page that displays the collection you want to paginate
  • ensure the collection on the page is bound to the Collection object and not a Collection['data'] array
  • tell the Paginator which collection you want to paginate using the Collection dropdown:

Paginator settings in WeWeb


This is not intuitive but, for the Paginator element to work, the Collection it relates to must be bound to the Collection object, not Collection['data']. This is because Collection['data'] only includes the list of items in our Collection and we need the information about the current page which is in the Collection object.

To learn more about frontend pagination in the context of a real project, consider watching this video from level 1 of the WeWeb Academy:

The limits of frontend pagination

With frontend pagination, data that is not displayed on the page is still accessible in the browser:

This has two consequences:

  1. the data being loaded may still be heavy enough to slow the browser down or strain your visitors' data plans

  2. even though it is not displayed on the page, the data is accessible to anyone who knows where to look for it, i.e. in the inspector / network.

If you want to avoid this, consider adding pagination in the backend instead.

Backend pagination

When working with large amounts of data, it is best practice to paginate your Collection of data in the backend.

If you paginate a Collection in the frontend, the entire set of data will be loaded in your users' browsers, even if you only display 10 items on the page.

This is a big no-no if you're working with a heavy set of data as your users' browsers will crash.

People often talk about millions of records but another way to look at it is in terms of volume. The less you tap into your users mobile data plans, the better.

This next steps explain how to setup custom pagination on the Paginator Element.


How you add pagination to a table in your backend is specific to your backend. Here, we will illustrate how to add Custom pagination on the WeWeb Paginator element using a Xano endpoint. If you are having trouble to follow along with a different backend, please check the user docs of your backend provider.

Step 1: add paging to the backend

In Xano, you'll need to enable Paging in the Output of your query:

If you run and debug your API call, you should now see additional information in Xano like the number of itemsReceived and total number of pages, i.e. pageTotal:

Paginated output in Xano

In WeWeb, the collection should look something like this with context about the collection in addition to the items:

Paginated output in Xano

Note that, in the screenshot above, we can see Xano sends back 5 items. This is because we asked for 5 items per page when we enabled Paging in Xano.

Step 2: have the backend listen for info about the current page and offset

With the WeWeb Paginator element, we can send info about the current page and offset to tell Xano what items the user needs to see next. In order to to feed that information to Xano, we will create two integer inputs in Xano – page and offset – which we'll map in the External tab:

Paginated external setting in Xano


In the context of pagination in web development, offset refers to the number of items that should be skipped from the beginning of a dataset when displaying a particular page of results.

For example, let's say we have a list of 50 items, and we want to display 10 items per page. To display the second page of results, we would need to skip the first 10 items (i.e., the offset would be 10), and then display the next 10 items.

Step 3: test the API call

Through a "Run & Debug" in Xano and/or in a Collection in WeWeb, test your API call to make sure it sends back the data you expect depending on the page or offset you send.

Here we chose to tell Xano which page we want:

API call to Xano


Test your API call with different pages and offsets, including the first and last page to ensure that your backend is sending the right items based on the information the frontend is requesting.

Don’t worry about making the call dynamic yet, just try with a few values to make sure the response is what you expect.

Step 4: create a paginator variable

Create a paginator variable of type Object with the default values your backend needs to send the first items you want to display from your table.

Usually, the default page value should be 1 – paginator is on the first page – and the default offset value should be 0 – no items should be skipped:

Pagination variable

Step 5: Paginator workflow

On the page with the collection you want to paginate, add the WeWeb paginator element with a workflow that:

  • triggers On change
  • updates the paginator object variable with the information from the event
  • refetches the Collection you are working with

Paginator workflow

That way your paginator variable will have the up to date offset and current page so however you chose to make the call to Xano, you’ll have the correct info based on user interactions with the paginator.

Step 6: Paginator settings

On the paginator element, enable "Custom pagination", and bind:

  • the total items returned by your backend (e.g. Xano sends back itemsTotal),
  • the fixed number of items per page (note: this is NOT the number of items received because if you’re on the last page of the collection, the backend might return only 17 items leftover instead of the full 25 per page for example)
  • the offset – the offset should be current page (from the paginator event) - 1 * number of items per page

Paginator custom settings

Step 7: bind the collection

In WeWeb, instead of binding your collection to the collection with its metadata, you'll need to bind directly to an array or list of items.

If we take Xano as an example, that means instead of binding to Collection['data'] or Collection, you'll need to bind Collection['data']['items']:

Paginated external setting in Xano

This is because the container to which you bind the collection expects an Array, i.e. a list of items.

The binding of the Collection List items is the same as with any other Collection List. If you're unsure how to display the job title or company logo on the page, please refer to the user documentation on binding.

Step 8: make your API call dynamic

Back in your collection, you can now bind the input you are sending to your backend to the data in your paginator variable (for example, the page or offset).

The input you send to your backend will depend on the info your backend needs to return the items you want.

And voilà! You should be good to go.

Enable the Preview mode to check that everything is working correctly.

Setting up backend pagination can be challenging. Please don't hesitate to reach out to the WeWeb Community if you get stuck.