Skip to main content

Command Palette

Search for a command to run...

Where SpriteDX Will Store Your AI-Generated Assets

Updated
2 min readView as Markdown
Where SpriteDX Will Store Your AI-Generated Assets

SpriteDX is a one-click AI tool for generating animated sprite characters that you can drop into whatever tools you already use. As we build the Web UI, we’ve explored two storage paths for your generated assets.

Option 1 — Cloud Object Storage (Cloudflare R2 / Backblaze B2)

Storing assets in object storage is straightforward and inexpensive. For example, Cloudflare R2 is $0.015 per GB-month—so 100 GB ≈ $1.50/month. Backblaze B2 can be cheaper depending on your egress patterns.

Pros

  • Cheap, scalable, durable

  • Easy to add multi-device sync and sharing later

Cons

  • Requires auth, quotas, and abuse controls from day one

  • Adds operational surface area (billing, limits, lifecycle policies)

Option 2 — Local Browser Storage (OPFS)

OPFS gives each site a private filesystem. SpriteDX can create/read/update/delete files locally without any server setup.

Pros

  • Zero setup, zero auth, instant performance

  • Works offline; great “creator-tool” UX

Cons

  • Eviction risk under device storage pressure

  • “Clear browsing data” nukes assets

  • No cross-device sync out of the box

  • Safari does not support choosing a real OS folder (File System Access API); Chromium does

We can request persistence with navigator.storage.persist(). It doesn’t guarantee forever, but it significantly reduces eviction risk.


Our Initial Call

We’re starting OPFS-first for the MVP.

Why

  • Fastest path to a great single-device creation experience

  • No login friction; works offline

  • Minimal ops while we iterate on core generation quality

Mitigations we’ll ship with MVP

  • Ask for persistent storage (persist())

  • Monitor quota and warn early (storage meter + “backup recommended”)

  • Export/Import projects (.spritedx.zip)

  • On Chromium, offer “Choose project folder” for true on-disk persistence (power-user option)

Then

  • Add optional cloud sync (R2/B2) for backup and multi-device continuity

  • If we go desktop (e.g., Tauri), swap to the real file system for guaranteed persistence


When We’d Flip to Cloud-First

  • You need multi-device access on day one

  • Real-time collaboration/sharing becomes core

  • Mobile-heavy workflows where eviction risk is higher

  • We promise archival/retention guarantees


TL;DR

  • MVP: OPFS by default (fast, offline), plus export and persistence request, with a Chromium “link folder” option.

  • Soon after: optional cloud sync for backup and portability.

  • Future: desktop app → true file system persistence.

S
Sprited Dev10mo ago

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

P
Pixel10mo ago

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.

S
Sprited Dev10mo ago

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

P
Pixel10mo ago

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.