Overview
V-Ray is the renderer that architectural and product work has been finished in for two decades, and this is the build that lives inside SketchUp rather than in a separate application. Materials, lights, cameras and render settings all appear as SketchUp toolbars and dialogs, so a model goes from massing study to a presentation image without leaving the window it was built in.
Two engines ship together. The CPU engine is the reference path, deterministic and predictable, and the GPU engine trades a few features for interactive speed on a modern card. The interactive preview updates as you drag a light or change a material, which is what turns lighting from guesswork into something you can judge while you work.
Around the engines sits the practical set: a physical material system with real reflectance behaviour, a large asset library of surfaces and vegetation, a sun and sky model driven by location and time, light objects that match real fixtures, proxy geometry for scenes far heavier than SketchUp would otherwise carry, and a frame buffer with layered post correction so an image is finished before it ever reaches an editor.
What it does well
Two engines
A deterministic CPU path and a GPU path for interactive work, both driven from the same scene and material set.
Interactive preview
Move a light, swap a material or nudge a camera and the preview keeps resolving, so lighting decisions happen live.
Asset library
A large bundled library of physical materials, light fixtures and vegetation that drops into a scene with a drag.
Proxy geometry
Heavy assets load as lightweight stand-ins in the viewport and resolve at render, so a scene with real planting still opens.
Frame buffer with post
Exposure, curves, bloom, glare and lens effects applied as layers on the rendered result, saved with the scene.
Changes in this build
- GPU engine gained fuller support for the material features that previously forced a CPU render.
- Denoiser retrained, so a usable image resolves from far fewer samples.
- Material library expanded with new surfaces and updated vegetation.
- Scene intelligence pass automatically sets exposure and white balance on a first render.
- Faster geometry export from very large SketchUp models.
What is in the package
- V-Ray for SketchUp installer, 64-bit
- CPU and GPU rendering engines
- Physical material and vegetation asset library
- Frame buffer with layered post correction
- Sample scenes and render presets
System requirements
| Processor | Intel or AMD 64-bit with SSE 4.2, high core count strongly recommended |
| Memory | 16 GB minimum, 32 GB or more for interior scenes |
| Graphics | CUDA capable GPU with 8 GB VRAM for the GPU engine |
| Storage | 10 GB free for the install and library |
| Display | 1920 x 1080 minimum |
| Host | A supported SketchUp release must be installed first |
Installation
- Install and launch the host modelling application once before starting.
- Extract the archive to a local folder.
- Close SketchUp completely, including any background process.
- Run setup and let it register the toolbars and the asset library.
- Open SketchUp, load a sample scene and run one render so the shader cache builds.
Before you start
The plugin binds to a specific host release. A SketchUp upgrade means reinstalling the renderer.
The GPU engine needs current display drivers, an old driver shows up as a black render rather than an error.
Keep the asset library on a fast drive, it is read constantly during scene assembly.
Questions about this title
Do I need SketchUp installed first?
Yes, this is a plugin. Install and launch the host once before running setup.
CPU or GPU?
GPU for speed while you work, CPU for the final image if the scene uses features the GPU path handles differently.
Is the material library included?
Yes, the full bundled asset library installs with the plugin.
Can it render animation?
Yes, camera and scene animation from the host renders through the same settings.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.