Blender add-on upgrade checker

Add-ons & pipelines

Your setup is analyzed locally in this browser.

02What’s in your setup?

Browsers cannot scan your PC. Import an inventory JSON from a local scanner, or enter a list.

View import format

JSON up to 5 MB · up to 10,000 components · imported verdicts are recomputed.

{
  "schemaVersion": 1,
  "vertical": "blender",
  "platform": "windows",
  "architecture": "x86_64",
  "generatedAt": "2026-10-05T00:00:00Z",
  "host": {
    "name": "Blender",
    "version": "4.5 LTS"
  },
  "components": [
    {
      "id": "my-component",
      "name": "My component",
      "version": "1.0",
      "category": "Add-on",
      "critical": true
    }
  ]
}

What’s in your setup? 0

Changes to your setup recalculate the report immediately.

My setups

Setup name

03Upgrade verdict

Loading environment data…

Your inventory · Missing verified evidence stays UNKNOWN.

Compare target

Preflight your Blender creator pipeline

Check add-ons, extensions, Geometry Nodes packs, render engines, Python tools, asset libraries and export pipelines together. Numeric versions are compared correctly with LTS tags.

Review Python and API changes together

Resolve tested ranges, Python runtime requirements, binary extensions and API changes from evidence. Unresolved critical changes produce a WAIT verdict.

Blender Preflight checks an entire creator stack before a Blender upgrade. Include add-ons, extensions, Geometry Nodes packs, render engines, Python tools, asset libraries and export tools. The engine compares numeric versions correctly even when the target has an LTS label. Verified Python/runtime and API requirements can block a dependant or recommend waiting. The fictional sample is useful for learning the workflow; real add-on support still requires scoped primary-source records.

How it works

Blender stack: Being listed in the catalog does not establish compatibility.

Blender stack: Based on source authority, verification dates and the weakest relevant requirement.

Worked example

A fictional Blender 4.5 LTS stack targets 5.2 LTS with a Python runtime requirement and an unresolved renderer API change. The sample verdict recommends waiting.

SAMPLE: Blender 4.5 LTS → 5.2 LTS

Check the result

Blender stack: Your inventory · Missing verified evidence stays UNKNOWN.
Blender stack: Your setup is analyzed locally in this browser.

Troubleshooting

Symptom	Likely cause	How to check	Fix
Blender stack · Unknown compatibility	No verified statement matches the target	Read the vendor link and installed version	Keep the verdict cautious until verified
Blender stack · Dependency failure	A required runtime is missing or blocked	Open the component dependency section	Resolve the dependency before upgrading
Blender stack · JSON rejected	Wrong vertical or unsupported inventory schema	Check schemaVersion, host and component IDs	Export a version 1 inventory for this vertical

Other ways to do it

Option	When it is the better choice
Vendor documentation	Blender stack: Verify target support for with the vendor.

What this page does not cover

Blender stack: SAMPLE DATA · Fictional components for demonstration. Not real product compatibility.
Blender stack: Browsers cannot scan your PC. Import an inventory JSON from a local scanner, or enter a list.