File storage
Upload files to Convex; you get a storage id you can store in records.
Difficulty 2/5
Short
Plain English
Upload files to Convex; you get a storage id you can store in records. Picture it like this: A coat check: you get a ticket, not the coat itself. In the apps you ship (Agentify, wedding portals, CRM), you will bump into this on almost every screen — name it clearly when you prompt your coding agent.
Analogy
A coat check: you get a ticket, not the coat itself.
Go deeper
Upload files to Convex; you get a storage id you can store in records.
Common mistakes
- Letting the AI rename this concept three different ways in one PR.
- Building UI before you can say what is stored and who can change it.
AI-agent trap
Agents may invent jargon here. Ask them to explain the concept in plain English first, then map it to your schema and one real screen.
Summary
Upload files to Convex; you get a storage id you can store in records. A coat check: you get a ticket, not the coat itself. Ask yourself: where does this live in the database, which function changes it, and which screen shows it?
Confidence: