Files and storage

Files show up in three different places in Vaulter, and they behave differently in each: files you attach to a chat message, assets that are part of your app, and files your users upload into your app. Knowing which is which saves confusion about where things went and who can see them.

1. Chat attachments: context for the agent

You can attach up to 4 files per message, 8 MB each, to any chat message. These are input for the agent, not part of your app:

• Images (PNG, JPG, GIF, WebP): screenshots of bugs, designs to match, photos to use. Showing beats describing; this is the highest-leverage habit in the prompting guide.
• Documents (PDF, Word, plain text): specs, copy decks, requirements.
• Spreadsheets (CSV, XLSX, XLS): the agent reads the columns and sample rows, which makes "build me a dashboard for this data" work in one message.

If a spreadsheet is rejected as unsupported, check the file actually ends in .csv, .xlsx, or .xls; browsers sometimes report unhelpful types, and the extension is what rescues them.

When you attach an image and ask for it to be used in the app ("use this as the hero image"), Vaulter promotes it into your app's asset store automatically, so one message does both jobs.

2. App assets: images that ship with your app

Vault → Storage is your app's media library for images (PNG, JPG, GIF, WebP, SVG): upload, copy URLs, rename, and delete. Anything here is available to your app in the preview and the published version alike, and the agent can see the list, so "put the logo I uploaded in the header" works by name.

Asset upload size follows your plan: 10 MB on Free, 50 MB on Starter, 100 MB on Pro and Teams. Oversized files are refused with a clear message.

3. User uploads: files inside your app

If your app lets its users upload files (a profile photo, a document to a case, an image on a listing), ask for the feature in chat and the agent builds it: the upload control, the storage, and the wiring to display the file where it belongs.

When you ask for an upload feature, say who should see the files, the same way you would for data: "clients upload documents that only they and I can see" is a different build from "sellers upload photos everyone can browse". Stating it up front gets the visibility right the first time, and test it with two accounts before launch like any other privacy decision.

Frequently asked

What image format should I use for logos and photos?

PNG or WebP for logos and anything with sharp edges or transparency, JPG or WebP for photos. Keep files under a megabyte or two where you can; the biggest single cause of a slow-feeling app is multi-megabyte images.

Can I replace an asset and keep the same URL?

Asset filenames are unique per upload, so upload the new version and ask the agent to switch to it (or point Edit Mode at the image). That also means a stale cached copy can never mask your update.

A file type I need is not accepted

Chat attachments accept the types listed above. For anything else, the content usually travels another way: paste text directly into chat, or convert the file. If your app's users need to upload a specific type, say so when asking for the feature; the accepted types of your app's own upload feature are part of its build.

Where do user uploads actually live?

In your app's own storage on Vaulter's managed backend, alongside its database. They are separate from the public asset library, which holds only what you upload as the builder.