> 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-create-upload-url.md).

# files\_create\_upload\_url

Prepare a large-file upload using filename, exact byte\_length and content\_hash=base64(SHA-256(file bytes)).

**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.                                                                           |
| `byte_length`  | integer | Required    | Exact file size in bytes, from 1 through 104857600 (100 MiB).                                                                 |
| `content_hash` | string  | Required    | Standard base64 of the SHA-256 digest of the exact file bytes: 44 characters ending in `=`. Do not send a hexadecimal digest. |
| `purpose`      | string  | Optional    | Default `user-documents`. Allowed: `user-documents`, `user-content`, `user-tables`, `form-banner`.                            |
| `mime_type`    | string  | Optional    | Content type. Omitted: inferred from filename.                                                                                |

## Example

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

The size and hash below correspond to the UTF-8 bytes `Approved notes.` with no trailing newline. Compute them from your actual file before sending the request.

```json
{
  "filename": "notes.txt",
  "byte_length": 15,
  "content_hash": "ccX1sDcgkglGrhFPo8Jc7mUSr9TXl+bpdPhYftxpbE0=",
  "mime_type": "text/plain"
}
```

## Result

Abbreviated result example; unshown fields are omitted for clarity.

```json
{
  "file_id": "<file-id>",
  "bytes": 15,
  "upload_url": "<temporary-upload-url>",
  "upload_token": "<temporary-upload-token>"
}
```

## Behavior

The hash is 44 characters ending in =.

Maximum file size is 100 MiB.

Returns upload\_url, upload\_token, file\_id, expiry and next\_step.

The client must PUT the bytes directly with Authorization: Bearer \<upload\_token>, then finalize.

Bytes do not pass through MCP.

Duplicate content hashes can reuse a file record.

## Troubleshooting

If size or hash validation fails, recompute both from the exact bytes to be uploaded. Complete the PUT before the returned expiry; do not finalize an incomplete upload.

## Related resources

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

[Upload a larger document](https://docs.stackai.com/stackai-mcp/workflow-recipes/upload-a-larger-document.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-create-upload-url.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.
