> 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/creating-large-productions-on-the-render-network/workflow-recommendations.md).

# Workflow Recommendations

### The Manager App & API

* Use **Presets** in the Manager App to streamline job submissions:
* Build from completed jobs or predefine custom setups per job

Please see detailed information about the Manager App here

{% embed url="<https://know.rendernetwork.com/getting-started/using-the-render-network-manager-app-and-render-network-api>" %}

### Using Differential Uploading

The Render Network uses **Differential Upload** to save time:

* On your first upload, all assets are uploaded normally.
* On future submissions using unchanged assets, the network only uploads differences.
* This drastically speeds up subsequent job submissions.

**Using the Manager App automatically enables Differential Upload.** WebApp supports it as well.

![](https://1286142079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKt2GmpnqwLIsi-Sh1Z%2Fuploads%2F8n5q2z0aesKiWrKo1Z8E%2Funknown.png?alt=media\&token=b3a30435-9337-4fe6-a04e-a9fb61949a8c)

Here is a guide to using Differential Uploading from Octane Standalone.

{% embed url="<https://know.rendernetwork.com/getting-started/render-network-tutorials/using-renders-differential-uploading-from-octane-standalone>" %}

#### Using Render Network Cloud Storage

{% embed url="<https://know.rendernetwork.com/getting-started/how-to-get-started/downloading-directly-to-cloud-storage-providers>" %}

Massive renders aren’t like sending a Dropbox link to a client for a few JPEGs. An 18K sequence can be hundreds of gigabytes. Uploading, downloading, and re-transferring files between people wastes days if it’s not planned.

* **Why it matters:**\
  Cloud storage networks like **Amazon S3, Dropbox**, or **Google Drive** can act as the bridge between render output and delivery. They let you sync straight from the render network to cloud, or link a local hotfolder that uploads automatically. This means you don’t have to manually babysit transfers every time.<br>
* **What happens if you skip it:**\
  You end up downloading files locally just to re-upload them again for delivery, doubling your transfer time. With files this size, that can mean losing a full day or more — often at the worst possible moment.<br>
* **How to address it:**\
  Set up cloud storage in advance. Point your render outputs to a hot folder that syncs to the cloud. Once the frames land, the other party can start pulling them down immediately - even while new frames are still uploading. This simple workflow saves hours and avoids delivery delays.


---

# 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/creating-large-productions-on-the-render-network/workflow-recommendations.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.