Content

When your app lets people upload a profile picture, attach a document, or generate a PDF, those files have to live somewhere. The Content view is the window onto that file storage — every file your app has stored, browsable in one place, without leaving the console.

Annotated screenshot of the Content view: a folder tree on the left, a file list in the middle showing names, sizes, and a status pill ("Uploaded", "Pending"), and a status filter at the top. Callout: "Browse every file your app stores, organized in folders."

Browsing your files

Files are organized into folders, just like on your own computer. Open a folder to see what's inside — each file shows its name, size, and current status. It's a straightforward way to confirm that an upload landed, find a file by name, or check how much you're storing.

File status

A file isn't always ready the instant someone starts an upload, so each one carries a status:

• Uploaded — fully stored and ready to use.
• Pending — an upload that's been started but hasn't finished landing yet.
• Expired / Deleted — files that were time-limited or removed, kept visible so you have a complete picture.

Filter by status at the top to, say, show only what's fully uploaded, or hunt down uploads that never completed.

Content gives you a plain, file-explorer view of your storage — no special tooling, no guessing whether a user's upload actually made it.

How files get there

Files arrive because your app put them there — a user uploaded one, or a function generated one. This view doesn't change how that happens; it's where you go to see and verify the result. To change what your app stores or how, describe it in the Builder.

Where to go next

• Database schema — the structured data that sits alongside your files.
• Functions — the jobs that store and generate files.
• Logs — trace an upload that didn't behave as expected.