📣 Announcing the Storage component


Implement it the same way storing in hidden divs worked: using a callback retrieve localStorage contents as State, manipulate the data, and save. The default “click count” demo in the documentation illustrates how to read and update values stored in local/session/memory. Should be easy to extend to a updating a list of values or dict of list of values.

You can also use State('store-element', 'modified_timestamp') as a lookup for querying new data. Believe the modified timestamp is given as epoch time in milliseconds.


This is a HUGE improvement over the hidden div method. Much appreciated. However, I wanted to verify one point: the Store method will incur the same network transport costs as a hidden div, right? In other words, I will still likely want to cache (memoize) very large files?


A post was split to a new topic: Infinite loop with dcc.Store?