# Uploading Scenes From Cloud Storage Uploading Scenes from Cloud Storage with a Watch Folder | TL;DR: Render Network can create a new Scene from a connected cloud storage account. Upload your scene file and assets first, then upload render\_config.json last. That JSON file is the trigger. For Dropbox, the watch folder should be created at the Dropbox root, not inside Apps/Render Network. The Apps/Render Network folder is used for outputs. | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ## Overview Render Network can monitor a connected cloud storage location and create a new Scene automatically when a valid render\_config.json file appears. This allows you to prepare a scene in cloud storage instead of manually uploading the scene through the Render Network web portal. The workflow is simple: place the scene file in the watched cloud location, make sure all required assets have finished syncing, then upload render\_config.json as the final file. Render Network looks for the scene named inside the JSON file and creates one Scene from that upload. | Important: render\_config.json must be uploaded last. If the JSON file arrives before the scene file or supporting assets are fully uploaded, Render Network may try to ingest an incomplete scene. | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ### Supported cloud storage providers Cloud watch folder submission is configured from your Render Network account page under Cloud Storage. The same render\_config.json trigger format is used for supported providers. * Dropbox * Amazon S3 * Google Drive Provider-specific folder behavior may vary, so use the folder or bucket location shown in your Cloud Storage configuration as the source of truth. ## How the watch folder trigger works 1\. Connect a cloud storage provider from the Render Network account page. 2\. Configure the watch folder or bucket location. 3\. Upload your scene file and supporting assets to the watched location. 4\. Wait until the upload is complete and the file size is fully available in the cloud provider. 5\. Upload render\_config.json last. 6\. Render Network detects the JSON file, reads the scene name, searches that location including subfolders, and creates one Scene. ### Supported scene file extensions The scene name inside render\_config.json must point to a file using one of these extensions: |

blend
c4d
ocs
orbx
zip

| | ----------------------------------------- | ## render\_config.json format The file must contain valid JSON. The scene name must be an exact match to the file in cloud storage, including extension and capitalization. ### Native scene files Use this format for .blend, .c4d, .ocs, or .orbx files: |

{
"scene": {
"name": "my\_scene.orbx"
}
}

| | -------------------------------------------------------------------- | ### Zip files For .zip files, include the host application so Render Network knows which application should open the packaged scene: |

{
"scene": {
"name": "my\_scene.zip",
"host\_application": "octane"
}
}

| | --------------------------------------------------------------------------------------------------------- | Supported host\_application values: |

blender
c4d
octane

| | --------------------------------------------------------------------------------------------------------------------------------------- | | One JSON equals one Scene. For multiple scene submissions, use separate folders and a separate render\_config.json file for each scene. | ## Universal submission rules * Upload render\_config.json last. It is the trigger for scene ingestion. * The scene.name value must match the scene file exactly, including extension and case. * Only one Scene is created per render\_config.json upload. * For zip files, host\_application is required and must be set to blender, c4d, or octane. * Use a separate folder per scene when submitting multiple scenes. * Confirm large files have fully uploaded before adding the JSON file. ## Dropbox setup Dropbox has two important folder locations. They are not the same folder. | Folder | Dropbox location | Purpose | | ------------- | --------------------------------------------- | ---------------------------------------------------- | | Watch Folder | Dropbox root, for example /RENDER\_SUBMISSION | Upload scene files and render\_config.json here. | | Output Folder | Apps/Render Network/\ | Finished outputs are written here by Render Network. | | Most common Dropbox mistake: creating the watch folder inside Apps/Render Network. The watch folder should be at the Dropbox root. Apps/Render Network is used for output files. | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
### Configuring Dropbox in Render Network 1\. Create the watch folder at the Dropbox root. Example: RENDER\_SUBMISSION. 2\. In Render Network, go to Account > Cloud Storage. 3\. Choose Dropbox and select Connect to Render. 4\. Enter a connection name, output folder, and watch folder. 5\. Submit, authorize Dropbox when redirected, then return to Render Network. Example Dropbox configuration: | Field | Use | | ------------- | ------------------ | | Name | User Dropbox | | Output Folder | RENDER\_NETWORK | | Watch Folder | RENDER\_SUBMISSION | ### Dropbox folder example |

Dropbox/
├── RENDER\_SUBMISSION/ # watch folder at Dropbox root
│ ├── job\_001/
│ │ ├── hero\_scene.orbx
│ │ └── render\_config.json # upload LAST
│ └── job\_002/
│ ├── product\_scene.zip
│ └── render\_config.json # upload LAST
└── Apps/
└── Render Network/
└── RENDER\_NETWORK/ # output folder
└── completed render outputs

| | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ## Amazon S3 and Google Drive notes The same render\_config.json rules apply to other supported cloud storage providers. Upload the scene file first, wait for it to fully upload, then upload render\_config.json last. ### Amazon S3 For Amazon S3, connect your bucket from the Render Network Cloud Storage settings. After the connection is active, place the scene file and render\_config.json in the configured bucket location or prefix. Use the current Render Network UI as the source of truth for the exact S3 fields and credential requirements. | Internal reviewer note: Confirm the current S3 configuration screen and required IAM permissions before publishing provider-specific S3 instructions. | | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ### Google Drive For Google Drive, connect your Google account from the Render Network Cloud Storage settings. After authorization, use the configured watch folder for scene submissions and the configured output folder for completed outputs. Use the current Render Network UI as the source of truth for exact Drive folder behavior. | Internal reviewer note: Confirm the current Google Drive configuration screen before publishing provider-specific Drive instructions. | | ------------------------------------------------------------------------------------------------------------------------------------- | ## Example submission layouts ### Native ORBX submission |

RENDER\_SUBMISSION/
└── job\_001\_hero/
├── hero\_scene.orbx
└── render\_config.json

| | ------------------------------------------------------------------------------------------------------------ | render\_config.json: |

{
"scene": {
"name": "hero\_scene.orbx"
}
}

| | ---------------------------------------------------------------------- | ### Zip submission |

RENDER\_SUBMISSION/
└── job\_002\_product/
├── product\_scene.zip
└── render\_config.json

| | ----------------------------------------------------------------------------------------------------------------- | render\_config.json: |

{
"scene": {
"name": "product\_scene.zip",
"host\_application": "c4d"
}
}

| | ----------------------------------------------------------------------------------------------------------- | ## Troubleshooting ### The cloud storage connection fails * Confirm the watch folder already exists. * For Dropbox, confirm the watch folder is at the Dropbox root, not inside Apps/Render Network. * Check spelling and capitalization in the configured folder name. * Reconnect the provider if authorization was interrupted. ### The Scene never appears * Confirm render\_config.json was uploaded last. * Confirm the scene.name value exactly matches the scene file name. * Confirm the scene file uses a supported extension: blend, c4d, ocs, orbx, or zip. * For zip files, confirm host\_application is included and valid. * Confirm the scene file finished uploading before the JSON file was added. ### Dropbox is watching the wrong location Use this mental model: |

RENDER\_SUBMISSION = Dropbox root watch folder for upload/ingestion
Apps/Render Network/RENDER\_NETWORK = output folder for completed renders

| | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ## Quick reference | Rule | Details | | --------------------- | ----------------------------------------------------- | | Trigger file | render\_config.json | | Upload order | Scene file and assets first, render\_config.json last | | Supported extensions | blend, c4d, ocs, orbx, zip | | Zip requirement | host\_application must be blender, c4d, or octane | | Dropbox watch folder | Dropbox root, for example /RENDER\_SUBMISSION | | Dropbox output folder | Apps/Render Network/\ | | Scene count | One render\_config.json creates one Scene |
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://know.rendernetwork.com/getting-started/how-to-get-started/uploading-scenes-from-cloud-storage.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.