> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mythos.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Files and artifacts

> The workspace Files tab holds non-code files — downloadable artifacts the agent generates (PDF, CSV, XLSX, charts) and files you upload in chat.

The **Files** tab in the workspace is where your project's non-code files live. It holds two things:
**artifacts** the agent generates for you to download — a PDF, a CSV, a spreadsheet, or a chart — and
**files you upload** through the chat composer. It's deliberately separate from your site's code: the
images and components that make up the website itself stay in the Code view, not here.

The mental model: Code is the site you're building; Files is the stuff *around* it — a generated
report, an exported data dump, a chart image, or a document you handed the agent to work from.

<Note>**Cost:** asking the agent to generate an artifact happens inside a normal build or edit, so it
costs the usual **3 credits** (build) or **2 credits** (edit). Uploading a file in the Files tab is
free. See [Credits & usage](/introduction/credits-and-usage).</Note>

## Why use it

* **Get real deliverables, not just a website.** Ask for a PDF invoice, a CSV export, or a chart and
  download the actual file.
* **One place for everything that isn't code.** Generated documents and uploaded files are grouped,
  searchable, and downloadable in the same view.
* **Hand the agent reference material.** Upload a file once and reference it in later prompts.

## What the agent can generate

Ask for any of these in plain language and the agent produces a downloadable artifact:

| Kind  | What you get                | Example request                         |
| ----- | --------------------------- | --------------------------------------- |
| PDF   | A rendered document         | "Make a one-page PDF contract."         |
| CSV   | A comma-separated data file | "Export these orders as a CSV."         |
| XLSX  | An Excel spreadsheet        | "Put this into a spreadsheet."          |
| Chart | A chart image               | "Build a bar chart of monthly revenue." |

The agent is steered to treat these as separate deliverables — generating an artifact doesn't change
your website's code.

## How to generate an artifact

<Steps>
  <Step title="Ask for it in chat">
    Describe the file you want — a PDF, a CSV, a spreadsheet, or a chart — in a normal build or edit
    prompt.
  </Step>

  <Step title="Wait for the build to finish">
    The agent generates the artifact as part of the run. When it's done, the artifact appears in the
    Files tab.
  </Step>

  <Step title="Open the Files tab">
    Find the file grouped by type (Documents, Spreadsheets, Charts, Images, Other), or use search.
    Preview it, then **Download**.
  </Step>
</Steps>

## How to upload a file

<Steps>
  <Step title="Use the Upload button in the Files tab">
    Upload a file directly into the project's files.
  </Step>

  <Step title="Or attach it in chat">
    Files attached through the chat composer also appear here. See
    [Chat attachments](/features/chat-attachments) for the per-message flow.
  </Step>

  <Step title="Reference it later">
    From a file in the Files tab, use **Reference in chat** to drop a reference into your next prompt
    so the agent works from it.
  </Step>
</Steps>

## Examples

Generate a spreadsheet from data described in chat:

```
Take the order list above and export it as an XLSX spreadsheet with columns
for date, customer, item, and total.
```

Generate a chart:

```
Build a bar chart of these monthly signup numbers and give me the image.
```

Generate a document:

```
Create a one-page PDF invoice for Acme Inc. — line items, subtotal, and total.
```

## Limitations & good to know

* **Files are not your site's code.** Images used by the website live in the code (under `src/assets`)
  and show in the Code view, not here. The Files tab is for artifacts and uploads only.
* **A PDF renders on first download.** For PDF artifacts, the agent writes the document and Mythos
  renders the final PDF the first time you download it, then caches it. The first download of a PDF can
  take a moment longer.
* **Charts are static images.** A generated chart is an image of the chart, not an interactive widget.
* **Re-running a generation replaces a file with the same name** rather than stacking duplicates.
* **There's a per-project limit** on how many artifacts a project keeps; older ones are dropped once
  the limit is reached.
* **PowerPoint and other formats aren't generated yet.** The supported artifact kinds are PDF, CSV,
  XLSX, and charts.

## FAQ

<AccordionGroup>
  <Accordion title="How do I get the agent to make a file?">Just ask in a normal prompt — "make a PDF…", "export as CSV…", "build a chart…". The artifact lands in the Files tab when the build finishes.</Accordion>
  <Accordion title="Does generating an artifact cost extra?">No extra charge beyond the build or edit it's part of — 3 credits for a build, 2 for an edit.</Accordion>
  <Accordion title="Where did my uploaded file go?">Files you upload — via the Files tab or the chat composer — appear in the Files tab. Files attached in chat are committed before the agent runs.</Accordion>
  <Accordion title="Can I edit a generated artifact?">Ask the agent to regenerate it with changes. A new generation with the same filename replaces the old one rather than adding a duplicate.</Accordion>
  <Accordion title="Will generating a PDF change my website?">No. Artifacts are separate deliverables; the agent is instructed not to touch the site's code when making one.</Accordion>
</AccordionGroup>

## Related

* [Chat attachments](/features/chat-attachments) — attach images and files to a single prompt.
* [Skills](/features/skills) — reusable instructions the agent applies across projects.
* [Credits & usage](/introduction/credits-and-usage) — what a build or edit costs.