> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/notebooks/files.md).

# Files

Store, use and download files in a project.

Each project has a **file system** for the files it needs: data, reference documents, models and code. Open the files sidebar with **Ctrl+1** or **⌘+1** in the notebook view, or **Ctrl+2** or **⌘+2** in the canvas view.

## Uploading and using files

Upload files from the files sidebar. Your code can then read them by their path, as on your own computer.

You can also import `.py` files from the file system as modules in your blocks.

## Saving files from code

Code can write files to the file system. For example, to download a file from the web in Python:

```python
import requests

url = "https://archive.ics.uci.edu/ml/machine-learning-databases/iris/iris.data"
file_path = "./iris_dataset.csv"

response = requests.get(url)
if response.status_code == 200:
    with open(file_path, "wb") as file:
        file.write(response.content)
```

Or in R:

```r
url <- "https://archive.ics.uci.edu/ml/machine-learning-databases/iris/iris.data"
download.file(url, "./iris_dataset.csv", method = "auto")
```

## Downloading and deleting files

Download any file to your computer from the files sidebar, or delete files you no longer need.

## Larger data

For large or shared datasets, use a [data connection](/zerve-docs/data-and-assets/connections.md) instead of uploading files.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/notebooks/files.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.