Skip to Content
TroubleshootingAssets Without a Saved Canvas

Fix: Images Show Up but the Canvas Is Missing

Symptom

In the All Members admin view, a member shows image assets in storage but 0 canvases — or a canvas you expect to see just isn’t listed.

Why this happens

Canvases and images are stored separately:

Canvas document:
craftboard_users/{uid}/projects/{projectId}

Image file:
craftboard_users/{uid}/images/{imageId}

Normally, a generated or pasted image becomes an image node, a Storage asset, and a firebase: reference inside the saved project document, all together. Before recent protections were added, it was possible for a user to end up with image assets but no saved project document — for example, if sync was interrupted before the canvas itself saved.

Current protections reduce this: the editor blocks image work until canvas sync is ready, persistent Firebase asset references trigger an immediate project save, and Storage references outside the owner’s UID are stripped from project saves. But older, pre-fix orphan assets can still show up this way.

Causes to check, in order

  1. Pre-fix orphan assets — images generated before the current save protections existed
  2. Deletion — the canvas was deleted, but its images remain in Storage
  3. Browser-local state that never synced — the canvas may still exist only in the original browser’s local storage

How to recover

  • Check the original browser’s local storage / IndexedDB for the canvas — it may still be there even if it never synced.
  • Check for an export of the canvas (see Export a Canvas) taken before the issue occurred.
  • Check canvas history if available.
  • As a last resort, the canvas may need to be manually reconstructed from the surviving image assets.

What not to assume

Don’t conclude that Firebase was reset based on this symptom alone. Inspect the user’s profile, project documents, and Storage assets separately — each tells a different part of the story.

OverviewCommon Issues