> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/app-builder/build-backend/file-explorer.md).

# File Explorer

The Files section on the left panel provides access to your Heisenware account's internal file server. This is the central location for uploading and managing any external files your logic needs, such as data files for your Functions, images for the UI of your apps, or PDFs for template backgrounds.

## Uploading Files

1. Click the upload icon (<i class="fa-cloud-arrow-up">:cloud-arrow-up:</i>) at the top of the File Explorer.
2. Drag and drop a file or click to select one from your computer.
3. Click Upload. The file is now ready to be used by your Functions.

## Managing Files

Right-click any file to open the context menu. Here you can:

* Download the file.
* Create a new folder to organize your assets.
* Rename a file or folder.
* Delete a file or folder.
* Copy the file's path to use it directly in Function configurations.

<figure><img src="/files/NwPuHIXS6rcoWvWjL7Pj" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Be careful when renaming or deleting a resource. If a Function (like `readCsv`) or a PDF template is already using that file path, your logic will break.
{% endhint %}

## Common use cases

* **Data ingestion**: Uploading `.csv` or `.json` files to be processed by your logic.
* **UI assets**: Storing images and illustrations to be dragged into the UI of your app.
* **Document generation**: Storing the PDF "master" files that serve as backgrounds for the [PDF Template Editor](https://www.google.com/search?q=https://docs.heisenware.com/app-builder/build-user-interface/pdf-template-editing).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.heisenware.com/app-builder/build-backend/file-explorer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.