How to render C4D projects and Recommendation
Here’s the summary of the steps to use Cinema 4D and SuperRenders:
- Log into the SuperRenders website.
- In the web manager interface, click on the “SRF Space” button.
- Next, click on the button that says “Upload file or folder” to upload your Cinema 4D project.
- After uploading it to the system, open the file and click on Scenes to analyze it.
- Select the software version and the render engine version, then click on Analyze Scene.
- The system will analyze the file and provide any warnings or errors, if any. If there are no errors, click on the “Start render job” button.
- Once the render job is complete, click on “Download render output”.
- Right-click on the newly appeared folder and select “Download” to save the “render output” to your computer.
Read for more detailed instruction:
Click here
Watch the video below for a detailed tutorial on rendering Cinema4D on SuperRenders.
Recommendation for C4D render
General recommendation for rendering C4D project in Super Renders Farm.
Sometime in your rendering, it is normal that something could go wrong, but if you follow these simple rules you increase your odds of avoiding issues by quite a margin:
Scene file – should be saved in version 2026
XRefs & additional objects – should be merged into one scene file.
**Textures **– all textures should be copied do \tex\ folder is scene project directory. All files should be localized to this path.
Animation files (avi/mp4/etc) are not a good option for animated textures, also .mov files cannot be used. Please make a frame sequence (jpg\png or so) and connect as an image sequence. If there are textures from various plugins (like Greyscale Gorillas packs) – they should be saved with the scene (in \tex\ folder)
GI files – if GI is used, should be prepared with correct setup for multiple machines rendering with all saving options OFF.
If GI cache is done on your side – please copy all needed GI maps to the \illu\ folder in scene project directory and re-link GI paths in Render settings.
Multiple cameras – we can render multiple camera scenes with our plugin. If you got some untypical setup (like changing cameras over the timeline) – you should prepare your scene with a stage tag.
Frame range & FPS setup – should be set with covering values.
Deformers, effectors, dynamics & particles – each of these features should be checked for caching purposes before sending the scene. We are using multiple machines to render and some of them may render differently without a cache file.
**Multipass & output **– we are supporting both outputs. Paths to renders should be set in the same way as rendering on your local machine.
Scene name, output paths should not contain any untypical characters like / \ ” % # ? or any similar too
Updated on: 24/09/2026
Thank you!