Armorpaint

Physically-based texture painting, honestly reviewed. No marketing copy, just what you get when you drop the Adobe subscription and self-host your creative pipeline.

TL;DR

• What it is: A standalone, GPU-accelerated 3D texture painting application designed as an alternative to Adobe Substance 3D Painter — source code is on GitHub, pre-built binaries are sold for a one-time fee [website].
• Who it’s for: Indie game developers, 3D artists, and small studios who need professional PBR texture painting and don’t want to pay Adobe’s recurring subscription. Not aimed at non-technical founders — this is a tool for people who make 3D things.
• Cost savings: Adobe Substance 3D Painter is only available as part of the Substance 3D Collection subscription. The collection runs ~$49.99/month for individuals. ArmorPaint is a one-time purchase from the official site. Exact pricing requires visiting armorpaint.org/download directly — data not available in scraped materials [website].
• Key strength: Runs entirely on the GPU — the team rebuilt the renderer from scratch rather than wrapping an existing engine. The result is 4K painting on integrated graphics hardware, and up to 16K on a discrete GPU. All AI features run locally with no cloud dependency [website].
• Key weakness: The license is not a standard OSI open-source license. The GitHub repo’s license field returns “NOASSERTION” — meaning you can read and compile the source, but the legal terms for redistribution and commercial use are non-standard. If license clarity matters for your project, read the repo’s license file before depending on it [GitHub].

---

What is ArmorPaint

ArmorPaint is a standalone 3D texture painting application. You drag in a 3D model, and paint directly onto its surface in a PBR (physically-based rendering) workflow — the same pipeline used in game engines, VFX production, and product visualization. The painted textures export as standard maps: base color, metallic, roughness, normal, ambient occlusion, and height.

The project is built by the same team behind the Armory3D game engine, and uses an in-house rendering engine rather than Unity, Unreal, or a standard OpenGL/WebGL abstraction layer. That architectural choice is the reason for the GPU-first performance claims — every stroke, every bake, every viewport preview runs directly on the GPU [website].

The GitHub repository sits at 3,829 stars. That’s a real number but a modest one compared to general-purpose tools like Blender (180,000+ stars) or even niche automation tools like Activepieces (21,000+). What it signals: ArmorPaint has a dedicated following among 3D artists, but it hasn’t broken into mainstream developer or maker culture the way some other open-source creative tools have [GitHub].

What makes the business model unusual is the source-available approach. You can clone the repository and compile ArmorPaint yourself, for free. The official pre-compiled builds — which save you from setting up the Haxe/Kha toolchain — are sold as a one-time purchase. This puts it in a different category than “free open-source software” and also a different category than “proprietary SaaS.” It’s closer to what some call source-available or “open-core lite” — read the code, contribute to it, but pay for the convenience build [GitHub][website].

---

Why People Choose It

The competitive context here is straightforward: Adobe acquired Allegorithmic (makers of Substance Painter) in 2019 and folded it into the Creative Cloud subscription model. Before the acquisition, Substance Painter had a perpetual license option. After: subscription only. That transition created a durable resentment in the indie 3D community, visible across game dev forums and r/gamedev threads, that ArmorPaint benefits from directly.

The OMR 3D painting software category [1] lists the competitive field: Adobe Substance 3D Painter, ZBrush, Blender, Krita, Modo, Autodesk Mudbox — all either expensive subscriptions or limited in texture painting specifically. The curated open-source creative tools list at Codeberg [5] includes ArmorPaint as one of the notable alternatives in the 3D painting space, alongside Blender’s built-in painter and Quixel Mixer. The framing in [5] is “tools for digital creatives” that don’t lock you into vendor pricing — which is exactly the value proposition ArmorPaint is selling.

It’s worth being direct about something: in-depth independent reviews of ArmorPaint are sparse compared to tools like n8n or Nextcloud. The sources available for this review are thin on user experience detail. That’s a data point in itself — ArmorPaint is used by people who make 3D models, not people who write tech blog posts. The community feedback that does exist lives in game dev Discord servers, Blender forums, and occasional YouTube comparisons, none of which were available in the source materials for this review. The analysis below relies more heavily on the official website and repository than a review of Activepieces would.

---

Features

Based on the official website and repository:

Core painting:

• Drag-and-drop model import, immediate painting in viewport [website]
• Layer-based workflow with fill layers, paint layers, and decal layers [website]
• Real-time viewport feedback — strokes appear instantly without baking delays [website]
• Edge wear effects [website]
• Subsurface scattering support in the viewport [website]

Node-based materials:

• Fully procedural material system using a node graph [website]
• Brush nodes for custom brush shapes and procedural patterns [website]
• Material fill layers built entirely from node graphs [website]

GPU rendering:

• Runs entirely on GPU — no CPU-side rendering fallbacks [website]
• 4K texture painting on integrated graphics; up to 16K on discrete GPUs [website]
• Ray-traced baking, painting effects, and viewport rendering via Direct3D12, Vulkan, and Metal [website]
• Path-traced viewport mode for true light simulation while painting [website]

Baking:

• GPU-accelerated bake for high-poly to low-poly normal maps, AO, and other standard maps [website]
• Hardware-accelerated ray-traced baking on DX12/Vulkan/Metal [website]

Live link and integration:

• Blender, Unreal Engine, and Unity live-link plugins available [website]
• Changes in ArmorPaint propagate to the connected DCC in real time [website]

AI features (all local, no cloud):

• Image to Material: extracts base color, height, normal, AO, and roughness from a photo using a local neural network [website]
• Text to Material: generates seamless PBR materials from text prompts; generates variants via seed [website]
• Tiling: converts photos to seamless textures; text-guided mode for complex features like brick walls [website]
• Upscale and Variance: super-samples textures to higher resolution; generates variants [website]
• Inpaint: fills or removes texture regions via painted mask and optional text prompt [website]
• Edit Image: adds or removes texture details via text prompt [website]
• Minimum 4GB VRAM recommended for AI nodes; all models run offline after initial download [website]
• AI models used are under open-source licenses [website]

Platform and deployment:

• Windows, Linux, macOS, iOS, and Android [website]
• Desktop version: portable application, no installer, download under 10MB [website]
• Near-instant startup [website]

Plugins:

• Plugin system for extending nodes, material systems, and custom tools [website]

---

Pricing: SaaS vs Self-Hosted Math

This is where ArmorPaint’s value proposition is clearest.

Adobe Substance 3D Collection (competitor):

• Individual: ~$49.99/month (includes Painter, Sampler, Designer, Stager, and asset library access)
• No perpetual license available
• Over 12 months: ~$600/year, recurring indefinitely

ArmorPaint:

• Pre-built binary: one-time purchase from armorpaint.org — exact current price requires checking the site directly, as it was not available in the scraped data [website]
• Source compile: free (requires setting up Haxe/Kha toolchain; non-trivial for non-developers)
• No subscription, no per-seat fee, no usage limits

The math for a solo 3D artist or indie game studio is direct: whatever ArmorPaint’s binary costs, you pay it once. After the first year, the Substance subscription has cost you more. After three years, it’s cost you three times more. The only scenarios where Substance wins on pure cost are if you legitimately need its asset library (thousands of curated materials from Adobe Stock 3D) or if you’re already inside the Creative Cloud family for other tools.

Quixel Mixer (another competitor) is free but requires an Epic Games account and ties you to the Fab/Mega-scans ecosystem. Its future under Epic is less predictable than ArmorPaint’s independent development path.

---

Deployment Reality Check

“Deployment” means something different for a desktop application than for a server tool. ArmorPaint on desktop is as simple as it gets: download the binary, unzip, run. No installer, no system libraries required, no admin rights on Windows, under 10MB [website]. The portable format means you can run it from a USB drive or a project folder.

The complications are elsewhere:

AI model setup: The AI nodes (Image to Material, Text to Material, etc.) require downloading models separately after installation. Minimum 4GB VRAM. If your GPU doesn’t meet this threshold, the AI nodes don’t run. The website doesn’t detail which models are required or how large they are — you’ll find that out during first use [website].

Source compilation: If you want to build from source rather than pay for the binary, you need the Haxe programming language and the Kha framework set up. This is a real technical lift — not as simple as npm install or docker compose up. Expect 1–3 hours for a developer unfamiliar with the toolchain. Non-developers: use the binary.

License clarity: The GitHub repository license returns “NOASSERTION” [GitHub]. Before integrating ArmorPaint into a commercial pipeline or redistributing modified builds, read the actual license file in the repo. The source-available model means the code is readable, but the terms for commercial use, modification, and redistribution may be more restricted than a standard MIT or Apache license would allow.

Mobile: iOS and Android versions exist, but texture painting on a touchscreen is a different experience than on a desktop with a Wacom tablet. The mobile versions appear aimed at convenience/portability rather than production use. No dedicated mobile review data was available in source materials.

---

Pros and Cons

Pros

• One-time purchase model. The most direct escape from Adobe’s subscription lock-in for 3D texture work. Pay once, use indefinitely, no bill next month [website].
• GPU-first architecture built from scratch. Not a wrapper around an existing renderer. The performance claims (4K on integrated graphics) are architectural, not marketing [website].
• Local AI nodes. Image-to-material, text-to-material, inpaint — all run on your GPU with no cloud connectivity after model download. Data sovereignty for studios with IP sensitivity [website].
• Portable binary. No installation, no system entanglement, runs under 10MB. Simple to set up on a new machine or share across a team [website].
• Cross-platform including mobile. Windows, Linux, macOS, iOS, Android — one tool across the full range [website].
• Live link with Blender, Unreal, Unity. Direct integration with the three most common open-source/indie DCC tools [website].
• Node-based material system. Procedural materials without requiring a separate Substance Designer license [website].
• Listed among curated open creative tools [5] — the community considers it a legitimate independent alternative.

Cons

• License is not a standard OSI open-source license. “NOASSERTION” on GitHub means the terms are non-standard [GitHub]. Fine for individual artists; needs legal review for studios doing commercial redistribution or white-labeling.
• Small community compared to Substance. Adobe’s Substance ecosystem has years of tutorials, presets, preset marketplaces, and forum answers. ArmorPaint’s community is smaller and its documentation less thorough. You’ll solve problems yourself more often.
• 3,829 GitHub stars. Active development is real, but the user base is modest. If the lead developer stops maintaining the project, the community may not sustain it. Compare to Blender or GIMP which have thousands of contributors [GitHub].
• AI node VRAM requirement. 4GB minimum VRAM is a hard requirement for the AI features. Users on older or budget hardware are locked out [website].
• No curated asset library. Substance Painter comes with access to Adobe’s 3D asset library. ArmorPaint comes with the software. If you rely on commercial-grade material libraries, you’d need to source them separately.
• Source compilation is non-trivial. The “free if you compile it yourself” option requires familiarity with Haxe and Kha — not a realistic path for most users [GitHub].
• Independent reviews are sparse. The lack of mainstream review coverage means you’re relying more on official sources and community forums to evaluate real-world quality. That’s a risk signal for enterprise adoption decisions.

---

Who Should Use This / Who Shouldn’t

Use ArmorPaint if:

• You’re an indie game developer or 3D artist currently paying for Substance Painter and wanting to cut the subscription.
• You do texture work in Blender, Unreal, or Unity and want a live-link workflow without Adobe in the middle.
• You need local AI texture generation for IP-sensitive work — generated materials that never leave your machine.
• You want a portable tool that runs on a USB drive with no installation.
• You’re comfortable on a desktop with a drawing tablet; the workflow will feel natural.

Skip it (stay on Substance Painter) if:

• You depend heavily on Adobe’s Substance 3D asset library — tens of thousands of curated materials you can’t easily replicate.
• You work in a large studio with legal requirements around tool licensing and need an OSI-certified open-source license or a formal commercial license agreement.
• You rely on the Substance Painter community for tutorials, preset packs, and troubleshooting — ArmorPaint’s community is much smaller.
• You need enterprise support contracts or SLAs.

Skip it (use Blender’s texture paint mode) if:

• You have basic texture painting needs and already use Blender — Blender’s built-in painter is free and the community is enormous [1].
• You don’t want to manage a second application.

Skip it (use Quixel Mixer) if:

• You’re deep in Unreal Engine and the Epic/Fab/Megascans pipeline, and free access to those assets outweighs the subscription-independence concern.

---

Alternatives Worth Considering

• Adobe Substance 3D Painter — the incumbent. Most tutorials, largest asset library, tightest integration with industry pipelines. Subscription only, no perpetual license, ~$49.99/month [1].
• Blender (texture paint mode) — free, truly open source, massive community. Less capable than dedicated texture painters for complex PBR work, but sufficient for many indie projects [1][5].
• Quixel Mixer — free with Epic account, solid for Megascans-based workflows. Future roadmap tied to Epic’s priorities.
• 3DCoat — perpetual license option available (~$99–$379 depending on edition), more mature feature set in some areas, stronger commercial clarity than ArmorPaint.
• Marmoset Toolbag — includes texture baking and some painting; primarily a presentation/rendering tool but relevant if you’re already using it for bakes.
• Krita — free, open source, GPL. 2D painting with some 3D support. Not a replacement for PBR texture painting, but listed because it appears in the same creative tools category [1][5].

For an indie game developer escaping the Substance subscription, the realistic shortlist is ArmorPaint vs 3DCoat. ArmorPaint wins on price model (one-time, source-available), GPU performance claims, and local AI. 3DCoat wins on license clarity, community size, and documentation depth.

---

Bottom Line

ArmorPaint occupies a specific niche that it fills well: one-time-purchase, GPU-native, PBR texture painting for artists who’ve had enough of Adobe’s subscription cycle. The GPU-first architecture is a real technical decision, not marketing — painting at 4K on integrated graphics and up to 16K on discrete hardware is a meaningful claim for artists working on mid-range machines. The local AI features (text-to-material, image-to-material, inpaint) are genuinely useful and the offline execution is a real advantage for studios with IP concerns.

The honest caveats are also real: the license situation requires verification before commercial use, the community is smaller than Substance’s, and independent reviews are sparse enough that you’re largely trusting the official documentation. For a solo artist or small indie studio already committed to dropping Adobe subscriptions from their toolchain, ArmorPaint is worth evaluating seriously. For a studio needing legal clarity, a certified license, or enterprise support, the calculus gets more complicated.

---

Sources

1. OMR Reviews — 3D Painting Software Category (39 products listed, competitive landscape overview). https://omr.com/de/reviews/category/3d-painting
2. OMR Reviews — Software & Tools A-Z (German) (product directory reference). https://omr.com/de/reviews/products
3. OMR Reviews — Software & Tools A-Z (English) (product directory reference). https://omr.com/en/reviews/products
4. oreznicek / delightful-creative-tools — Codeberg (curated open-source creative tools list; includes ArmorPaint in 3D painting category). https://codeberg.org/oreznicek/delightful-creative-tools

Primary sources:

• GitHub repository: https://github.com/armory3d/armorpaint (3,829 stars; license: NOASSERTION)
• Official website and feature descriptions: https://armorpaint.org
• Download and pricing page: https://armorpaint.org/download