KeyShot Animation and Turntable Rendering on Cloud GPU

A KeyShot animation render involves rendering many individual frames, so total render time depends on frame count and rendering speed per frame. GPU Mode can accelerate animation rendering when the scene fits within available VRAM. KeyShot Studio 2025.2 supports NVIDIA Maxwell or newer GPUs, recommends Turing or later, and ideally requires at least 8GB of VRAM with driver 572.16 or newer. However, RTX 50-series Blackwell GPUs require KeyShot Studio 2025.3 or a later compatible version. If GPU memory runs out, KeyShot may revert to CPU rendering. For cloud workflows, exporting individual EXR or PNG frames makes it easier to recover from interrupted jobs. You can use a compatible render farm or rent a remote GPU workstation to run KeyShot yourself. Check software compatibility and licensing requirements before choosing either option.

Source: KeyShot

Consider a simple KeyShot turntable: one full 360-degree rotation over 10 seconds at 30 fps produces 300 frames. If each frame takes two minutes to render, the entire animation would require approximately 10 hours on one machine rendering frames sequentially. This is an illustrative calculation, not a measured benchmark. It shows why even a short product animation can become time-consuming and why artists may consider cloud rendering when deadlines are tight.

Why Turntables Eat More Time Than You Expect

A KeyShot turntable may look simple, but rendering hundreds of frames can take hours. Total render time is approximately the number of frames multiplied by the average render time per frame. Once the animation duration and frame rate are approved, reducing the frame count may no longer be practical.

The remaining opportunity is to reduce the workload per frame. Important factors include CPU versus GPU rendering, sample count, output resolution, and material complexity. Higher sample counts and resolutions generally increase render time, while complex materials and lighting can require additional processing.

For a detailed comparison of the two rendering engines, see our KeyShot CPU vs GPU guide.

GPU Mode for Animation: What It Needs

GPU Mode can accelerate a KeyShot animation render, provided the scene fits within the available GPU memory and the hardware is supported. KeyShot Studio 2025.2 requires NVIDIA Maxwell architecture or newer, recommends Turing or later, and ideally at least 8GB of VRAM with driver 572.16 or newer. AMD GPU Mode support starts with RDNA 3, including Radeon RX 7600 and newer, with driver 23.30 or later.

Check your KeyShot version before choosing a cloud GPU. Although the 2025.2 requirements list RTX 50-series cards, KeyShot notes that Blackwell GPUs need a CUDA update included in Studio 2025.3. Therefore, an RTX 5090 should not be assumed compatible with GPU Mode in 2025.2.

VRAM is another important limitation. KeyShot’s GPU Mode documentation states that the software reverts to CPU rendering when GPU memory runs out. This can significantly affect performance. Use the Heads Up Display in the Real-time View to monitor GPU memory usage before starting a long animation.

Textures can consume substantial VRAM. According to KeyShot’s documentation, a single 4K RGBA texture requires approximately 64MB at 8-bit depth or 256MB at 32-bit depth. Multiple high-resolution texture maps can increase memory requirements quickly.

GPU Mode also has geometry limitations. NURBS-only objects are ignored, some curve geometry may render incorrectly or disappear, and ZBrush ZSpheres are unsupported. Check the warning icon in the Real-time View for affected scene elements before rendering.

KeyShot supports multiple GPUs for rendering performance, but their VRAM does not automatically combine. NVIDIA memory scaling requires a supported NVLink configuration. RTX 4090 and RTX 5090 cards do not support NVLink, so adding more of these GPUs does not create one shared VRAM pool.

Recommended Animation Export Settings for Cloud Rendering

For cloud-based KeyShot animation rendering, exporting individual frames offers more control over long jobs and makes interrupted renders easier to recover. KeyShot Studio supports frame output, specific frame ranges, and several image formats.

Setting	Recommended option	Why it matters
Output type	Image sequence	Keeps successfully saved frames available, allowing missing frames to be rendered separately
Frame format	EXR 16-bit half-precision or PNG	EXR for workflows requiring floating-point image data; PNG for simpler image delivery
Time range	Specific frame range	Divide a long animation into sections that can be rendered separately
Video output	Assemble afterward	Allows you to inspect the frames before encoding the final video
Render engine	GPU if supported and within VRAM limits	Check GPU compatibility and memory usage before submitting the job

KeyShot also documents a specific video creation issue involving Switch Events and image Name Templates. If your animation uses Switch Events, avoid Name Template parameters that change during those events, such as the active Studio, Camera, Model Set, or Environment.

Building a Turntable That Loops Cleanly

KeyShot’s Animation Wizard provides a guided way to create product animations, including rotation-based turntables. Before rendering, decide whether the model or camera should rotate.

Rotating the camera around a stationary product changes the viewing angle while keeping the product fixed relative to its environment. Rotating the model changes its orientation relative to the lighting environment, which can produce different reflection patterns. Test both approaches to find the result that suits your product.

For a seamless loop, check whether the last frame duplicates the first frame’s orientation. If both are included in the final video, the repeated position may create a brief pause at the loop boundary. Review a short preview before finalizing the animation.

As a practical quality check, render 10 to 20 frames evenly distributed around the rotation. This can reveal unwanted reflections, lighting changes, or material issues before you commit to the full sequence.

Job-Based Farm or Remote Machine?

A job-based render farm is convenient when your KeyShot turntable is finalized. You submit the project, and the service handles rendering without requiring you to manage a remote workstation. Confirm that the farm supports your KeyShot version, render engine, and required project features before submitting.

A remote GPU machine offers more control when you are still adjusting materials, lighting, or animation settings. You can install a compatible KeyShot version, test different configurations, and render the final sequence within your own working environment.

KeyShot also offers Network Rendering, which distributes rendering tasks across multiple workers. For animations, KeyShot normally divides the job into individual frames. Its bands and regions methods are primarily used for still-image rendering. Network Rendering uses a Manager and Worker architecture and can be configured with suitable network infrastructure, including cloud-based machines, subject to compatibility and licensing requirements.

Whichever approach you choose, confirm the licensing requirements before starting. Using a remote workstation or a Network Rendering setup may involve different activation and licensing arrangements.

The License Step People Forget

Before moving a KeyShot animation render to the cloud, check whether your license is node-locked, floating, or subscription-based. The transfer process differs by license type, and KeyShot’s standard license transfer instructions specifically apply to node-locked licenses.

For a supported node-locked license, follow these steps:

1. On your current computer, open KeyShot and select Help > Deactivate License. Wait for the successful deactivation confirmation.
2. On the remote machine, install KeyShot and select Activate your license. Enter your registration information and serial code.
3. After rendering, deactivate the license on the remote machine and reactivate it on your original computer.

Both machines need an internet connection for this transfer process. If you use a subscription license, KeyShot Studio 2025.2 and later provide account-based activation, so the same deactivate-and-reactivate procedure may not apply. Floating licenses also have separate requirements.

Important: Never intentionally deactivate a KeyShot license that has reached its End of Life. KeyShot warns that reactivation may no longer be possible.

Render KeyShot Animations on iRender GPU Cloud

If your KeyShot turntable fits within GPU memory but takes too long on your local workstation, iRender offers Windows GPU cloud machines with RTX 4090 GPUs featuring 24GB VRAM or RTX 5090 GPUs featuring 32GB VRAM. You can install a compatible KeyShot version, select GPU Mode, and render the animation on a remote workstation. Multi-GPU configurations are also available for supported workloads, although VRAM does not automatically combine across cards.

One limitation is that iRender provides the hardware, not the KeyShot license. You must arrange your own valid license and confirm that it permits remote use. If you need to transfer a node-locked license, plan the activation process before rendering and return it to your local machine afterward.

Accelerate your KeyShot animation rendering with iRender GPU Cloud

FAQ

How long does a KeyShot turntable take to render?

Total render time depends on the number of frames and the average time required to render each frame. You can estimate it using Render Time = Frame Count × Average Render Time per Frame. For example, a 300-frame turntable averaging two minutes per frame would take approximately 10 hours when rendered sequentially. Actual performance varies with resolution, samples, scene complexity, and hardware.

What happens if a KeyShot scene doesn’t fit in GPU memory?

According to KeyShot’s GPU Mode documentation, KeyShot can fall back to CPU rendering when the scene exceeds available GPU memory. This may allow the render to continue, but it can significantly increase rendering time. Monitor VRAM usage before starting a long animation and consider reducing texture memory requirements or using a GPU with more VRAM.

Can I use my KeyShot license on a cloud computer?

For a supported node-locked license, you can deactivate KeyShot on your current computer and activate it on another machine, subject to the license terms. After rendering, deactivate the license on the remote machine before reactivating it locally. Subscription and floating licenses follow different procedures, so check your license type before moving to the cloud.

Should I export a KeyShot animation as video or image sequence?

For long animations or cloud rendering, an image sequence is generally more practical. Formats such as EXR and PNG preserve completed frames, making it easier to recover from interrupted jobs or rerender individual frames. Direct video export can be convenient for short previews, but an image sequence provides greater flexibility for compositing, editing, and final video encoding.