> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/file-inputs-supported-formats-and-size-limits.md).

# File Inputs, Supported Formats, and Size Limits

File inputs pass documents or media to a workflow. The supported format and size depend on the receiving node, parser, and upload path.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FeDoAU9vC8BKj4VoLNrJy%2FG027.mp4?alt=media&token=48db82ec-dfc4-468c-9563-a0b99ce04d4b>" %}

## Before you begin

Identify whether you are uploading into a workflow input, a knowledge base, or the Files API. Check the corresponding formats and limits below before uploading.

## Supported document formats

Knowledge-base ingestion supports the following file families. A specialized workflow input or model can accept a smaller set; a file that can be stored is not necessarily readable by every processing step.

| Content                           | Formats                                                              |
| --------------------------------- | -------------------------------------------------------------------- |
| Documents                         | PDF; Word DOC, DOCX, DOCM, DOTX, DOTM; OpenDocument ODT              |
| Spreadsheets                      | CSV; XLS, XLSX, XLSM, XLSB, XLTX, XLTM; ODS                          |
| Presentations                     | PPT, PPTX; ODP                                                       |
| Text and structured text          | TXT, HTML/HTM, XML, Markdown, JSON, YAML/YML, PY, CSS, CPP, SQL, VTT |
| Images                            | JPG/JPEG, PNG, GIF, BMP, TIFF/TIF, SVG                               |
| Audio and media for transcription | MP3, MP2, MP4, AAC, WAV, FLAC, M4A, OGG, OPUS, WEBM                  |
| Email and archives                | EML, MSG, ZIP                                                        |

Google Workspace documents are imported through their source connection. Renaming a local file to a Google Workspace extension does not turn it into a supported cloud document.

## Size limits by upload path

| Upload path                                                                       | Maximum size                           | Scope                                                                             |
| --------------------------------------------------------------------------------- | -------------------------------------- | --------------------------------------------------------------------------------- |
| Knowledge-base resource upload                                                    | 1,000,000,000 bytes (1 GB)             | General cap per file; lower type-specific limits below still apply.               |
| Knowledge-base DOCX upload                                                        | 104,857,600 bytes (100 MiB)            | DOCX has a lower cap.                                                             |
| Knowledge-base MP4, MP3, MP2, AAC, WAV, FLAC, M4A, OGG, OPUS, WEBM, or SVG upload | 21,000,000 bytes (21 MB, about 20 MiB) | Per-file type-specific cap.                                                       |
| Files API upload                                                                  | 536,870,912 bytes (512 MiB)            | File storage limit; it does not override the receiving node’s or parser’s limits. |

The upload control can apply a lower limit than the storage API. If a file is rejected, use the limit shown by that control or error rather than the limit for a different upload path. For Files API requests, see [File Upload and Download Contracts](https://docs.stackai.com/technical-reference/apis-and-mcp/file-upload-and-download-contracts.md).

## File input terms

| Term           | Definition                                                                                                                                                      |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| File reference | An identifier or URL used to pass a file to a supported operation. It must be accessible and use the format expected by that operation.                         |
| Upload         | Transfer of file bytes through a supported interface or API. Upload acceptance does not establish parsing or indexing completion.                               |
| Finalization   | A required confirmation step for upload methods that separate allocation from completion. Do not use an allocated upload URL as if the file were already ready. |
| Parsing        | Extraction of usable text or structure from source content. Review the extracted content when the workflow misses text, tables, or locations.                   |
| Schema         | A definition of fields, types, required values, and supported constraints. Use it to validate the shape of data; it does not establish factual correctness.     |

## Provide a file input

1. Inspect whether the input expects a file reference, one URL, or a list.
2. Upload the file through the supported interface or file API.

![Add the source document through the Files input before passing it to a processing step.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/xOpgyviU2vgCFzmISIvy/assets/g027-g027-01-pdf-file.png)

Add the source document through the Files input before passing it to a processing step.

3. Map the completed upload reference to the node and inspect the parsed result.

Confirm the node receives the file reference and that parsing returns the expected content.

## Use an interface upload in an agent

Expose the intended Files input in the interface and reference it in the agent’s Prompt. For inspection, analysis, or generated downloads, configure **File Access** with the appropriate file tool. The interface’s upload icon alone does not perform this setup.

Follow [Let an agent work with uploaded files](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/let-an-agent-work-with-uploaded-files.md) for a real chat upload and downloadable result, or use [Troubleshoot uploaded files and downloads](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/let-an-agent-work-with-uploaded-files/troubleshoot-uploaded-files-and-downloads.md) to investigate reading and output problems.

## Behavior and limitations

Allocating an upload URL is not the same as completing and finalizing an upload. A file accepted for storage can still fail parsing. Do not apply one tool’s size limit to every upload path. A workflow file upload does not automatically add the file to a knowledge base.

## Related resources

[Document, image, and URL processing](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/document-image-and-url-processing.md)

[Parsing, OCR, and Document Structure](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/parsing-ocr-and-document-structure.md)


---

# 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.stackai.com/technical-reference/files-knowledge-and-retrieval/file-inputs-supported-formats-and-size-limits.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.
