> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/getting-started/how-to-get-started/downloading-directly-to-cloud-storage-providers.md).

# Downloading Directly to Cloud Storage Providers

Guides to using third party cloud storage providers like Dropbox, AWS, and more

The Render Network is integrated into third party storage providers like Dropbox and AWS, with the aim to support over 60 of the leading cloud storage providers, enabling artists and studios to more efficiently download renders directly from the network to major cloud storage services. 

Downloading renders directly to third party cloud storage providers allows artists and studios in collaborative cloud workflows to bypass the friction of downloading renders locally and then re-uploading them to the cloud, saving time and bandwidth.\
The following articles provide in-depth details for using the Dropbox and AWS cloud storage integrations. 

**Guide to Using the Dropbox Cloud Storage Integration**

{% embed url="<https://know.rendernetwork.com/getting-started/how-to-get-started/downloading-directly-to-cloud-storage-providers/using-the-render-network-cloud-storage-integration-for-dropbox>" %}

**Guide to Using the AWS S3 Cloud Storage Integration**

{% embed url="<https://know.rendernetwork.com/getting-started/how-to-get-started/downloading-directly-to-cloud-storage-providers/using-the-render-network-cloud-storage-integration-for-aws-s3>" %}


---

# 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://know.rendernetwork.com/getting-started/how-to-get-started/downloading-directly-to-cloud-storage-providers.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.