> 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/stackai-mcp/tool-reference/file-uploads/files-upload.md).

# files\_upload

Upload small files inline as standard base64 and receive signed\_url, file\_id and file metadata. purpose defaults to user-documents; mime\_type defaults to application/octet-stream.

**Effect:** This call saves data or changes configuration. Review the behavior below before using it.

## Inputs

| Name             | Type   | Requirement | Description                                                                                        |
| ---------------- | ------ | ----------- | -------------------------------------------------------------------------------------------------- |
| `filename`       | string | Required    | Name of the uploaded file, including its extension.                                                |
| `content_base64` | string | Required    | Standard base64 of the complete file bytes.                                                        |
| `purpose`        | string | Optional    | Default `user-documents`. Allowed: `user-documents`, `user-content`, `user-tables`, `form-banner`. |
| `mime_type`      | string | Optional    | Content type. Default `application/octet-stream`.                                                  |

## Example

These are MCP tool arguments, not an HTTP request body. Replace bracketed IDs with values returned from your account.

```json
{
  "filename": "notes.txt",
  "content_base64": "QXBwcm92ZWQgbm90ZXMu",
  "mime_type": "text/plain"
}
```

## Result

Abbreviated result example; unshown fields are omitted for clarity.

```json
{
  "file_id": "<file-id>",
  "filename": "notes.txt",
  "bytes": 15,
  "signed_url": "<temporary-file-url>"
}
```

## Behavior

Each call creates a file.

The approximate limit is 200 KiB before base64 encoding.

The full JSON request must also fit within 256 KiB, so encoding overhead may lower the usable file size.

For files near this limit, use `files_create_upload_url` instead.

## Troubleshooting

If the body exceeds the transport limit, use the large-file upload route. Base64 makes the request larger than the original file.

## Related resources

[File uploads](https://docs.stackai.com/stackai-mcp/tool-reference/file-uploads.md)

[Connection, permissions, pagination, and recovery](https://docs.stackai.com/stackai-mcp/best-practices-and-troubleshooting.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/stackai-mcp/tool-reference/file-uploads/files-upload.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.
