Armory3D

Armory3D is a free, open-source 3D game engine built around Blender, with Haxe scripting and visual logic for creating game behavior. It best suits developers who want a Blender-based workflow and need to target desktop, mobile, web or console platforms. Its broad rendering and export options make it a capable choice, provided its Blender requirement fits your setup.

Overview

Armory3D brings game development into Blender through an add-on and an external SDK. Its focus on portability, a small footprint and performance pairs with a zlib/libpng license that permits commercial applications subject to its restrictions. The privacy policy says the software does not collect, market or sell user data.

The Blender integration can keep modeling and game development in one workflow, but it also makes Blender compatibility a practical prerequisite. The setup guide calls for Blender 4.5.x LTS and says Blender 3.3 LTS and earlier are unsupported. The SDK is distributed as a Blender add-on and external SDK; the setup guide describes the add-on as portable and requiring no installation.

Key features

Game behavior can be written in Haxe or assembled with visual logic nodes, including custom nodes. This gives code-oriented developers and node users room to work in their preferred style, while the named scripting language means teams should be comfortable adopting Haxe. Multiplayer tools are also supported.

The scriptable renderer offers deferred and forward paths, as well as custom render paths. That flexibility gives developers more control over rendering than a fixed pipeline, though custom paths are most useful to teams prepared to shape their own rendering approach. The engine includes a UI library and editor for building game interfaces.

Physics uses Bullet for rigid and soft body simulation, with Oimo as an alternative configuration. For navigation, objects can be marked as actors so the engine can calculate real-time pathing with navigation meshes. Animation and effects support includes emitter and hair particles with GPU instancing, plus GPU skinning, bones, keyframes, shape keys and tilesheets.

Lighting features include voxel-based ambient occlusion, lightmapping, area lights, reflection probes and IES textures. Together with mobile and console export, these capabilities make Armory3D relevant to projects that need more than a web-only or desktop-only target, while the range of systems also gives developers more engine areas to configure.

Pricing

Armory Engine: free. The plan includes the open-source engine, Blender add-on and external SDK. There are no paid tiers or subscription terms in this plan. Its license permits commercial use subject to the stated restrictions, so it is an option for both individual developers and commercial projects that can work within those terms.

Platforms

Armory3D runs on Android, iOS, Linux, macOS, the web and Windows, and games built with the engine can target those platforms. Console export is also supported. Code editor integrations documented by the setup guide include Visual Studio Code with the Kha Extension pack, Kode Studio, Sublime Text and custom editors. For installation or usage problems, the guide points users to troubleshooting documentation and the GitHub issue tracker; the download page also links to contribution instructions, Discord and release notes.

Who it's for

Choose Armory3D if you want Blender to anchor your 3D game workflow, value a choice between Haxe and visual logic, or need one engine with desktop, mobile and web exports. It is less suitable if your project depends on Blender 3.3 LTS or earlier, or if you do not want to build around Blender and Haxe or node-based logic.

Pros and cons

Pros: A Blender-centered workflow joins 3D creation and game development in one environment.

Pros: Haxe, visual logic and custom nodes offer more than one route for implementing game behavior.

Pros: Desktop, mobile, web and console export give projects a broad set of deployment targets.

Pros: The free, open-source engine allows commercial use subject to its license restrictions.

Cons: Blender 4.5.x LTS is the setup guide's requirement, while Blender 3.3 LTS and earlier are unsupported.

Cons: Haxe is the named scripting language, which may not suit teams committed to a different language workflow.

Cons: The feature breadth, including custom rendering paths and multiple physics options, may be unnecessary for projects seeking a narrower, simpler tool.

Alternatives

For a game-visual-scripting shortlist, see Game Visual Scripting Software; for a broader comparison, see Game Development Software or Game Engine Software.

Choose Construct 3 instead if you want a freemium option with a free plan and trial, and an individual Personal License that unlocks all features and can be canceled any time.

Flowlab is another freemium choice; its free plan is capped at three games, five levels per game and 50 game objects, and does not allow exporting, so Armory3D is a stronger fit when deployment from the free plan matters.

GDevelop offers a free plan for creating a first game; choose it if that is the starting point you want rather than Armory3D's Blender-based workflow.

Choose Stencyl if publishing to web or HTML5 is the priority on its Starter plan, or if its $99 a year Indie plan's web and desktop publishing matches your needs.

Clickteam Fusion 2.5 offers a free edition with limited HTML5 export and a $99.99 USD one-time PC edition for commercial games and apps; consider it if those terms fit your intended release.

CopperCube is another option, with a free edition and open-source WebGL engine code.

GameMaker may suit a project that does not need console exports on its free plan, which is for non-commercial use only.

For another alternative, see RPG Paper Maker.

Verdict

Armory3D is a strong fit for developers who want a free, Blender-centered 3D engine with Haxe or visual logic and broad export reach. Its distinctive advantage is combining that workflow with flexible rendering and physics options; its main drawback is the Blender version requirement. Choose it when Blender is already part of your process, and look elsewhere if that compatibility constraint or Haxe-centered scripting is a poor match.