# Session expires on page reload

**URL:** <https://discuss.streamlit.io/t/session-expires-on-page-reload/4651>\
**Category:** Using Streamlit\
**Tags:** session-state\
**Created:** [July 31, 2020, 11:02am UTC](https://discuss.streamlit.io/t/session-expires-on-page-reload/4651 "2020-07-31T11:02:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![GokulNC](https://sea2.discourse-cdn.com/streamlit/user_avatar/discuss.streamlit.io/gokulnc/32/2806_2.png) [@GokulNC](https://discuss.streamlit.io/u/GokulNC)\
**Post date:** [August 20, 2020, 1:55pm UTC](https://discuss.streamlit.io/t/session-expires-on-page-reload/4651/2 "2020-08-20T13:55:22Z")

</div>

Related:

> [@Persisting device fingerprint specific states specific to a client](https://discuss.streamlit.io/t/persisting-device-fingerprint-specific-states-specific-to-a-client/4981):
>
> Though there are ways to store a single session’s states (like [this](https://discuss.streamlit.io/t/multi-page-app-with-session-state/3074/)), there currently seems to be no way to persist them across refreshes for a single user/client. (Something roughly like a browser cookie or local storage) Not to be confused with a global persistent states (like [this](https://discuss.streamlit.io/t/simple-example-of-persistence-and-waiting-for-input/2111) or [this](https://discuss.streamlit.io/t/multi-page-app-with-session-state/3074/35)). It would be great if we could use the device fingerprint of the client to store a state object specific to that client. Would that be possible?

---

_[View the full topic](https://discuss.streamlit.io/t/session-expires-on-page-reload/4651)._