SketchUp
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 project - page render mode (single & multi page stills)
At first, you’ll need to prepare your SketchUp project for .vrscene export. Our SketchUp plugin works as an automated .vrscene exporter, so we require everything to have been prepared before using it. Preparation should be done in accordance with the intended renderer mode. Preparation process should be done directly in SketchUp settings, and V-Ray render options. This step is crucial because of the .vrscene export procedure.
You can use our plugin with 3 modes - page render (with multi page option), page animation , and frames render.

Page render mode - single page rendering
This mode is designed to render single or multiple SketchUp pages as still shots. With page render you can choose to render still shots from your current project pages. Below you can find directions on how to prepare your scene for the .vrscene export procedure used by our plugin.
Head to V-Ray settings and make sure you do the following:
- set the right resolution
- set the file output path
- turn off the Animation switch (for single page render) - for multi page render, turn on the Animation switch
- select your GI caching (Single frame to cache it on our side or From File to use your own cache)
- select all your desired render outputs under Render Elements

Now your scene should be correctly set up and ready to go. Please make sure you save your scene before going to the next step. Next, just run renderBeamer from the extensions menu.
Page render mode should be used only to render Sketchup pages as still shots.
We will divide your still image into several parts called strips and will distribute them across multiple nodes. You can select the number of strips you want to render with (1 strip = 1 node, usually the higher number means the image will complete sooner, with some exceptions). An important thing to note is that the image resolution height must be divisible by the number of strips you choose. For example, 1920x1080 can be divided by 10 and thus the image will be split into 10 strips.
Our plugin reads your GI settings and just forwards them to the UI. We strongly suggest to always leave the “bake” switch (next to GI engines) on. Otherwise, you can expect visible connection lines between rendered strips, as every render node will calculate its “own” GI files. Using the bake switch with the “off” setting is only recommended when rendering scenes with setups like BR, BR+BR or with pre-cached GI maps.

To continue, just select the number of strips, choose the strips orientation (horizontal or vertical), double check the bake switch box (this means we will cache the GI), and select the pages you want to render. Now, your project is fully set up and ready to be sent to the farm.
Page render mode - multi page rendering
If you have multiple pages, and want to render them as still images, first, you need to make sure you have your SketchUp Animation settings properly configured. Go to View > Animation > Settings and enable Scene Transitions and input 1 second in the time field just like in the image below.

Now head to V-Ray settings and make sure you do the following:
- set the right resolution
- set file output path
- turn on the Animation switch
- use Frame Range in Time Segment and click Get Animation Range to adjust the frame range
- select your GI caching (Single frame to cache it on our side or From File to use your own cache)
- select all your desired render outputs under Render Elements

Now your scene should be correctly set up and ready to go. Next, just run renderBeamer from the extensions menu. Plugin usage is exactly the same as for single page rendering.
Prepare the project - page animation mode (animated pages)
This mode should be used for fully animated camera shots. First, you need to make sure you have your SketchUp Animation settings properly configured. Go to View > Animation > Settings, enable Scene Transitions and input 1 second in the time field. Sketchup operates in seconds, not frames. By default, V-Ray 3.x sets 30 frames per second. That means if you set the Scene Transition time to 1 second - you will receive 30 frames rendered between Page 1 -> Page 2. If you set 2 seconds for scene transition, you will get 60 frames rendered between your SketchUp pages.
Now head to V-Ray settings and make sure you do the following:
- set the right resolution
- set file output path
- turn on the Animation switch
- use Entire Animation for Time Segment
- select your GI caching (Single frame to cache it on our side or From File to use your own cache)
- select all your desired render outputs under Render Elements

Now your scene should be prepared correctly and ready to go. Please make sure you save your scene before going to the next step. Next, just run renderBeamer from the extensions menu.
Page animation mode should be used only to render animated projects.
Another Important thing to note is that by default SketchUp renders 30 frames per page. You can adjust this value in SketchUp’s settings View > Animation > Settings using the time field. Next, you need to select your page range (the starting Page and the ending Page), set baking step (which defines the step for caching GI, i.e. 10 = every 10th frame), and check the store direct light checkbox. Now, your project is fully set up and ready to send to the farm.

Irradiance Map (with incremental add to current map option for GI caching, and from file for rendering) + Light Cache (in flythrough mode for GI caching). If you are using any other GI setup, please use Frames render mode instead.
Prepare the project - frames animation mode (advanced frames mode)
Frames animation mode is designed for more advanced users who are familiar with operating on frames - not SketchUp pages. If you're not sure about the workflow with frames & SketchUp please use Page render or Page animation modes instead.
With frames animation you can choose which exact frames you want to render, or which frame needs to be rendered as still shots. By default, SketchUp renders scenes with 30 frames per second (FPS). That means if your project starts from page 1 and ends on page 8 - you will have 210 frames to render (starting from frame 0). Frames mode allows you to operate in two combined modes - range rendering and still image rendering.

To use Frames render with range rendering just put desired render range in “Frame range” field. You can also set a render step (for testing purposes) by changing the “s” value at the end of frame range. For example, setting render range to 0to210s10 will render every 10th frame. Please keep in mind that our plugin will not allow you to render a range greater than what is set in the project. As for GI settings, they are forwarded from your V-Ray render setup and reflected on the plugin UI. By default, the bake switch is on so that your scene can be GI cached before rendering.
To use Frames render mode with distributed still shot rendering you need to put a single frame value in “Frame range” field. Still shot mode (similar to “Page render”) works only with single frames rendering. That means you can select frames in your project render range and just forward it to the farm as one still shot. By default, the strips on/off switch will be always ON when using single frame render range. Next, you can select how many strips you want to use. More strips usually means faster rendering.
Please keep in mind that your resolution needs to be divisible by an even number!
Good example - 3840x2160 - you can easily use 10, 20, or 30 strips with this resolution
Bad example - 3843x2169 - it’s much harder to divide this resolution and so only a few strips will be available
sRGB switch and SketchUp while processing the scene
After you click SEND TO FARM please don’t perform any operations in SketchUp while the plugin is exporting the scene. It may seem like the program is hanging but, in fact, the V-Ray exporter is working in the background. It may take a minute or longer depending on the size and complexity of your scene. With bigger projects (like 500MB+ and lots of geometry, additional assets and so on) .vrscene export can take even 10 minutes or longer. After that, you can continue using SketchUp for your work or close it since we won’t be needing it anymore.
Our plugin will remind you about checking the sRGB output settings you have used in your scene. It’s crucial to render the scene with the same setup as on your local machine. Open the V-Ray frame buffer and check your color space settings at the bottom of the window. By default, the sRGB switch is always on. You will also be able to set sRGB ON or OFF later, after uploading the scene

You should always run a test job first prior to rendering a full range animation or full resolution still image to check for potential issues and to get an estimated job cost. For animations, try to render a shorter range or a single page first. For still images, you should render a smaller resolution job (i.e. ⅕ res). This is a very important step to follow, and will help you fully test the service without potentially overspending your credits. To get a preliminary cost estimation, use our Cost Calculator. While this is only a rough number and shouldn’t replace the actual testing, it’s a quick way to get a cost and render time estimate for animations (it doesn’t work for stills).
You can read more about the importance of testing and ways to estimate the render cost and time in our FAQ.
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.

If you close the submission window using the close button, you do not need to prepare or upload the scene again. To reopen the submission window, right-click the prepared item and select submit using web manager. The previously generated submission link will be displayed again.
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 file browser under the projects tab, finding the scene file within the project folder (in your folder structure look for the folder called “data”, i.e. Project_name/data/SceneName.vrscene), 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 Output Path, Output File Name, Advanced Settings, 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 V-Ray Scene standalone (.vrscene) projects, the "Output path" and "Output file name (without extension)" fields are displayed for reference only. They cannot be edited and are intended to help verify the output location and file name.

Version - for V-Ray Scene standalone (.vrscene) projects, this field shows the source DCC application from which the .vrscene file was exported (e.g. 3ds Max, SketchUp, Rhino). This value is provided for reference only, displayed as read-only, and cannot be changed.
Extension - a format for the output file is the same as in your scene settings. However, if you want to change the extension to a different one, you can choose from the available options, i.e: PNG, EXR, JPEG, SGI, TIF, TGA, JPG, VRIMG, HDR.
.png)
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).

Frames per execution - this option is only available for animations. By default, the value for FPE is set to 1 for projects rendered on CPU. This means that each frame will be rendered as a new execution (a separate task), in other words, the scene will be loaded on each node every time a new frame starts. In the case of projects rendered on GPU, the value for FPE is set to 5 by default. So it means that 5 frames will be rendered in a row on one node.
The FPE (Frames Per Execution) option allows you to render several frames (the value you put in) in a row without the need to reload the scene on a render node, and potentially may improve rendering efficiency. If your scene has a long loading time but a short rendering time, you can set FPE to a higher value (for example 4). If the loading time is not long but the rendering time is long, leave the default value or set it to 1.
Detailed information on the use and examples of the FPE option in practice can be found in our dedicated guide: https://garagefarm.net/documentation/how-to-use-and-optimize-frame-per-execution-fpe

Use sRGB - enables sRGB color space for the rendered output.

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) - by default, the system sets the preferred hardware to nodes with 62GB RAM. Depending on the rendering device you choose to render the job with (CPU or GPU), you can also switch the node group button to custom setup and select the particular group of nodes either based on RAM or device:


The full technical specification of nodes can be found here: https://garagefarm.net/pricing#specs
If you know that your scene requires more than 62GB RAM, then when adding a job to the queue select the group with 121 GB RAM or more to render more optimally only on nodes that have more RAM.

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 get you familiar 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 an approximation 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 for detecting potential errors.

When the job has started rendering, you can check the real-time progress of currently processed frames. To do that, just select the render job from the main project list and then click the arrow on the top right side to open the progress panel.

The Progress Panel (the panel on the right side of the screen) will show its content only when any of the jobs is selected. The panel is divided into 3 sections.
Active frames - it shows currently rendering frames. When a frame finishes, it is moved to the second section Done frames. If you select any frame in the Done frames list, you can then access the render output process log in the bottom section called Process results.
When you’re in the Progress Panel and right click on any of the currently rendering frames in the “Active frames” section, you can access the real-time render log from our nodes.
Please keep in mind that if a job has finished rendering, the frames list in the “Active frames” section will be empty because all frames are already rendered and the list is moved to “Done frames”.

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


