# Elasticsearch Pagination: Scroll API

**URL:** <https://discuss.elastic.co/t/elasticsearch-pagination-scroll-api/379852>\
**Category:** Elasticsearch\
**Created:** [July 7, 2025, 8:16am UTC](https://discuss.elastic.co/t/elasticsearch-pagination-scroll-api/379852 "2025-07-07T08:16:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sundar.s](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@sundar.s](https://discuss.elastic.co/u/sundar.s)\
**Post date:** [July 7, 2025, 8:16am UTC](https://discuss.elastic.co/t/elasticsearch-pagination-scroll-api/379852/1 "2025-07-07T08:16:26Z")

</div>

Hi,

Noticed, that the following note has been added for Scroll Pagination.

> We no longer recommend using the scroll API for deep pagination. If you need to preserve the index state while paging through more than 10,000 hits, use the [`search_after`](https://www.elastic.co/docs/reference/elasticsearch/rest-apis/paginate-search-results#search-after) parameter with a point in time (PIT).

Could someone advise me on this to understand this better as we are intended to use scroll pagination for one of our use cases, where the results has to be fetched in a paginated fashion to be consumed by another consuming application.

1. Why this is not recommended for paging through more than 10,000 hits ? What is the impact of this ?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 7, 2025, 10:35am UTC](https://discuss.elastic.co/t/elasticsearch-pagination-scroll-api/379852/2 "2025-07-07T10:35:43Z")

</div>

> [@sundar.s](#):
>
> the results has to be fetched in a paginated fashion to be consumed by another consuming application.

That's exactly the goal of `pit` + `search_after`.  
This is much better than scroll API as there are some optimizations behind the scene.

> Why this is not recommended for paging through more than 10,000 hits?

Actually, I think I read the sentence in another way than you did and we probably meant:

> if you need to run data extraction for more than 10 000 hits, don't use `from + size` but `search_after + pit`.

Where previously it was:

> if you need to run data extraction for more than 10 000 hits, don't use `from + size` but `scroll`

My 2 cents.

---

<div class="post-metadata">

**Author:** ![sundar.s](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@sundar.s](https://discuss.elastic.co/u/sundar.s)\
**Post date:** [July 8, 2025, 6:23am UTC](https://discuss.elastic.co/t/elasticsearch-pagination-scroll-api/379852/3 "2025-07-08T06:23:29Z")

</div>

Thanks @dadoonet - From your message, I understand that `pit` + `search_after` is more optimized than `scroll`.  
But in our use case, we are leaning towards `scroll` mostly, because,

1. Identifying an unique sortable attribute may be bit difficult. But in scrol API, we do not need any such sortable fields.
2. These producing(which fetches the data from the ES in paginated batches) and consuming services here are not going to run all the time. These agents may run only when required.
3. Probably, we can keep the hits less than 10, 000 most of the time, with proper search criteria

Would you still advise that, its better to use the `pit`+`search_after` instead of `scroll`? If at all, `scroll` what kind of impacts, we can expect.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 8, 2025, 6:40am UTC](https://discuss.elastic.co/t/elasticsearch-pagination-scroll-api/379852/4 "2025-07-08T06:40:31Z")

</div>

> [@sundar.s](#):
>
> we do not need any such sortable fields

Yeah. Sort by `_doc`. That's the most efficient way.

> [@sundar.s](#):
>
> Probably, we can keep the hits less than 10, 000 most of the time, with proper search criteria

That's even better. You can fetch all the hits in one single query. Which means that you don't need to hold the pit.

---

<div class="post-metadata">

**Author:** ![sundar.s](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@sundar.s](https://discuss.elastic.co/u/sundar.s)\
**Post date:** [July 21, 2025, 6:44am UTC](https://discuss.elastic.co/t/elasticsearch-pagination-scroll-api/379852/5 "2025-07-21T06:44:31Z")

</div>

Thanks David. This helps.

Could you please advise me on the following also,

1. What is the maximum keep alive duration for  
a. Scroll API  
b. PIT for Search\_After  
Thanks,  
Sundar.