# Increase search results page size

**URL:** https://discuss.elastic.co/t/increase-search-results-page-size/163819
**Category:** Kibana
**Created:** [January 11, 2019, 12:22am UTC](https://discuss.elastic.co/t/increase-search-results-page-size/163819 "2019-01-11T00:22:11Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![FiveHundred](https://avatars.discourse-cdn.com/v4/letter/f/47e85d/32.png) [@FiveHundred](https://discuss.elastic.co/u/FiveHundred)
#### Post date: [January 11, 2019, 12:22am UTC](https://discuss.elastic.co/t/increase-search-results-page-size/163819/1 "2019-01-11T00:22:12Z")

</div>

When you use a search in a dashboard, you can only view 50 results at a time and then you have to go to the next page:

![image](https://us1.discourse-cdn.com/elastic/original/3X/4/4/446de4e9e106307385610500dc11b734886cd9f0.png)

For our use case, it's far more user-friendly to pull all the results (or at least 1000 or so at a time).

We are using Elastic/Kibana to replace our old system of trawling through 3000 line text files to view the logs generated by a process run. This process starts, generates up to ~3000 lines, and then stops, so for us it's useful to have a nice big scroll bar that can slide through this process chronologically. If I want to glance at what happened 150 lines ago, I'd rather not have to click the back arrow and wait for a page to load three times. It's also worth noting I don't ever expect to have much more than ~3000 lines per process run.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 8, 2019, 12:22am UTC](https://discuss.elastic.co/t/increase-search-results-page-size/163819/2 "2019-02-08T00:22:16Z")

</div>

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