Corona Render Is Too Slow on My CPU: Faster Options for Arch-Viz
Corona is a popular CPU-based rendering engine widely used in architectural visualization for its photorealistic lighting and ease of use. Because it relies on Intel Embree ray tracing kernels rather than graphics cards, upgrading your GPU will not speed up your rendering times—the GPU only assists with optional AI denoising. Before investing in new hardware, you can drastically reduce render times using free built-in features, such as smart denoising, the downscaling workflow, and distributed rendering across local machines. In this article, Radar Render will discuss why Corona runs slowly on CPUs and explore the most effective solutions and faster options for your arch-viz projects.
Why is Corona using my CPU and not my graphics card?

source: chaos
Because Chaos Corona is designed to render entirely on the CPU, using Intel Embree ray tracing algorithms. Your graphics card (GPU) is only used to display the viewport, or to help with AI denoising if you turn that feature on.
There is no hidden button or setting to make Corona render on your graphics card. This is a deliberate design choice by the developers. By rendering on the CPU, Corona can use your computer’s large RAM (usually 32GB to 128GB or more). This means heavy arch-viz scenes with millions of polygons and hundreds of high-resolution textures will never run out of memory like they often do on GPU VRAM.
Therefore, when buying hardware for Corona, you should spend your budget on more CPU cores and more RAM, rather than expensive graphics cards. You can read our article on V-Ray GPU vs CPU architecture to understand this difference better.
How much time does denoising actually save?
Denoising saves a lot of time. Chaos documents state that denoising reduces the number of passes needed to get a clean image, usually cutting render times by 50 to 70 percent depending on the scene.
Instead of waiting for hundreds of passes to clean up noise naturally, you can stop rendering much earlier once the image is clear enough and let the denoiser smooth out the rest. Corona offers three main denoisers:
- Corona Denoiser: A full CPU-based denoiser that gives the highest quality and sharpest details. It is applied after rendering finishes.
- NVIDIA OptiX: Uses NVIDIA AI cores to update almost in real time during rendering, making it great for quick previews.
- Intel AI Denoiser: A balanced option between speed and quality that runs smoothly on both CPU and GPU.
A big advantage is that you can adjust the denoising amount directly in the VFB (Virtual Frame Buffer) or via the Corona Image Editor after rendering finishes without needing to render again from scratch.
However, there is an important warning for animation: the Intel AI Denoiser lacks temporal consistency. Each video frame might get slightly different denoising, causing uncomfortable flickering between frames. For animations, you should use the default Corona Denoiser or run a short test render first.
What is the downscaling workflow and does it really help?
This is an official technique from Chaos where you render at double resolution, use Intel AI Denoiser, and then save the image at 50% size.
Here are the 3 simple steps:
- In Render Setup, set resolution to 2 your target size (e.g., render at 38402160 for a 19201080 final image).
- Under Denoising, select Intel AI Denoiser.
- After rendering, click Save 50% in the VFB to save the image at normal size.
Why it works: Shrinking a high-resolution image smooths out remaining noise. This lets you stop rendering much earlier while keeping fine details sharp. Chaos tested this method and got renders up to 6 times faster, though actual speed depends on your scene.
I once used this trick for an urgent interior project. Not only did it cut render time in half, but wood and tile lines also looked cleaner and sharper than rendering at normal size directly.
Note: Since this method uses Intel AI Denoiser, use it for still images only. Avoid using it for animations to prevent flickering between frames.
Can I use the other computers in my office?
Yes, absolutely. Corona has a built-in feature called Distributed Rendering that works seamlessly with 3ds Max and Cinema 4D to combine the power of multiple computers on the same local network. According to Chaos, rendering speed increases almost linearly with each added computer. For example, a heavy scene that takes 10 minutes on one PC will take only about 5 minutes if you add a second PC with similar specs. However, transferring large files over the network may cause a small slowdown. In this setup, your main PC works as the Master Node (controls the project and renders), while the other PCs act as Render Nodes.
Note: If you use AI denoising, all connected computers must have compatible graphics cards and drivers so denoising works properly across all nodes.
Should I switch to a GPU renderer instead?
You should only switch if you are ready to change your entire workflow. If you want GPU speed without leaving the Corona ecosystem, the easiest option is connecting Corona directly to Chaos Vantage. Chaos Vantage lets you send your entire scene from Corona to render still images and animations extremely fast using your GPU. You can learn more about optimizing for these tools in our guide on choosing a render farm for real-time archviz.
However, keep in mind that Chaos Vantage is a separate program. While Corona-to-Vantage conversion is getting better, some advanced materials and complex effects from pure Corona still do not look 100% the same in Vantage. If you decide to fully switch to a pure GPU engine like V-Ray GPU, remember it takes time to recreate materials and lighting for ongoing projects. For a deeper look at these differences, check out our comparison on GPU vs CPU rendering in 3ds Max interior design.
What should I look for in a render service for Corona?
When choosing an external render service for Corona, the most important things to check are the number of CPU cores per node and supported Corona versions, rather than graphics card specs.
Since Corona renders purely on the CPU, GPU-focused services will not speed up your workflow. Before renting, ask the provider these key questions:
- How many total CPU cores and what clock speed does each node have?
- Does the system support your exact Corona version and plugins (like Forest Pack or RailClone/Itoo)?
- Are proxies and asset file paths handled automatically?
- Are you billed per minute or by fixed hourly slots?
If you prefer remote desktop rental, services like iRender offer powerful PCs where you have full control to install software yourself. However, keep in mind that iRender’s main strength is multi-GPU setups. If you only run pure CPU Corona without Vantage or V-Ray GPU, those expensive graphics cards will go unused. Always compare the CPU specs of the rented machine with your current PC to make sure it is cost-effective.
What else in my scene is making Corona slow?
Besides hardware, settings inside your 3D file also affect render speed:
- Output Resolution: Avoid setting higher image sizes than needed, unless you are deliberately using the downscaling workflow.
- Complex Materials: Surfaces with heavy reflection, refraction, or subsurface scattering (like frosted glass, rough metal, or marble) take much longer for the CPU to render than simple diffuse materials.
- Number of Lights: Too many small artificial lights inside an interior scene increase calculation time. Try grouping small lights or using larger Area Lights instead.
- Geometry Optimization: Always convert repeated objects (like trees, chairs, or recessed ceiling lights) into Corona Proxies to save RAM and shorten scene preparation time.
Need extra rendering power for Corona?
With iRender, you rent a complete, high-specification physical server via Remote Desktop on an hourly basis. You have full freedom to install your own licensed version of Chaos Corona and complementary software like Chaos Vantage or V-Ray GPU.
Since Corona relies strictly on CPU performance, be sure to compare the node’s CPU core count with your current PC to ensure maximum cost-efficiency.
👉 Try iRender for free today: Benchmark one of your heavy Corona scenes on our high-core CPU nodes before committing to a full project!
FAQs
1. Can Corona use my graphics card to render faster?
No. Chaos Corona renders entirely on the CPU using Intel Embree ray tracing kernels, and there is no option to switch to GPU rendering. The graphics card is only used for viewport display and optional AI denoising. Therefore, for a Corona workflow, your upgrade budget should go into CPU cores and system memory rather than graphics cards.
2. How much faster is Corona with denoising?
Chaos states that denoising reduces the number of passes needed for a clean image, with time savings commonly reported between 50 and 70 percent. Actual savings vary depending on the scene and settings. You can choose between the Corona Denoiser applied after rendering finishes, NVIDIA OptiX which works nearly in real time, and Intel AI as a hybrid option. For animation, be careful with the Intel AI Denoiser because it lacks temporal consistency and can cause flickering between frames.
3. What is the Corona downscaling trick?
This is an official workflow recommended by Chaos, where you render at double the final resolution, select the Intel AI Denoiser in the Render Setup Denoising section, and then use the option to save at half size. Downscaling averages out the remaining noise, allowing you to stop rendering earlier while keeping the final image clean and sharp. Chaos guides show significant speed improvement in their example, but results depend on your scene.
4. Can I render one Corona image across several computers?
Yes. Corona has its own distributed rendering system that works natively with 3ds Max and Cinema 4D. Chaos documentation states the speedup is almost linear. For example, an image that takes ten minutes on one machine can finish in about five minutes on two identical machines, minus a small network bandwidth overhead for large scenes at high resolutions. If you use AI denoising, all participating machines need compatible GPUs and drivers installed.
5. Which render service is right for a Corona project?
Choose based on CPU core count, not graphics card specs, because Corona does not use the GPU for rendering. Key questions to ask the provider include the total CPU cores per node, supported Corona version, support for proxies and scatter plugins, and whether billing is calculated per frame or per node-hour. Chaos provides an official render farm partner page so you can compare providers yourself.
See more: Why Corona Renderer Maxes Out CPU & RAM in 4K Batch Renders (And How to Fix Thermal Bottlenecks)
Part of our guide: for a full overview of cloud options, see the Corona render farm guide.