ComfyUI 0.40.0 adds native LoRA stacks and camera prompts
ComfyUI released version 0.40.0 on October 13, 2026, adding native LoRA stack loaders and camera composition tools to its visual AI workflow editor. For people building image workflows, the useful additions are controls for combining adapters and preparing camera instructions inside a graph.
Several LoRAs fit inside one loader
ComfyUI’s existing LoRA documentation describes adapters that change styles, characters or details in an image. Users could already combine them by chaining loader nodes together. The new release gives that repeated operation a compact interface.
The native stack implementation adds Load LoRA (Model) and Load LoRA (Text Encoder). Each accepts up to 20 rows, with a file, strength and enabled switch for each adapter. The two nodes separately target the diffusion model and the CLIP text encoder. Active adapters are applied in row order.
Turning a row off preserves its file and strength, making it easier to compare combinations without rebuilding the list. Disabled and zero strength rows skip loading and application. Disabled rows still undergo normal prompt validation, so the switch does not excuse missing required values.
The implementation uses the existing loading path. The merged change warns that a later adapter can overwrite metadata from an earlier one, a behavior shared with chained loaders. Workflows that rely on adapter metadata need a check before migration.
Camera controls produce reusable instructions
Compose Camera Angle Prompt takes horizontal angle, vertical angle and zoom, then returns camera data and an English shot description. An optional reference image appears on a cube in the preview. That creates a visual way to compose the requested view.
The output still needs a downstream workflow that can use the camera data or text. The node itself does not reconstruct a scene from the reference image. Treat the preview as a composition aid and check whether the chosen generation model follows the resulting instruction.
Asset scanning depends on the launch mode
The release history includes several reversals of the asset system default. The final tagged configuration leaves its database, API routes and background scanning off during an ordinary launch unless enabled. Windows standalone mode enables it, which covers the standard portable launchers. An explicit disable setting takes precedence in either case.
This distinction matters when two installations show different asset behavior after updating. Check how each starts before assuming the feature is missing or the update failed.
Check the frontend before moving a working graph
Version 0.40.0 pins frontend 1.55.17, workflow templates 0.11.82 and embedded documentation 0.5.14. The published release includes Windows portable downloads, including a new NVIDIA ARM64 package. Availability in a GitHub release does not establish that every managed installation has already received it.
The official update guide warns that updating core code without its dependencies can leave new features without frontend support. Use the update route for the installation type, keep the specified dependency versions together and test a saved workflow before replacing a working setup. The guide also warns that a full dependency reinstall can break custom nodes.
ByteForward reviewed the release, merged changes and tagged implementation. We have not run image generation benchmarks or verified every custom node combination.
The featured image is an illustrative software workstation photograph by Upen Singh, available from the WordPress Photo Directory under CC0.
