Skip to content
InvokeAI Logo InvokeAI Documentation

Releases

v5.13.0

This release adds advanced Inpainting mask controls and a selection of other minor enhancements.

Changes

  • Canvas Inpaint Masks have additional per-mask settings. Enable them via right-click menu on the mask layer. Thanks @dunkeroni for working on these very useful features!
    • Noise Level adds image-space noise to the masked region before it is denoised. This can add natural variation and detail to the region. The added noise is generated using the global seed parameter as the RNG seed.
    • Denoise Limit caps the amount of denoising done on the masked region. You can inpaint multiple regions of the image simultaneously, but with different amounts of variation. This greatly simplifies a workflow where you want to make variations on an image, but want different parts of the image to vary more or less.
  • When selecting aspect ratios, give special handling to SDXL’s trained sizes to reduce artifacts. Thanks @dunkeroni!
  • Improved Canvas scroll-to-zoom handling, including smoother scaling on touchpads and snapping to common zoom levels.
  • Added button to pull the bbox content into an empty Control Layer.
  • Added ability to delete all images from the Uncategorized board via button in its right-click menu.
  • Prompt boxes remember their size.
  • Support installing HF repo subfolders via Model Manager’s HuggingFace tab.
  • Faster Heuristic Resize algorithm, used in New Layer from Image (Resize) functionality.
  • Allow LoRA patcher to skip unknown layers instead of erroring. Thanks @keturn!
  • Log a warning when a node has an unregistered output class.
  • Updated Compel to get better handling for long prompts.
  • Updated translations.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.12.0…v5.13.0

v5.12.0

This release includes support for Nvidia 50xx GPUs, a way to relate models (e.g. LoRAs with a specific main model), new IP Adapter methods and other smaller changes..

Changes

  • Bumped PyTorch dependency to v2.7.0, which means Invoke now supports Nvidia 50xx GPUs.
  • New model relationship feature. In the model manager tab, you may “link” two models. At this time, the primary intended use case is to link LoRAs to main models. When you have the main model selected, the linked LoRAs will be at the top of the LoRA list. Thanks @xiaden!
  • New IP Adapter methods Style (Strong) and Style (Precise). The previous style method is renamed to Style (Simple). Thanks @cubiq!
  • Fixed GGUF quantization on MPS. Thanks @Vargol!
  • Updated translations. Thanks @Harvester62 @rikublock @Linos1391 @RyoK0220!
  • Internal: Invocation model changes, which aim to reduce occurrences of ValidationError errors.
  • Internal: Addressed pydantic deprecation warning.
  • Internal: Re-enabled new model classification API with safeguards.

🚨 Stricter Rules for Nodes, including Custom Nodes

This section is for node authors, whose nodes may be affected by the stricter rules.

Default values for node fields are now validated as the app starts up.

For example, this node defines my_image as an ImageField, but it provides a default value of None, which is not a valid ImageField:

@invocation("my_invocation")
class MyInvocation(BaseInvocation):
    my_image: ImageField = InputField(default=None)


    def invoke(self, context: InvocationContext) -> ImageOutput:
        ...

This node will error on app startup:

# 😱 Error on startup!
InvalidFieldError: Default value for field "my_image" on invocation "my_invocation" is invalid, 1 validation error for MyInvocation
my_image
  Input should be a valid dictionary or instance of ImageField [type=model_type, input_value=None, input_type=NoneType]

There are two ways to fix this, depending on the node author’s intention.

1. If the field is truly optional, update the type annotation.

Using the example invocation from above, make the type annotation for my_image a union with None:

@invocation("my_invocation")
class MyInvocation(BaseInvocation):
    my_image: ImageField | None = InputField(default=None)


    def invoke(self, context: InvocationContext) -> ImageOutput:
        ...

ImageField | None is equivalent to Optional[ImageField]. Either works.

2. If the field is not optional, remove the default or provide a valid default value.

Using the example invocation from above, simply remove default=None:

@invocation("my_invocation")
class MyInvocation(BaseInvocation):
    my_image: ImageField = InputField()


    def invoke(self, context: InvocationContext) -> ImageOutput:
        ...

This node has an integer field that must be greater than 10, but the provided default value of 5. This will error:

@invocation("my_other_invocation")
class MyOtherInvocation(BaseInvocation):
    my_number: int = InputField(default=5, gt=10)


    def invoke(self, context: InvocationContext) -> IntegerOutput:
        ...

Either remove the default, or provide a default value greater than 10.

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

New Contributors

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.11.0…v5.12.0

v5.11.0

This release’s largest change is a new and improved model drop-down component.

🚨 Achtung! 🚨

If you already updated to v5.10.0, you can skip this section. If you are on v5.9.1 or older, please review this section before updating.

There are important installation notes to be aware of in this release, which includes major updates to Invoke’s core components.

  1. You must use the latest installer/launcher (v1.5.0). If you’re using an older launcher version, the update may fail.

    To fix this, download the latest installer/launcher from https://invoke.com/downloads.

  2. If the installation fails, use repair mode to fix it.

    The installation may fail due to Python environment conflicts with log messages like those in this screenshot.

    To fix this, retry the installation with repair mode enabled, which will reinstall the bundled Python and resolve most installation issues.

    Enable repair mode by ticking this checkbox on the Review step of the install, then click Install.

  3. Form Builder reset on first launch.

    When you start Invoke for the first time after updating to v5.10.0, your Form Builder will be reset, losing any unsaved changes.

    Before updating, save your current workflow. After updating, re-load it manually.

Changes

  • New model drop-down component, aiming to improve the user experience with selecting models. It’s currently enabled only for the main model drop-down.
  • Added button to reset an existing HF token to the Model Manager tab.
  • Support for FLUX LoRAs trained in invoke-training.
  • Nodes that output images, including nodes that output image collections, should always update the gallery.
  • Fixed issue where drag-and-drop didn’t scroll when used in a scrollable container (for example, when you have a lot of layers or form builder elements).
  • Internal: Updated frontend dependencies.
  • Internal: Optional output_meta field added to BaseInvocationOutput. This field is not currently exposed in the Workflow Editor. In the future, it may be exposed to facilitate attaching additional metadata to invocation outputs.
  • Internal: Support code for a generation via Imagen3/ChatGPT 4o. These API models are currently unavailable in the Community Edition, but we may be able to change that in the future.

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

New Contributors

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.10.1…v5.11.0

v5.10.1

🚨 Achtung! 🚨

If you already updated to v5.10.0, you can skip this section. If you are on v5.9.1 or older, please review this section before updating.

There are important installation notes to be aware of in this release, which includes major updates to Invoke’s core components.

  1. You must use the latest installer/launcher (v1.5.0). If you’re using an older launcher version, the update may fail.

    To fix this, download the latest installer/launcher from https://invoke.com/downloads.

  2. If the installation fails, use repair mode to fix it.

    The installation may fail due to Python environment conflicts with log messages like those in this screenshot.

    To fix this, retry the installation with repair mode enabled, which will reinstall the bundled Python and resolve most installation issues.

    Enable repair mode by ticking this checkbox on the Review step of the install, then click Install.

  3. Form Builder reset on first launch.

    When you start Invoke for the first time after updating to v5.10.0, your Form Builder will be reset, losing any unsaved changes.

    Before updating, save your current workflow. After updating, re-load it manually.

Changes

  • Support partial loading for LLaVA and SigLIP (FLUX Redux) models, reducing VRAM requirements for users with Nvidia GPUs.
  • Reduce peak CPU RAM usage during initial load of LLaVA and SigLIP models. This allows users with at least 24GB CPU RAM to run the LLaVA 7B model without crashing during load. With partial loading now working for the model, most users should be able to run the model - though it can take a few minutes if you don’t have a GPU with 24GB VRAM.
  • Revert a recent change to model installation, which could result in some models being misidentified as LoRAs.
  • The data viewer component, used to display JSON (e.g. metadata, workflows, node outputs) now wraps lines.

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.10.0…v5.10.1

v5.10.0

This release focuses on internal improvements with a number of enhancements and fixes.

The biggest enhancement is support for CogView4, a permissively-licensed model that is fairly close to FLUX in terms of quality.

🚨 Achtung! 🚨

There are important installation notes to be aware of in this release, which includes major updates to Invoke’s core components.

  1. You must use the latest installer/launcher (v1.5.0). If you’re using an older launcher version, the update may fail.

    To fix this, download the latest installer/launcher from https://invoke.com/downloads.

  2. If the installation fails, use repair mode to fix it.

    The installation may fail due to Python environment conflicts with log messages like those in this screenshot.

    To fix this, retry the installation with repair mode enabled, which will reinstall the bundled Python and resolve most installation issues.

    Enable repair mode by ticking this checkbox on the Review step of the install, then click Install.

  3. Form Builder reset on first launch.

    When you start Invoke for the first time after updating to v5.10.0, your Form Builder will be reset, losing any unsaved changes.

    Before updating, save your current workflow. After updating, re-load it manually.

Python 3.12 & PyTorch 2.6.0 support

Invoke now supports Python 3.12 and PyTorch 2.6.0. Many major dependencies have also be bumped to their latest version.

Changes

Enhancements

  • Support for CogView4 in Canvas and Workflows. Like FLUX, it works best with detailed, narrative prompts. You can download the model from the Starter Models tab in the Model Manager. It’s pretty chunky at ~30GB overall, with similar hardware requirements to FLUX.
  • Save Canvas/Bbox to Gallery buttons now save basic metadata with the image (prompts, model, seed).
  • Models now have their file sizes recorded and displayed in the Model Manager. Thanks @keturn!
  • New capabilities for FLUX Redux to control how much influences the generation. On Canvas, this is controlled by the new Image Influence setting for both Global and Regional Reference Images. There are more controls in Workflows. Thanks @skunkworxdark!
  • Added nodes to convert metadata into collection types. Thanks @skunkworxdark!
  • Improved undo/redo on Workflows.
  • Updated docs. Thanks @chantellmocha!
  • Updated translations. Thanks @rikublock @Harvester62 @Linos1391 @RyoK0220!

Fixes

  • Fixed error when loading workflows that has invalid edges. This can occur if an installation is missing a custom node.
  • When left/right arrow keys are pressed while focused on a tab UI element, do not switch between images.
  • Restored missing “Using torch device” message that should display on startup.
  • ONNX models (e.g. DW OpenPose) now have their sizes calculated correctly. This fixes an issue where these models didn’t work fully with the model manager.
  • Fixed issue where the Canvas Color Picker didn’t grab alpha values correctly.
  • Fixed Canvas layer drop indicator line color (was bright red).
  • Send to Canvas image actions now work when Canvas is uninitialized. For example, if the UI loads on the Workflows tab and the user has not yet clicked the Canvas tab, the Canvas will not be initialized.
  • Increased padding when fitting layers to canvas to prevent the floating tool panel and other buttons from covering up the edges of the layers.
  • Fixed issue where, after a Canvas reset, if no prompt is entered, generating will re-use the prompt that was last used before the reset.
  • Fixed issue where some network queries weren’t reset correctly. This could have caused a minor memory leak.

Internal

  • Support for python 3.12. This necessitates the use of repair mode during installation, as described in the 🚨 callout above.
  • Bump many dependencies to latest, including torch.
  • Remove many unused dependencies.
  • Remove legacy scripts from the codebase.
  • Ported LoRA model configs to the new classification API. This is an internal change.
  • Merged workflow Form Builder and Node Editor state and logic. Undo/redo on the Workflows tab now works for both Node Editor and the Form Builder, and the way actions are grouped in the undo/redo history is improved. This causes the loss of Form Builder state on first run, as described in the 🚨 callout above. Unfortunately, there’s no way to prevent this data loss without significant effort.

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

New Contributors

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.9.1…v5.10.0

v5.9.1

This release includes bugfixes and internal changes.

Changes

  • Enhancement: Disable the denoising strength slider for FLUX Fill, which ignores the strength parameter.
  • Fix: Error when mask blur is set to 0.
  • Fix: Issue with inpaint/outpainting where the output images were not masked correctly, causing what should be transparent areas (i.e. alpha 0/255) to be very slightly not-transparent (i.e. alpha 1/255). This threw off layer bounds calculations and caused gradual degradation across repeated inpainting/outpainting operations in unmasked areas.
  • Fix: Error when installing certain FLUX finetunes.
  • Internal: Continued iteration on model manager’s internal API.
  • Internal: CI workflows now use uv, dropped nonfunctional CUDA/ROCm workflows (we only have CPU runners anyways).

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.9.0…v5.9.1

v5.9.0

This release adds FLUX Fill support in Workflows and Canvas, beta support for the LLaVA OneVision VLLM family of models, and a selection of minor fixes and enhancements.

FLUX Fill

FLUX Fill provides high quality inpainting and outpainting, improving on these tasks over the other FLUX models. It’s a “main” model, like FLUX dev or schnell.

To use it, download it from Starter Models and then select it from the main model drop-down on Canvas. It’s not compatible* with Text to Image or Image to Image - you’ll get an error if you try to Invoke without an inpaint mask or some empty regions in your bbox.

*Technically, it can do Text to Image and Image to Image - but the quality is very poor. We’ve opted to disallow this on Canvas.

LLaVA OneVision VLLM

This multimodal model generates text from text, image and/or video* inputs. You can use it to generate prompts and and describe images. You can use it in Workflows with the LLaVA OneVision VLLM node.

The 0.5B variant of the model is available for download from Starter Models.

*Invoke does not support video inputs.

Other Changes

  • Support for custom string field drop-downs in Workflow Builder. Add a node’s string field to the Builder and choose the dropdown component to see it in action.
  • The About modal now shows the app’s runtime settings. It includes a list of explicitly-set settings (i.e. the contents of invokeai.yaml), so it is possible to see what runtime settings are app defaults and which are user-defined.
  • Improved UX for missing or unexpected fields in Workflows.
  • De-wonkified LoRA node names (they got wonkified in v5.8.0).
  • Better error messages when scanning models with picklescan.
  • Fixed issue where shift-clicking to draw on Canvas ignored Clip to Bbox setting.
  • Fixed issue with Image Viewer where the image could overflow the viewer.
  • Fixed overflow with looooong node titles.
  • Fixed a minor visual bug in string generator nodes.
  • Internal: First iteration of improved model probing API.
  • Internal: Improved testing system for model-related tests.
  • Internal: Port LLaVA OV models to use new API.
  • Internal: Cleaned up a lot of model-related code.
  • Internal: Support hot reload for custom nodes. Thanks @keturn!
  • Updated translations. Thanks @rikublock @Harvester62 @Linos1391!

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.8.1…v5.9.0

v5.8.1

This release fixes a bug with retry functionality that could result in an endless loop of errors.

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.8.0…v5.8.1

v5.8.0

This release introduces an upgraded Workflow Library and FLUX Redux support, among other fixes and enhancements.

Workflow Library

We’ve redesigned the Workflow Library to provide a smoother interface for browsing workflows.

  • Larger modal to display workflows in a grid
  • Browse by tag (default workflows only)
  • Search by name/description/tags
  • Opened at works correctly
  • Workflows may have thumbnails

FLUX Redux

This release includes support for FLUX Redux in Workflows and Canvas.

FLUX Redux is an add-on model for FLUX. It works similarly to IP Adapter or an “instant” LoRA, where an input image guides the generation’s style and composition. It can provide some degree of character consistency.

To use it on Canvas, add a Global Reference Image layer and drag a reference image onto the layer - same as you would for IP Adapter - and select the FLUX Redux from the model drop-down.

You can also use it in Regional Guidance layers. Add a Reference Image to the layer and select FLUX Redux from the model drop-down.

Other Changes

  • You may override the min and max constraints for float and integer fields added to the Form Builder. This is useful when fields are set to render as sliders and/or to add guardrails to your form fields.
  • Support for uploading WEBP images. They are converted to PNG after uploading.
  • Improvements to workflow loading, including checks on every load to ensure unsaved changes are not lost.
  • Fixed an issue where workflows were not marked as having unsaved changes when its form was edited.
  • Form Builder text and heading elements render line breaks correctly.
  • Fixed issue where some Form Builder elements didn’t fill their containers correctly.
  • Invalid node fields now display errors in the field’s tooltip.
  • Fixed issue where duplicate edges could be created when re-connecting an existing edge.
  • Focused UI regions are highlight (configurable in Settings, off by default). Thanks @joshistoast!
  • Updated the display names of model-specific nodes and default workflows to include the model. For example, Main Model Loader is now Main Model - SD1.5.
  • Internal changes to custom node loading.
  • Updated translations. Thanks @rikublock @Linos1391 @Harvester62!

Download the models from the Starter Models tab in the Model Manager.

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.7.2…v5.8.0

v5.7.2

This release adds a setting to reduce peak VRAM usage and improve performance, plus a few other fixes and enhancements.

Memory Management Improvements

By default, Invoke uses pytorch’s own memory allocator to load and manage models in VRAM. CUDA also provides a memory allocator, and on many systems, the CUDA allocator outperforms the pytorch allocator, reducing peak VRAM usage. On some systems, this may improve generation speeds.

You can use the new pytorch_cuda_alloc_conf setting in invokeai.yaml to opt-in to CUDA’s memory allocator:

pytorch_cuda_alloc_conf: "backend:cudaMallocAsync"

If you do not add this setting, Invoke will continue to use the pytorch allocator (same as it always has).

There are other possible configurations you can use for this setting, dictated by pytorch. Refer to the new section in the Low-VRAM mode docs for more information.

Other Changes

  • You may now upload WEBP images to Invoke. They will be converted to PNGs for use within the application. Thanks @keturn!
  • Added “pull bbox” button to the Regional and Global Reference Image layer’s empty state.
  • More conservative estimates for VAE VRAM usage. This aims to reduce the slowdowns and OOMs on the VAE decode step.
  • Fixed “single or collection” field type rendering in the Workflow Editor. This was causing fields like IP Adapter’s images and ControlNet’s control weights from displaying a widget.
  • Fixed the download button in the Workflow Library list, which was downloading the active workflow instead of the workflow for which the button was clicked.
  • Loosened validation for ControlNet begin and end step percentages. Thanks @JPPhoto!
  • Enqueuing a batch (i.e. what happens when you click the Invoke button) is now a non-blocking operation, allowing the app to be more responsive immediately after clicking Invoke. To enable this improvement, we migrated from using a global mutex for DB access with long-lived SQLite cursors to WAL mode with short-lived SQLite cursors. This is expected to afford a minor (likely not noticeable) performance boost in the backend in addition to the responsiveness improvement.
  • Smaller docker builds. Thanks @keturn!
  • Updated translations. Thanks @Harvester62 @Linos1391 @rikublock!

Installing and Updating

The new Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Follow the Quick Start guide to get started with the launcher.

If you don’t want to use the launcher, or need a headless install, you can follow the manual install guide.

What’s Changed

Full Changelog: https://github.com/invoke-ai/InvokeAI/compare/v5.7.1…v5.7.2

This site was designed and developed by Aether Fox Studio.