설정

Blender에서 Drop & Render을(를) 사용하는 방법에 관한 종합 가이드입니다.

Download this guide, open it as markdown or explore our other manuals using the buttons above.

Use (Ctrl or CMD) + K to activate fuzzy search.

Why Drop & Render

Drop & Render is a premiere managed render farm solution designed with both freelancers and studios in mind. You send us projects that take hours to render, and we'll have them ready for you in minutes.

  • Seamless integration: Our add-on integrates directly into Blender, Cinema 4D and Houdini.
  • Managed servers: We bring the hardware, you bring the project. No need to maintain your own infrastructure or set up any virtual environments.
  • Plug and play: We take your projects as they are. Drop & Render is built around your projects, not the other way around.
  • Outputs where you expect: Downloads go straight to your project folder. Just like rendering locally.
  • Dedicated support: You can always reach real people with long term experience in 3D rendering for all of our supported platforms.

System requirements

The Drop & Render Link supports Windows 10 and newer, macOS 12 and newer and 64-bit Linux. All computation happens on our farm, so your workstation only needs to run the Blender version used by your project.

Setup & installation

To use Drop & Render, first create an account. Setup opens automatically after registration. Install and open the Drop & Render Link, then choose Blender from the detected applications to install the add-on. You can return to Dashboard > Plugins later to manage it.

Core concepts

Distribution of work

Our datacenter is filled with top-of-the-line machines optimized for 3D rendering. When you submit a job we will split it many smaller chunk, and give each to an independent machine. This means that your job can be rendered by 50+ machines all at the same time.

Slices & slice numbers

Optimize your render with a Custom Slice Number

Slices are the chunks we split your project into, and the number of frames that are processed by each chunk is its "slice number". Rendering multiple frames in one slice means you reduce the number of times Blender has to initialize the project. The slice number defaults to 1, but this is not always optimal.

Each job has a startup overhead of 1-2 minutes due to Blender itself. For a render that takes 30 seconds per frame on our machines, this effectively means that with a slice number of 1, each machine will charge you for up to 2 and a half minutes, even though your render only took up 20% of that time.

Increasing the slice number helps reduce this extra cost - by rendering more frames per slice you reduce the number of startups. In the above case, if your render has 10 total frames and you set the slice number to 10, you'll end up doing 5 minutes of rendering for each 2 minutes of startup. This means your total render time goes from ~25 minutes (2.5 minutes * 10 frames) to only 7 minutes (~72% faster & cheaper) (2 minutes + 30 seconds * 10 frames) executed concurrently with 10 machines working at once.

Tip: Aim for approximately 20 minutes of total work per slice (startup + rendering).

Queues and priority

Understanding render priorities

Machines are assigned to slices based on our priority system. We have 3 priority levels, Sapphire (lowest), Emerald (medium) and Diamond (highest). The higher your priority, the further ahead your slices go in the global queue and thus the faster your job will complete.

Each priority level carries a multiplier of cost, with Sapphire standing as the base price. However, the extra costs apply only when the higher priority made a difference. If there are machines immediately available, you will only be charged Sapphire costs even if you choose the Diamond priority.

Tip: For production deadlines, we recommend using the Emerald or Diamond priorities. Use Sapphire when the deadline isn't strict, such as overnight renders or other non-urgent work.

The Drop & Render Link

The Drop & Render Link runs in the background and connects Blender to the render farm. It keeps the add-on up to date, reuses files already on the farm, uploads new and changed files and automatically delivers completed frames. Monitor and manage jobs from the web dashboard. Once your job is uploaded you can close Blender, render locally or shut down the workstation; rendering continues on the farm.

Note: Automatic delivery works while the Drop & Render Link is open. If it is closed, delivery resumes the next time you open it.

The sync system

Drop & Render uses an intelligent syncing system with hash-based file comparisons and aggressive de-duplication. When you first upload a file we store a hash of it, which we can then check against any future uploads. If the local and remote hashes match it means the file hasn't changed, so it doesn't need to be re-uploaded. This drastically reduces upload costs when re-rendering alterations of the same project.

Assets uploaded by team members are automatically available for everyone in the studio. They are stored for 7 days after their last usage. We allocate 5TB of storage per studio account by default. More is available on request through our support system.

The download system

Completed frames return to the output folder selected in Blender while the Drop & Render Link is open. Outputs also remain available for seven days; open the render in the web dashboard to manually download its complete output or selected slices.

The Drop & Render Blender add-on

Getting started

Opening the add-on

Once installed, you can find the Drop & Render add-on in Blender by:

  1. Press N in the 3D Viewport to open the sidebar
  2. Look for the Drop & Render tab

This will open the add-on interface where you can configure your render settings and submit jobs to the farm.

Check scene system

Before submitting your project, the add-on automatically runs a scene check to ensure everything is set up correctly. This check performs over 150 intelligent project verifications, including:

  • Your project file is saved
  • Output paths are configured
  • All textures and assets are accessible
  • Render settings are valid
  • Camera is set
  • Output format is supported
  • The add-ons your scene needs are on the farm (see Add-ons on the farm)
  • Your scene is compatible with our render farm

If any issues are detected, the add-on shows clear warnings with instructions on how to fix them. A problem the farm can't render with, such as a missing camera or output path, stops the submit: the add-on names the check that failed, so you can fix it and submit again. This prevents failed renders and saves you time and credits.

You can manually run a scene check at any time by clicking the "Check Scene" button in the add-on interface.

Supported render engines

Drop & Render supports all major Blender render engines:

  • Cycles - Blender's built-in physically based path tracer (CPU/GPU)
  • EEVEE - Blender's built-in real-time renderer (Blender 4.2 and newer)
  • Redshift - GPU-accelerated production renderer
  • Octane - Unbiased GPU renderer
  • LuxCore - Open-source physically based renderer
  • Workbench - Blender's built-in viewport renderer

The add-on automatically detects which render engine you're using based on your scene settings. If your scene renders with an engine from an add-on the farm doesn't have, the scene check shows Render engine ... isn't on the farm before you submit.

Note: EEVEE renders natively on the farm for projects saved in Blender 4.2 or newer. Projects from older Blender versions that use EEVEE are rendered with Cycles instead, so the result will look different from your local render. Open and save the project in Blender 4.2 or newer to keep the EEVEE look.

Blender builds

Besides the official Blender releases, the farm also supports these Blender builds:

  • Goo Engine - The NPR and anime-focused Blender build
  • E-Cycles - The speed-optimized Cycles build

The add-on detects the build you're running and the farm renders with the matching version.

Add-on & version matching

Drop & Render automatically detects and matches your local add-on versions to ensure renders execute exactly as they would on your machine. This includes:

  • Blender version - Automatically matched to your local installation (supports 2.80+)
  • Render engine version - Matched to your installed Redshift, Octane, LuxCore, etc.
  • Third-party add-ons - Flip Fluids, Botaniq, Advanced Ocean Modifier and other supported add-ons

The add-on scans your Blender installation and uploads version information along with your project. Our farm then activates the same versions you're using locally, ensuring consistent results. When the farm doesn't have your exact version of an add-on, it uses the nearest version it has.

Note: If you need to override the automatic version detection, you can manually specify versions in the Advanced tab.

Add-ons on the farm

Add-ons the farm doesn't have

The scene check looks at which of your enabled add-ons the scene actually needs to render: add-ons whose render engine it uses, whose nodes are in the file, whose functions drivers call, or that run on every frame or render. If the farm doesn't have one of those, the check lists it with the reason. Add-ons that only add tools to Blender's interface, such as importers, render the same without them and aren't listed.

The check also warns when a driver calls a function from an add-on the farm doesn't have. On the farm such a driver evaluates to 0. Bake or apply what it creates, upload the add-on with the job, or contact support to have the add-on added to the farm.

Extensions from extensions.blender.org

Extensions from extensions.blender.org that your scene needs are installed on the farm automatically, in the version you use. You don't need to do anything: the farm keeps its own copy of each extension that has been requested.

Note: An extension no job has used before is copied to the farm within about 15 minutes. The first job that needs it may start rendering before it's there; resubmit the frames that were rendered without it.

Uploading your own add-ons

Add-ons the farm doesn't have can travel with your job. In the Advanced tab, tick Upload add-ons the farm lacks. The add-on lists each add-on it would upload, with a tick you can clear, and says why it can't upload one:

  • macOS/Linux only - the add-on has no Windows version, and the farm runs Windows
  • larger than 200 MB
  • files not found on this computer

The farm installs uploaded add-ons for your job only, inside the isolated environment that renders your scene, which is cleared after every slice. They are never shared with other jobs or other customers.

Uploads need a Blender version that renders in that isolated environment: Blender 3.0 to 5.4, and the OctaneBlender builds from 30.2 to 30.11. The add-on tells you when your job uses another version, such as Goo Engine.

Note: Add-ons that need their own licence or activation may not run on the farm, because the farm can't sign in to the add-on's licence server. Contact support before relying on one in a deadline job.

Tile rendering

Tile rendering splits a single frame into multiple rectangular regions (tiles), with each tile rendered independently by different machines. This is particularly useful for:

  • High-resolution stills - Render 4K, 8K or larger images much faster
  • Heavy scenes - Distribute memory and processing load across multiple machines
  • Final frames - Accelerate hero frames that need maximum quality

To enable tile rendering:

  1. Tick Tile Render at the top of the add-on
  2. The add-on will automatically calculate optimal tile divisions based on your resolution
  3. Submit your job as normal

The tiles are automatically stitched together on our farm and delivered as a complete frame.

Tip: Tile rendering is for a single frame. For animations, regular frame-based distribution is more efficient.

Tile rendering with Octane

Octane doesn't use Blender's render border, so each Octane tile renders through a camera of its own that sees only its part of the frame. The scene check shows Each tile renders through its own camera when this is set up.

  • Denoiser: with the Octane denoiser on, every tile renders 16 px larger on each side and the extra border is cut off before stitching, so the denoiser can see past the tile's edge. The scene check shows Denoiser: tiles overlap 16 px.
  • Bloom, glare and vignetting are worked out over the whole image, so each tile would get its own and the tile edges would show. The scene check stops a tile job that uses them; click Turn off to switch them off on the camera, and add them in compositing instead.
  • Cameras: panoramic cameras and Octane's Baking, OSL and Realistic lens camera types can't be split into tiles.

Advanced tab

The Advanced tab contains additional options for fine-tuning your render job. Most users won't need these settings, but they're available for specific use cases:

Custom frame list

Submit a custom frame range to the farm

Override the frame range with a specific list of frames. Use commas and dashes:

  • 1,5,10 - Renders only frames 1, 5, and 10
  • 1-10,20,30-40 - Renders frames 1 through 10, frame 20, and frames 30 through 40

This is useful for re-rendering specific frames or creating custom sequences.

Custom Blender version

Override the automatic version detection and specify exactly which Blender version to use on the farm.

Only change this if you need a specific version different from your local installation.

Custom slice number

Override the automatic slice calculation and manually set how many frames are rendered per slice. See the Slices & slice numbers section for guidance on choosing the right value.

Tip: Start with the automatic settings. Only use custom values if you have specific performance requirements or if advised by our support team.

Upload add-ons the farm lacks

Sends the add-ons your scene needs and the farm doesn't have along with the job. See Uploading your own add-ons.

Other advanced options

The Advanced tab contains additional settings reserved for troubleshooting and support purposes. These are typically only used when working with our support team to resolve specific issues. If you encounter problems with your renders, our support team may ask you to adjust these settings.

Flamenco

Studios that run Flamenco, the render manager from the Blender Studio, can send Flamenco jobs to Drop & Render. Artists keep submitting from Blender with the Flamenco add-on and pick Drop & Render as the job type. The job renders on our farm, the frames arrive in the job's render output folder on your shared storage and Flamenco shows the progress. See the Flamenco render farm page for an overview.

Setting it up

Only the computer that runs your Flamenco Manager needs Drop & Render software. Run the Manager on that computer under the same user account as the Link.

  1. Install the Drop & Render Link on that computer and sign in with a Drop & Render login reserved for it.
  2. Install the Drop & Render add-on 3.21 or newer in Blender on that computer, from the plugins page.
  3. Open a new terminal and run dar install flamenco. On macOS, run '/Applications/Drop & Render Link.app/Contents/MacOS/dar' install flamenco, and on Linux ~/.local/share/dropandrender/dar install flamenco. The Link adds its Flamenco extension, downloads the Flamenco worker that matches your Manager and adds the Drop & Render job type to the Manager.
  4. If Flamenco Manager was already running, restart it once.

In Blender, open Output Properties > Flamenco, click Refresh from Manager, choose Drop & Render as the job type, set the render output root (an empty folder for each new job) and submit. Artists who have our add-on also pick a Queue there. Run dar flamenco status to see whether everything is ready; the setup guide covers each step and the messages it may show.

Good to know

  • Jobs use the credits of the account signed in to the Link. Flamenco has no login, so keep your Flamenco Manager on your studio network.
  • The worker handles one Drop & Render job at a time; other jobs wait in the Flamenco queue.
  • Jobs render with the Blender version installed on the computer that runs the Link.
  • Cancel a render that is already on the farm from the dashboard.
  • To stop sending Flamenco jobs, run dar uninstall flamenco.

No results found. Check out our other manuals.