# Roku Non-Volatile Memory Storage Issue

**URL:** <https://forum.developer.roku.com/t/roku-non-volatile-memory-storage-issue/8394>\
**Category:** Archived\
**Tags:** roku-developer-program\
**Created:** [July 26, 2018, 6:18pm UTC](https://forum.developer.roku.com/t/roku-non-volatile-memory-storage-issue/8394 "2018-07-26T18:18:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vishalpatil](https://avatars.discourse-cdn.com/v4/letter/v/ecccb3/32.png) [@vishalpatil](https://forum.developer.roku.com/u/vishalpatil)\
**Post date:** [July 26, 2018, 6:18pm UTC](https://forum.developer.roku.com/t/roku-non-volatile-memory-storage-issue/8394/1 "2018-07-26T18:18:14Z")

</div>

We are developing a Roku screensaver application. So, basically, we are fetching the images from the AWS S3 bucket. We need a way to cache the images in some kind of non-volatile memory in Roku after initially loading the images from the AWS S3 bucket. Is there a way to store the images at runtime (fetched from some external sources i.e. AWS s3 bucket) in a non-volatile memory in Roku? If yes, can you please brief about the same.

---

<div class="post-metadata">

**Author:** ![renojim](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@renojim](https://forum.developer.roku.com/u/renojim)\
**Post date:** [July 26, 2018, 7:00pm UTC](https://forum.developer.roku.com/t/roku-non-volatile-memory-storage-issue/8394/2 "2018-07-26T19:00:54Z")

</div>

cachefs might be what you’re looking for: [https://sdkdocs.roku.com/display/sdkdoc/File+System](https://sdkdocs.roku.com/display/sdkdoc/File+System)

It’s relatively new and I have no experience with it.

-JT

---

<div class="post-metadata">

**Author:** ![squirreltown](https://avatars.discourse-cdn.com/v4/letter/s/f07891/32.png) [@squirreltown](https://forum.developer.roku.com/u/squirreltown)\
**Post date:** [July 26, 2018, 11:15pm UTC](https://forum.developer.roku.com/t/roku-non-volatile-memory-storage-issue/8394/3 "2018-07-26T23:15:49Z")

</div>

@renojim is right, cachefs is what you want. The best you will be able to do though is reduce the downloading. Cachefs is non-volatile but limited and shared so you need to check if the graphic is there each time you need it.