convex-file-storage

You can store and serve files in Convex by generating a secure upload URL, sending the file payload to that URL, and saving the resulting storage identifier in your database via a mutation.

The best way to serve user avatars and documents is to retrieve the stored file's metadata and generate a serving URL. This provides web and mobile clients direct access to the generated assets without a custom back end.

Yes, you can delete stored files and their associated metadata using Convex mutations. This removes the physical storage entry and cleans up the system tables tracking the file references.

Yes, Convex file storage manages generated assets without a custom backend by providing built-in storage APIs. It handles upload URLs, secure storage, serving via URL, and metadata access entirely within your Convex application.

Limitations of Convex file storage include relying entirely on the platform's built-in storage APIs and system tables for metadata tracking. You must use generated upload URLs and mutations rather than direct file system access or custom backends.