Attaching files to a prompt
Attach spreadsheets, PDFs, images or data files to a prompt and the AI reads them as reference material — a spec to follow, sample data to model, a mockup to match.
Files belong to the prompt you send them with. They are inputs, not project source: the AI reads them, and never commits them into your code.
Attaching a file
Two ways, both in the composer:
- Drag files onto it — a Drop files here overlay appears while you hold them there.
- Or click Attach file (the paperclip) and pick them.
Each file uploads immediately and shows a chip with its name, size and progress; a tick means it is ready. Generate stays disabled until every upload finishes, so a prompt can never go out with a half-uploaded file.
Click a chip to preview it — text and images render in place, and spreadsheets and PDFs show the text that was extracted from them. The ✕ removes one, and Try again appears on an upload that failed.
Send the prompt and the chips move onto your message, where they stay in the history.
What you can attach
| Kind | Formats |
|---|---|
| Text & data | .txt, .md, .csv, .tsv, .json, .yaml |
| Spreadsheets | .xlsx, .xls |
| Documents | .pdf |
| Images | .png, .jpg, .webp |
Up to 5 files per prompt, each up to 10 MB.
How the AI reads them
Your files land in a folder the AI opens before it starts working, with an index naming each one and where to find it:
- Spreadsheets are converted to a plain-text table — the first 5 sheets, 50 rows each — and the AI is pointed at that view rather than the binary.
- PDFs are converted to plain text, capped at 100 KB.
- Images the AI opens and looks at, so "match this mockup" works.
- Text and data files are read as they are.
Attached text also reaches the planning stage, so a plan is drawn from your real spec instead of a guess — and once a plan is running, the files stay available to every step in it.
If a file cannot be converted, the prompt still runs. The AI gets the original plus a note that the conversion failed, so it tells you rather than inventing the contents.
Managing what you attached
Removing a chip before you send deletes the file. Once sent, the file stays with its prompt, and cannot be deleted while that prompt is still running.
Attachments count against 10 MB of storage per project — the total across everything you have attached there, not a per-prompt allowance. When it fills, delete files you no longer need, or wait: attachments are deleted automatically 30 days after upload.
Uploading is free; reading is not. File contents go through the AI like the rest of your prompt, so a large spreadsheet makes that run more expensive. See how credits work.
Limits & notes
- 5 files per prompt · 10 MB per file · 10 MB stored per project · deleted after 30 days.
- The type check reads the file type your browser reports, not the extension. A plain-text file with an unusual extension can be rejected as unsupported — save it as
.txtand attach it again. - A scanned PDF is a picture of text. There is no OCR, so it can come back empty — attach the source file, or paste the text into the prompt.
- Long files are trimmed for the AI, not for you: spreadsheets to 5 sheets of 50 rows, PDF text to 100 KB. If what matters sits further down a large file, cut it out and attach that.
- Only you can preview, download or delete the files you attached. Their names do show on your message in the chat, so collaborators can see what a prompt was given.
- Limits may change during alpha.