convex-file-storage

To handle file uploads in a Convex application, you generate upload URLs for client-side uploads to store images, documents, and generated assets, then save their file references in your data model.

Yes, you can store generated artifacts from Convex actions and serve them via stable URLs, providing reliable access to generated files for user-facing experiences alongside retrieving file metadata from system tables.

The best way to delete files in Convex is to use a workflow that deletes the stored file along with its associated metadata, ensuring that both the file reference in your data model and the system storage entry are removed.

Yes, Convex file storage supports accessing file metadata from system tables, allowing you to retrieve URLs for display and manage file references effectively within your own data model after client-side uploads.

You generate upload URLs in Convex to enable client-side uploads for storing any file type, then save the file references in your own data model and retrieve their URLs for display or deletion.

Serving stored files via URL in Convex requires saving file references in your own data model first, and you must manage the lifecycle of these files by deleting both the file and its associated metadata when no longer needed.