ArmorPaint: Open-Source 3D PBR Texture Painting
ArmorPaint fills a real gap for artists who want a dedicated, open pipeline for PBR texture creation without vendor lock-in. The trade-off is steep: the development build requires setting up platform-specific compilers, and stable releases are paid. If you have the patience to compile it and value having full control over your texturing workflow, it is worth the effort.
What is ArmorPaint?
ArmorPaint is a dedicated application for painting physically-based (PBR) materials directly onto 3D models. Written in C, it targets artists and developers who need a standalone texturing tool that can generate maps for roughness, metalness, height, and other PBR channels without tying them to a particular DCC application. The source code is public, but distributed binaries are paid.
Core Capabilities for 3D Artists
- โDedicated PBR workflow for creating roughness, metalness, height, ambient occlusion, and normal maps on 3D meshes
- โCross-platform support with native builds for Windows, Linux, macOS, iOS, Android, and WebAssembly
- โWritten in C for performance and portability, with platform-specific build tooling via a shared make system
- โManual available at armorpaint.org/manual covering core workflows
- โLocale extraction tooling for translating the interface into other languages
- โExperimental data embedding using C23 #embed for standalone binary distribution
- โOpen development model with all source code publicly accessible on GitHub
Compiling ArmorPaint from Source
Start by cloning the repository with `git clone https://github.com/armory3d/armorpaint` and navigating to the paint subdirectory. Platform-specific compilers are required: Visual Studio with clang tools on Windows, clang with documented Linux dependencies on Linux, Xcode on macOS and iOS, and Android Studio on Android. Run `../base/make` on each platform to generate the appropriate project files, then open the generated project and build. On Linux, append `--run` to compile and launch directly. For WebAssembly, use `--target wasm --compile --embed`. The README links to a Linux dependencies document for the full list of required packages.
Strengths
- โOpen development with publicly available source code and build tooling
- โSupports a wide range of platforms from desktop to mobile and web
- โDedicated PBR texturing focus without the overhead of a full 3D modeling suite
- โLocale extraction tooling enables interface localization
Important Considerations for Developers
- โณDevelopment builds require platform-specific compilers to be installed and configured manually
- โณStable distributed binaries are paid, which limits accessibility for non-developer users
- โณDocumentation states the repository may not be stable, making it unsuitable for non-technical artists seeking reliability
- โณNo pre-built free binaries provided, creating a gap between open source and free use
- โณCompiler requirements (clang 19+ for data embedding, Visual Studio on Windows) add friction for contributors
Other 3D Painting Tools
Frequently Asked Questions
The source code is publicly available on GitHub for free, but distributed binaries are paid to fund the project. Compiling the development version yourself is free but requires compiler setup on your platform.
ArmorPaint targets Windows x64, Linux x64, macOS arm64, iOS arm64, Android arm64, and WebAssembly. Each platform requires a different compiler toolchain and generates platform-specific project files.
The README explicitly warns that the git version may not be stable. For production, artists typically use paid stable releases or evaluate whether the development build meets their reliability requirements.
Contribute by cloning the repository, making changes to the C source in the paint directory, and submitting pull requests on GitHub. Familiarity with the platform-specific build system and a compiler matching the project's requirements is needed.
ArmorPaint is written in C. The build system uses platform-specific make scripts to generate Visual Studio, Xcode, or Android Studio projects depending on the target platform.
The official manual is hosted at armorpaint.org/manual and covers the core interface, brush tools, and PBR texturing workflows for artists new to the software.
The problem it solves
Most professional 3D PBR painting tools are expensive, closed-source, or bundled with larger suites you may not need. Indie developers and smaller studios often lack affordable options for creating physically-based materials that integrate cleanly with game engines and renderers outside a specific ecosystem.
Best use cases
- โขCreating PBR material textures for game assets in engines like Godot, Unreal, or Unity
- โขTexturing 3D models for architectural visualization without subscribing to a full DCC suite
- โขDeveloping custom material workflows for real-time rendering pipelines
- โขBuilding portable, self-contained texturing tools for studio pipelines
- โขContributing to or forking a C-based 3D painting application for specialized needs
Who should try it โ and who should skip
ArmorPaint suits developers and technical artists comfortable compiling C code who want a standalone PBR texturing tool for custom pipelines or indie game development. Skip it if you need stable, pre-built software without setup effort, or if you prefer the polish and ecosystem of established commercial tools.
Related repositories
Is armorpaint worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of armorpaint.
