Is Mantra Dead? What to Do With Legacy Mantra Scenes in 2026
Mantra is not removed, but it is not developed either. SideFX limits it to critical bug fixes and positions Karma as its replacement for new projects.
- Status: development is limited to critical bug fixes; Houdini 22 still documents the Mantra ROP
- SideFX plan: Karma to become the only supported built-in renderer; the FAQ dates have passed without an update
- Karma CPU: renders /obj scenes using the Principled shader; most VEX shading functions are not supported
- Karma XPU: will never support VEX-based shaders; use MaterialX
- Legacy shots: keep the Houdini build that rendered them, or move to Karma through the Karma ROP in /out
Mantra rendered Houdini scenes for decades, and many studios still have shots, HDAs and lookdev built around it. Since Karma arrived, the question keeps coming back: can you still render those scenes, and should you?
This guide sets out what SideFX actually says about Mantra, what still works in Houdini 22, and three practical paths for legacy scenes, from re-rendering them unchanged to rebuilding them for Karma XPU.
Checked against the SideFX Mantra and Karma FAQs and Houdini 22 documentation for Karma, Karma XPU, MaterialX and the Mantra ROP, November 2026.
What SideFX says about Mantra
The SideFX FAQ states that development on Mantra is limited to critical bug fixes. It planned support until the end of 2024, two years after Karma XPU was released, after which Karma would become Houdini’s only supported built-in renderer, and it said AUP customers keep their unsupported existing licences until at least 2025.
How to read the figure. Read the timeline from left to right. The blue point is the release of Karma XPU, which started the two-year countdown in the SideFX FAQ. The orange points are the dates the FAQ gives: the planned end of Mantra support at the end of 2024, and 2025 as the earliest date AUP users could lose their unsupported licences. The green point is today: the Houdini 22 documentation still describes the Mantra ROP and has no removal notice. The quote box is the safest summary: Mantra still exists, but only critical bugs get fixed.
Is Mantra still in Houdini 22?
Yes, in the documentation at least. The Mantra ROP page in the Houdini 22 docs still reads “Renders the scene using Houdini’s standard mantra renderer and generates IFD files”, with no deprecation notice, and the Houdini 22 release notes do not mention Mantra. We found no official removal notice. Whether SideFX considers Mantra formally unsupported in Houdini 22 is not stated, so treat it as legacy: usable, but not where new work should start.
The architectural difference is clear. According to SideFX, Mantra uses IFD and is not available in Solaris, while Karma uses USD and runs within LOPs. Karma is intended to replace Mantra for new projects.
Three paths for legacy Mantra scenes
Which path you choose depends on whether the shot is finished, how custom its shading is, and how much speed you need.
How to read the figure. All three arrows start from the same legacy scene. Path A, in green, changes nothing: re-render with the Mantra ROP in the Houdini build that made the shot, which is the safe choice for finished work. Path B, in blue, moves to Karma CPU through the Karma ROP in /out; scenes that use the Principled shader carry over, but most custom VEX shading does not. Path C, in orange, is a rebuild for Karma XPU with MaterialX materials, which gives GPU speed but means recreating every shader. The yellow line is the trade-off.
Moving an /obj scene to Karma step by step
SideFX has no official Mantra-to-Karma migration guide, so the steps below are a practical order rather than a documented procedure. The key fact is documented: the Karma ROP in /out wraps Scene Import, giving artists coming from Mantra a Karma workflow without Solaris.
How to read the figure. Badge 1 keeps the existing Mantra ROP and renders one frame as the look reference. Badge 2 is a new Karma ROP in /out set to Karma CPU, pointing at the same camera; it imports the /obj scene for you, so no Solaris setup is needed. Badge 3 renders the same frame for a side-by-side comparison. Badge 4 is where the work is: Principled materials carry over to Karma CPU, but custom VEX shaders need rebuilding, and for Karma XPU every material must be MaterialX.
Shaders, licences and what will not carry over
- Karma CPU can render /obj scenes that use the Principled shader, but SideFX notes it does not support most VEX shading functions or point-cloud lookups.
- Karma XPU will never support the traditional VEX-based shaders used by Mantra and Karma CPU. On XPU the Principled Shader will either not work or be an approximation at best, so use the USD MaterialX Builder for portable materials.
- Licensing. Generating IFD or USD needs an FX, Core or Engine licence; writing pixels needs a Renderer (Mantra) or Karma Renderer licence. The SideFX FAQ states that Mantra licences are free and that Mantra is licensed per machine.
Work through these before you re-render or convert an old shot.
SaaS or IaaS for legacy Mantra work
Legacy scenes depend on an exact Houdini build and custom shaders, which decides where they can render.
Rendering old Mantra scenes today
A neutral comparison for studios with legacy Houdini work.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| You need an older Houdini build | Farms usually support recent versions only | Install the exact build you need; the server image is kept |
| You want to compare Mantra and Karma | Two separate submissions | Render both on the same machine and compare directly |
| Your shots use custom VEX and HDAs | Must be supported by the farm | Your HDAs and packages work as at home |
| Licensing | Provided for supported renderers | You bring your own SideFX licences |
Re-rendering or migrating legacy scenes on iRender
How to read the figure. The top row is the setup: your own PC or Mac connects by remote desktop to a whole bare-metal server with 1, 2, 4 or 8 GPUs, so you open your Houdini project there exactly as at home. The numbered row is the order of a session: register and top up, upload to iRender Drive before the server runs, start and connect, render a test frame and the job, then shut down so billing stops.
- Register an iRender account and top up; the first top-up of $50 or more gets a 100% bonus.
- Upload the project folder to iRender Drive before you start the server.
- Start a server and connect by remote desktop; CPU-heavy Mantra and Karma CPU renders use the Threadripper PRO CPU, Karma XPU uses the GPUs.
- Install the Houdini build you need with your own SideFX licence; the server image is kept between sessions.
- Render the Mantra reference frame, then the Karma version, and compare.
- Render the sequence, download it and shut the server down so billing stops.
Frequently asked questions
1. Is Mantra dead in 2026?
Not removed, but not developed. SideFX states that development on Mantra is limited to critical bug fixes, and the Houdini 22 documentation still describes the Mantra ROP with no removal notice.
2. When did SideFX plan to end Mantra support?
The SideFX FAQ planned support until the end of 2024, two years after Karma XPU was released, with Karma becoming the only supported built-in renderer. Those dates have passed and the FAQ has not been updated.
3. Can Karma render my Mantra scenes?
Karma CPU can render /obj scenes that use the Principled shader through the Karma ROP in /out. Custom VEX shaders mostly need rebuilding, because Karma CPU does not support most VEX shading functions.
4. Does Karma XPU support VEX shaders?
No. SideFX states that Karma XPU will never support traditional VEX-based shaders. Use MaterialX, USD Preview Surface or Karma VOPs.
5. Do I need a licence to render with Mantra?
Writing pixels needs a Renderer licence. The SideFX FAQ states that Mantra licences are free and licensed per machine; generating the IFD needs an FX, Core or Engine licence.
6. Can I render legacy Mantra scenes on iRender?
Yes. Install the Houdini build the shot needs with your own SideFX licence; the server image is kept, so the same build is there next session.
Run your Houdini scenes on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 4x NVIDIA RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Houdini and use your own SideFX license; your server image is saved between sessions, so Houdini, your packages and caches stay installed. For Karma XPU and GPU-accelerated solvers we recommend the 4-GPU servers.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This video walks through rendering a Houdini Karma XPU scene on an iRender server in five steps:
New users get a 100% bonus on the first top-up (minimum $50). See the Karma XPU render farm page for server options, or download the iRender GPU app.
If Karma XPU renders are slow on your machine, iRender’s Karma XPU render farm gives you a dedicated remote server where you install Houdini, bring your own license and render on multiple RTX 5090 GPUs (for Karma XPU, 4 GPUs is usually the most efficient setup).


