Redshift standalone (.rs)
Download and install
Log in to Web Manager (web dashboard) at https://app.garagefarm.net and download our renderBeamer Desktop App for you operating system.

Install the renderBeamer app and start it. Once renderBeamer is done with the installation process, you need to choose the default download directory. This path will be used as the main output place for all your renders. Next, just log in using the account ID you received or your account email. Please keep in mind that the app should always be running in the background whenever uploading a project or downloading rendered frames.

Once renderBeamer is installed and you’re logged in, you’ll see the Plugins panel. Plugins installation panel should automatically open after the first renderBeamer startup. You can also open it anytime you need to install additional plugins for your 3D apps.

Please keep in mind that each 3D app (DCC) you use needs to have a plugin installed to properly connect to and render on our farm.
Prepare the scene
In your DCC app, open the scene and export it to the Redshift scene (.rs file).
- Scene files should be saved in .rs format.
- Remember that the filename should contain the frame number preceded by zeros and underscore characters. e.g: scenename_0000.rs (for still image), scenename_0001.rs - scenename_0250.rs (for animation of 250 frames).
- Best practice when exporting a .rs file with all assets is to have all the textures, caches, and other kinds of assets next to the exported scene.
- Scene should be free of missing assets when submitted to the render farm.
Our plugin is available for Windows OS. If you are using a different operating system (like macOS, or Linux), please contact support for details.
Use the plugin - startup & settings overview
When your DCC app is done with exporting the .rs sequence, you can use our plugin directly from your operating system’s file explorer. To do that just browse to the .rs file and right-mouse click on the scene file.

Once the plugin has started, you will see the main plugin panel. The plugin UI for Redshift Standalone is displayed in the setup tab in our renderBeamer app. Here you can check and change your settings before uploading your project to the render farm.

Settings tab
Our plugin automatically detects your settings that have been used in the DDC app render settings, however, you can always make changes here in the plugin before sending the scene to the farm.
- render mode – in our plugin we have a mode called "render as is". This is a common mode that you can use both for still image rendering and for complex animations. The advantage of this mode is that your settings set in the DDC app will be kept and used for the rendering on the farm.
- new project name – by default, the name of the project matches the name of the folder where the .vrscene file is located. You can activate the "new project name" option and change the name of the project according to your preferences. Please note that if you have already uploaded a project and are going to submit the same scene from that project but using modified assets that are named the same as previously, we recommend using this option. In this case, all assets will be uploaded again and you will be sure that you are using (new) modified assets. Otherwise, our plugin may not detect the new assets and thus won't upload them. If you decide to activate this option, please make sure to set a unique project name (other than the default one).
- frame range - the value for this option is set according to the detected exported sequence of .vrscene file. This means that if you exported the sequence for frames from 0 to 450, then this field will be set to: 0to450s1. For still images it will be simply one frame, for example 0.
- override resolution - by default, this option is disabled, which means that the system will use the resolution set in the DDC app (from which a scene was exported to the .rs sequence). If you want to set another resolution, enable this option and put in the final resolution. A value of 0x0 means that the original settings (from an exported scene) will be used.
Assets tab
Our Redshift Standalone plugin automatically checks scenes for missing assets, and if there are any, you can use our integrated asset tracker tool to relink or replace a given asset with a different version of the one you need.
To open the asset tracker, just click the “Assets” tab, then you can inspect all detected assets.

In the asset tracker panel, you can review your asset list. If assets paths and names are correct, all of them should have the green status with “found” info. Otherwise, you can point or relink missing assets by using the "search icon" and relink them one by one.
If there are paths to files in the assets tracker that are not required for proper rendering and you want to skip them, you need to tick the "ignore missing assets" option. This way, our plugin will not force you to select these files and it will not block the upload process.
Upload the project
Once our plugin completes the scene export, your project will be redirected to renderBeamer to be uploaded. In a nutshell, renderBeamer is a standalone uploader/downloader application that works in conjunction with our plugins. Simply put, it takes care of the file transfers.
After the scene has been fully uploaded, the app will show you a window with a direct link to your scene on Web Manager (web dashboard). To continue use the click here to submit job button. If for some reason you closed the window with the link or it didn’t work, don’t worry, you can locate your project in the web dashboard and submit your scene by clicking on the scene file any time (more on that in the next step). You can also copy the link to clipboard and manually paste it into your web browser.

Submit the job (add the job to the render queue)
Now that your project is uploaded you will need to follow the final step - creating and submitting a job to render farm. Web Manager is a home to all your projects and render jobs.
If you followed the link generated earlier by renderBeamer, you will now see the job submission window with several fields and settings. If you didn’t follow the link or it didn’t work, you can do it manually by locating your project in the projects panel, finding the scene file within the project folder (in your folder structure look for the folder called “data”, i.e. Project_name/Scenes/SceneName.rs), and clicking on it to open the job window.

Most render settings are automatically detected and pre-filled based on your scene. Before submitting the job to the render queue, review the options below and make any adjustments required for your specific project.

Advanced mode - located in the top-right corner of the submission window. By default, this mode is disabled to keep the interface simple and focused on the most commonly used settings. Enabling it reveals additional optional settings, including Advanced settings (job dependencies, custom script, custom node version), Retries, and Job node limit, providing greater control over job submission for advanced workflows.

Job name - displays the name that will be assigned to the submitted job. By default, it is generated automatically based on the project structure and scene file name. This farm-side path helps organize and identify jobs submitted to the render farm. The generated name will be visible in the Web Dashboard and can help you easily identify and manage your render jobs.

Output path - here you can find the default save path for rendered frames in the given job. The default output path is generated based on the name of your project and scene. You can customize this path if needed, for example when rendering multiple versions of the same project or when your workflow requires a specific output structure. This option is available in "Advanced mode".
Output file name (without extension) - by default, the output file name is generated based on the name of your scene. If you need a custom naming convention or want to create a unique output name that better fits your pipeline, you can specify your own file name. This option is available in "Advanced mode".
For Redshift standalone (.rs) projects, the "Output file name (without extension)" field is displayed for reference only. It is read-only and cannot be edited..

test/full job - by default, this switch is enabled (set to the "test job" option) for animation ranges containing more than 5 frames in total. This means that our system automatically sets up your scene's range to render every n-th frame. We always recommend performing a test render before proceeding with the final render. This allows you to identify potential errors and estimate costs. If you want to define the test range manually or want to render the full range without prior testing, simply toggle the switch to the "full Job" option.
For more details on the benefits and usage examples of this option, please refer to a separate article.

Frame range - use this field to specify the frame range you want to render. Frame range example for animations: 1to780s1 - this is a sequence of 780 frames in total, and all frames from 1 to 780 will be rendered. The parameter s1 means that every subsequent frame in the given range will be rendered. If you want to perform a test render first, set a higher step value, for example s20. This will render every twentieth frame in the animation range. For example, if you set the range to 1to780s20, the frames 1, 21, 41, 61, 81, 101, ..., 741, 761 will be rendered.
If you only want to render a single frame (still image), enter a single frame number into the field. For example, 1 will render frame number 1.
If you are going to render an animation or a still image, we always recommend that you perform a test before the final rendering:
- For animations, the best way to get a cost estimate is to run a test of the scene on the farm with around 20 frames spread evenly across the range. For example, a frame range 1to200s20 will render every 20th frame as a test and based on that our system will produce a cost estimate for the full render.
- For stills, please render the image in 1/5 resolution or any other smaller resolution. In the case of 1/5 resolution test, the cost of full resolution render will be 25 times bigger than the cost of a test. For example, if you want to render an image in resolution 5000x6000, run a test in 1000x1200 res first. If your test costs $1, then the estimated cost for the full res image should be around $25 (5 x 5 = 25). For a 1/4 test it would be $16 (4 x 4 = 16) and so on.
There's more information about running tests and estimating the cost in our documentation.

Resolution - here you can set the output resolution in pixels. This option is disabled by default in the web dashboard. If you want to change the resolution for your project it is required to resubmit the scene via our plugin. It is impossible to overwrite the resolution at this stage.
If you are going to render a still image in high resolution and your scene does not contain any post-production effects, then it’s recommended to use "Strips" to speed up rendering by using multiple nodes simultaneously (see more info below).

Advanced settings - available after enabling "Advanced mode". This section contains advanced configuration options intended for special workflows and support-assisted setups. In most cases, these settings should be left unchanged unless instructed otherwise by our support team.
- Job dependencies - if you want this job to start rendering only after another job in the queue has finished, you can select that job here. The current job will remain on hold until the selected dependency job is completed.
- Custom script - if your job requires a modified render environment or a custom script prepared by our support team (for example, a custom plugin installation), select the appropriate script from the list.
- Custom node version - if you need a different software setup (e.g. custom software version), put here the value you received from our support. Note that inputting a wrong number may cause errors during rendering.
The options above are intended for advanced use cases and are empty by default. Do not modify them unless instructed to do so by our support team.

Priority - before adding a job to the render queue, you can decide how you want to prioritize it. Depending on the queue and farm traffic, a higher priority may allow your job to quickly acquire nodes to render your project faster. Each priority has a different rate and gives you a different number of nodes - a detailed list can be found here:https://garagefarm.net/pricing

Node groups (preferred hardware) - for Redshift Standalone projects, Custom Setup is selected by default with recommended GPU node groups preselected based on the scene analysis. You can adjust the selection at any time and choose from various GPU and RAM configurations based on your performance and cost preferences.
The full technical specification of nodes can be found here: https://garagefarm.net/pricing#specs

Retries - the value for this option is set to 2 by default. This means that if a rendering process fails or the software crashes, our system will perform two additional rendering attempts. We recommend leaving this option set to default (value 2) as this is the optimal setting to retry rendering in the case of some random 3rd party software errors.
Job node limit - by default, the value for this option is empty and so the nodes are assigned automatically depending on the job priority and nodes availability on the farm. Nevertheless, if you want to limit the number of nodes for the given job, please put here the value of the maximum number of nodes you want to be used during rendering.

Add job as paused - if you tick this option and then submit your job, it will be added with the status “paused”. This means that it will not start rendering automatically. It is useful to use this option if you intend to add the job to the queue, but you do not intend to render it at the moment. After adding a "paused" job, you can resume it at any time by selecting the "resume job" option (right-click on the job).

Back - if you do not want to add the current job to the render queue or you want to reset your settings and add the scene again, you can use this option. The submission window with the settings for the given job will be closed and all changes will be cancelled.
Submit - when you press this button, the system will immediately add the job to the render queue. Please remember to check all settings before submitting a job!
Monitor render progress
After giving your render settings a final check and choosing your preferred priority, hit Submit to add your job to the render queue. If you’re a first-time user, you will have received $25 worth of credit to test out our service. The credits should be enough to run a few test jobs and familiarize you with the service.
You can right-click on the job to get additional options: change priority, pause job, kill job, and archive job.
The estimate is based on the currently finished frames and is approximated at that point. Rendering a test as prompted in the plugin (using a step i.e. 1to100s10) is highly recommended for more accurate estimates and detecting potential errors.

Once the job starts rendering, you can track its overall progress directly from the project list. Each job entry shows the frame range being rendered, the number of completed frames, and the current completion percentage.
For more detailed information, expand the job row and open the Active Frames section to monitor the progress of individual frames in real time.

Job details are available directly within the project list. By default, all jobs are collapsed. To view additional information, select a job and expand its row. Each job can be expanded independently to display detailed information and rendering progress.
ACTIVE FRAMES - displays frames that are currently being rendered. Completed frames are automatically moved to the DONE FRAMES section.
DONE FRAMES - contains all completed frames. Here, you can review basic information about each rendered frame, such as render time and cost. Each frame row can also be expanded to access additional details, including information about the render node used, associated subjobs, and execution logs.

Right-click any frame in the ACTIVE FRAMES section (after selecting a job and expanding its row) to access the real-time render log from the node currently rendering that frame.
Please note that after a job completes, the ACTIVE FRAMES section will no longer contain any entries. All rendered frames are automatically moved to the DONE FRAMES section.
Download and review frames
Each frame completed rendering is downloaded automatically to your local drive to a directory you selected in the renderBeamer application. If you’re unsure where your download folder is located, you can double-check it or change it in renderBeamer’s settings (click on the cogwheel). Also, ensure you have auto download turned on to get the frames downloaded as soon as they are available. If this box is unchecked, you will have to click on each job in Beamer's "downloads" tab, and manually download the frames.

If you prefer more control over what to download and when you can also download your frames manually. To do that, just turn off the auto download switch in renderBeamer settings and go to the “downloads” tab. Next, select the desired render output using a checkbox, and click the download button.

This workflow will download all rendered frames for the selected job or jobs. However, renderBeamer also gives you an option to download individual frames. You need to use the list files function under RMB to do that.

Once files for the selected job are listed, just roll down the list and select the files you’d like to download using checkboxes. Next, use the same download button.

Once your frames are downloaded, you can use the “open directory” option under RMB to open the folder where frames are saved.
Please ensure you keep renderBeamer running whenever you have jobs rendering to get the frames downloaded immediately. It may happen, however, that your frames aren’t downloading at the given moment. It’s likely because our application syncs the files in 15-minute cycles, and it is currently in between the cycles. You can click refresh to force the application to sync.
Purchase credits
You’ll need to charge your account to continue using the service once all trial credits are used up. Please note that when your balance goes below $0, you won’t be able to download rendered frames or start new render jobs.
Credits can be purchased in the Purchase panel available in the Web Dashboard. The default payment method is credit card payment, but you can also use alternative payment methods supporting debit/credit cards, Revolut Pay, and Google Pay. If you prefer paying via bank transfer, detailed wire transfer instructions are also available in the Purchase panel.
You can access the Purchase panel by clicking the $ icon in the main navigation bar next to your account balance, or by selecting “Top up balance” from the Account menu in the top-right corner of the dashboard.
If your rendering needs are high or you plan to render regularly, please make sure to check out our volume discounts.

In case your account balance goes below 0, any current jobs will be paused - all frames/strips that were in the middle of rendering will be completed but any subsequent frames/strips will not start rendering. To download rendered frames, your account balance must be positive or equal to $0.
Contact us anytime
You can talk to the GarageFarm.NET’s tech team any time of the day, any day of the week. We’re here to help you get started, answer your questions, and assist you in any way. Don’t hesitate to give us a shout.
You can contact us through our live chat accessible in the web dashboard or our desktop app when you log in to your account or message us here through the guest chat.
We also recommend checking out our FAQ page which answers most of the questions new users have.
Register Now and Get $50 FREE Credits!
Frequently asked questions


