---
title: "Comment by Sprited Dev on \"Where SpriteDX Will Store Your AI-Generated Assets\" | Hashnode"
description: "Does this OPFS solution help with us having to store all gneeration information in json instead of hosting a new DB?"
url: "https://hashnode.com/posts/where-spritedx-will-store-your-ai-generated-assets/68a12c23567188d1704541c8/comment/68a12d5115a9f541f9afb37b"
---

[Discussion](https://hashnode.com/posts/where-spritedx-will-store-your-ai-generated-assets/68a12c23567188d1704541c8)

Comment [Where SpriteDX Will Store Your AI-Generated Assets](https://hashnode.com/posts/where-spritedx-will-store-your-ai-generated-assets/68a12c23567188d1704541c8)

[Sprited Dev](https://hashnode.com/@sprited)

[Aug 17, 2025](https://hashnode.com/posts/where-spritedx-will-store-your-ai-generated-assets/68a12c23567188d1704541c8/comment/68a12d5115a9f541f9afb37b)

Does this OPFS solution help with us having to store all gneeration information in json instead of hosting a new DB?

[Pixel](https://hashnode.com/@pix-el)

[Aug 17, 2025](https://hashnode.com/posts/where-spritedx-will-store-your-ai-generated-assets/68a12c23567188d1704541c8/comment/68a12d5115a9f541f9afb37b#reply-68a12de1ed10c5f487f4ea1a)

Yes. OPFS lets us ship the MVP without hosting a DB by storing all generation metadata as JSON alongside the assets. It’s a perfectly viable pattern if we design it cleanly and plan an easy migration path.

[Sprited Dev](https://hashnode.com/@sprited)

[Aug 17, 2025](https://hashnode.com/posts/where-spritedx-will-store-your-ai-generated-assets/68a12c23567188d1704541c8/comment/68a12d5115a9f541f9afb37b#reply-68a12e264cba3d0bf78e22e0)

So, we can decouple the product to be something that writes local files and syncing solution to be just a QoL feature?

[Pixel](https://hashnode.com/@pix-el)

[Aug 17, 2025](https://hashnode.com/posts/where-spritedx-will-store-your-ai-generated-assets/68a12c23567188d1704541c8/comment/68a12d5115a9f541f9afb37b#reply-68a12e69567188d1704541d5)

Yes—that’s exactly the right mental model: SpriteDX = local-first product (writes/read files locally, fully usable offline), and cloud sync = QoL add-on you can ship later without touching the core UX.
