@devries-cameron20 / composio Mirror · read-only
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

next
md 21 lines 1.29 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "File Download Storage and Expiry"
4 description: "Public guidance for staged files, signed download URLs, retention, and size questions."
5 category: "sessions-and-execution"
6 visibility: "public"
7 timestamp: "2026-07-16T00:00:00Z"
8 tags:
9 - "files"
10 - "storage"
11 - "signed-urls"
12 ---
13 # File Download Storage and Expiry
14
15 ## Composio file URLs are short-lived staged downloads
16
17 When a hosted tool returns a file URL such as `data.file.s3url`, Composio normally stages the bytes in Composio-managed object storage and returns a signed download URL rather than the provider's original URL.
18
19 The default signed-URL lifetime is one hour. Organization admins can change it to any duration from 1 second to 24 hours in [**Project Settings > General**](https://dashboard.composio.dev/~/project/settings/general?utm_source=docs&utm_medium=content&utm_campaign=platform-file-storage) under **Configuration > File download link expiry**. Staged files are cleaned up after 24 hours. URL expiry and file cleanup are separate: rerun the tool or download the file again to obtain a fresh URL.
20
21 There is no single customer-facing maximum that applies to every tool. Provider limits, the action implementation, runtime memory, and timeouts can impose lower limits, so check the exact action before quoting a hard cap.