# Saved searches use case? **URL:** \ **Category:** Kibana\ **Created:** [November 12, 2018, 8:23am UTC](https://discuss.elastic.co/t/saved-searches-use-case/156250 "2018-11-12T08:23:08Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Sjaak01](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@Sjaak01](https://discuss.elastic.co/u/Sjaak01)\ **Post date:** [November 12, 2018, 8:23am UTC](https://discuss.elastic.co/t/saved-searches-use-case/156250/1 "2018-11-12T08:23:08Z")
Hi, I was wondering what is the purpose of saved searches? Obviously being able to generate .csv's from the discovery page is nice, but what if for example I use a saved search for a table visualization? For example; I have a table that queries @timestamp as a term and about 20 other items. This can get pretty slow. If I were to create a saved search with the same items, and then create the table based on that, would that be (much) faster? What use case do saved searches have? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [November 12, 2018, 8:52am UTC](https://discuss.elastic.co/t/saved-searches-use-case/156250/2 "2018-11-12T08:52:23Z")
Saved searches allow you to group an index pattern and a set of filters that are always applied. This allows you to create visualizations that only show a subset of data. The same set of filters is going to be applied though, so I am not sure I would expect any performance gain. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 10, 2018, 8:52am UTC](https://discuss.elastic.co/t/saved-searches-use-case/156250/3 "2018-12-10T08:52:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.