Godot plugin upgrade checker

Plugins & extensions

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": "godot",
  "platform": "windows",
  "architecture": "x86_64",
  "generatedAt": "2026-10-05T00:00:00Z",
  "host": {
    "name": "Godot",
    "version": "4.6"
  },
  "components": [
    {
      "id": "my-component",
      "name": "My component",
      "version": "1.0",
      "category": "Editor Plugin",
      "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

Check the whole Godot project stack

Add editor plugins, GDExtensions, GodotSteam, dialogue/terrain tools, native libraries and export templates. Check the renderer and project language alongside engine versions.

Inspect .NET and native binary requirements

Use advanced options to specify runtimes such as .NET. If a required API or binary is not ready, the report includes dependency impacts, reasons to wait and their sources.

Godot Preflight checks the project stack before an engine update. Add editor plugins, GDExtensions, dialogue and terrain tools, native libraries and export templates; specify the renderer, scripting mode and .NET runtime when applicable. Required dependencies propagate failures through the stack, while absent evidence remains unknown. The sample demonstrates unresolved API changes without asserting that GodotSteam, Terrain3D or another real project supports an unverified target.

How it works

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

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

Worked example

A fictional Godot 4.6 project targets 4.7. Its native extension has no fix for an API change; renderer and runtime choices must also be verified before exporting.

SAMPLE: Godot 4.6 → 4.7

Check the result

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

Troubleshooting

Symptom	Likely cause	How to check	Fix
Godot stack · Unknown compatibility	No verified statement matches the target	Read the vendor link and installed version	Keep the verdict cautious until verified
Godot stack · Dependency failure	A required runtime is missing or blocked	Open the component dependency section	Resolve the dependency before upgrading
Godot 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	Godot stack: Verify target support for with the vendor.

What this page does not cover

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