> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/clients/managing-files.md).

# Managing files

The Files panel is where you upload and review source documents for a client. Files uploaded here drive the Binder, AI Tax Prep, and all other AI tools in the client hub.

## The files panel

On desktop, the Files panel appears as a right sidebar within the client hub. On mobile, the **Files** button in the client header opens it as a full-screen dialog. Both views show the same content and controls.

## How files are organized

Files are grouped by their source, called a document provider. Each provider appears as a collapsible folder labeled with the source name and a file count. "Manual upload" holds files you upload directly in Filed. If your workspace is connected to a document management system, files synced from that integration appear in their own labeled folder alongside manual uploads.

## Uploading files

The **Upload more files** button at the bottom of the panel opens an upload sheet where you can add documents for this client.

**Walkthrough: upload more files to a client**

1. At the bottom of the **Files** panel, click **Upload more files**. The **Upload more** sheet opens, asking where to bring documents in from. Choose **File upload**. (If your workspace is connected to a document management system, that integration is also listed here as a source.)

![The Upload more sheet with the File upload source](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/managing-files/image1.webp)

2. Select files with the file picker or drag them onto the drop zone. You can add multiple files at once, and ZIP archives are expanded automatically - each file inside is uploaded individually (see [Supported file types](#supported-file-types)).
3. Each new file enters the processing pipeline with a **running** status and moves to **completed** when it has been added to the binder. While files are processing, the client's status reflects the work in progress and returns to **Active** once binder creation finishes; the Binder card badge then shows "0 Missing" if every file was extracted successfully.

## Searching within files

A search input at the top of the file list filters rows in real time as you type. It appears only when the panel contains at least one file. If nothing matches, the panel shows a "No files match" empty state.

## Viewing file details

Each file row displays:

* A file-type icon indicating the format.
* The **filename**.
* A meta line showing the MIME type, how long ago the file was uploaded (for example, "2 hours ago"), and the file's current processing status.

File-level processing statuses are running, completed, and failed.

## Downloading files

The Files panel header contains a download icon. Clicking it downloads all files for this client.

## Expanding the files panel

An expand icon in the Files panel header opens a larger view of the file list, giving more room to browse or search when a client has many documents.

## File processing states

After upload, each file passes through a processing pipeline with three possible states:

| Status    | Meaning                                                                  |
| --------- | ------------------------------------------------------------------------ |
| running   | The file is currently being added to the binder and analyzed             |
| completed | The file was processed successfully; its data is available in the Binder |
| failed    | The file could not be processed                                          |

The aggregate result appears in the Binder card badge on the client hub: "0 Missing" if all files complete successfully, or "N Missing" where N is the count of files that could not be extracted. For the client-level status these results affect, see [Client Statuses](/reference/clients/client-statuses.md).

## Supported file types

Filed accepts the following file types for source document uploads:

| Format          | Extension(s) |
| --------------- | ------------ |
| PDF             | .pdf         |
| PNG image       | .png         |
| JPEG image      | .jpg, .jpeg  |
| CSV spreadsheet | .csv         |
| Excel workbook  | .xlsx        |
| Word document   | .docx        |
| ZIP archive     | .zip         |

ZIP files are automatically extracted on upload: each file inside the archive is unpacked and uploaded individually. Nested files within a ZIP are expanded the same way.

Draft return uploads (AI Review) and prior-year return uploads (AI Tax Planning) accept PDF only.

## Troubleshooting failed files

A file with a "failed" status could not be processed by Filed's binder creation pipeline. Common causes are corrupted files, password-protected PDFs, or files whose extension matches an accepted format but whose internal content does not.

To recover, confirm the file opens correctly on your computer (and, for PDFs, that it is not password protected), then re-upload it. If the problem persists, contact support with the filename and client name.

A failed file affects the Binder card badge (showing "N Missing") but does not stop you working with successfully processed files. If the client itself shows a "Failed" status badge, see [Client Statuses](/reference/clients/client-statuses.md) for what triggered that state.


---

# 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://help.filed.com/reference/clients/managing-files.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.