convex-file-storage

To manage file storage in Convex, you can use mutations and queries to generate upload URLs, save file references, and serve files via deterministic URLs. This handles the complete upload, serve, and metadata access lifecycle for images, documents, and generated assets.

The best way to store generated content in Convex is through server-side actions that save files directly to storage. You can then retrieve file metadata from the _storage table and serve the generated assets via deterministic URLs.

You retrieve file metadata from the Convex _storage table by running queries that access saved file references. This allows your application to query storage metadata for robust data integrity when serving images, documents, and other uploaded assets.

Yes, you can delete files and clean up storage references in Convex. The system provides mutations to remove files from storage and delete their associated database references, ensuring complete end-to-end file lifecycle management and cleanup.

Convex file storage supports end-to-end workflows for images, documents, and generated assets. It covers uploading via generated URLs, serving files through deterministic URLs, accessing metadata, and deleting files for robust data integrity.