Table of Contents Show
For those who don’t know the tool: MechaPaint is a standalone Windows and macOS application for texturing existing 3D assets. Models come in from a DCC, painting and material work happen directly on the mesh, and textures or geometry return to modelling, game-engine, visualisation or 3D-printing workflows. Version 2.0 expands that middle stage with six-channel PBR authoring, physical-paint matching, photograph-derived geometry, fur tools and optional AI-assisted retouching.
More workshop than paint package
MechaPaint 2.0 makes most sense when treated as a production workshop rather than a conventional texture painter with an unusually long toolbar. The application spans direct mesh painting, six-channel PBR authoring, photo-derived materials and geometry, real-world paint matching, fur generation, engine-oriented export, 3D-print preparation and optional image processing through local or external AI services.
The common thread is the asset itself. MechaPaint does not attempt to become the DCC that owns the scene. Geometry can remain in Blender, Maya, LightWave or another modelling package, animation can remain where it already works, and the game engine can continue doing what game engines are generally happiest doing, which is rejecting the material setup five minutes before a build.
The artist brings an asset into MechaPaint, works directly on its surfaces, then sends textures or geometry back downstream. Existing textures can become starting layers, material assignments become independently paintable parts, and the application’s own .mpaint project keeps the mesh, layer stacks, masks, references and text decals together without overwriting the original source files.
That separation is useful in iterative production. The model can change upstream while the paint work remains a separate production stage instead of becoming entangled with the application that created the geometry.
PBR without another noodle farm
The largest technical expansion is the PBR workflow. MechaPaint 2.0 works across base colour, normal, roughness, metallic, ambient occlusion and height. These channels can be enabled independently for painting operations, so the same brush system can change surface roughness without touching colour, add height without affecting metallic values, or alter several material properties together.
That is an important part of the application’s character. MechaPaint treats materials as things an artist paints rather than primarily as node graphs an artist engineers. The layer model stays familiar, while the PBR channels travel through the painting system underneath it.
Materials can also be loaded onto the brush as linked multi-channel content. Instead of separately managing colour, roughness, normal and height maps, the artist can paint the material as one coordinated operation.
The Material Depot integrates CC0 material libraries from ambientCG and Poly Haven, with 1K, 2K and 4K assets. A downloaded material can become a grouped set of colour, roughness, metallic, normal, ambient-occlusion and height layers, or it can be loaded as brush content.
Downloaded material information remains associated with the project, and MechaPaint can generate a _Credits.txt file beside exported textures. CC0 material does not require attribution, but keeping origin information around becomes useful once assets have been passed between enough people that nobody remembers whether Stone_17_final came from a library, a scan or Dave.
External PBR material folders can also be imported. MechaPaint attempts to recognise component maps from common naming conventions, including typical packages from services such as Fab and Megascans. Gloss information can be converted for roughness-oriented workflows, while packed ORM textures can be split into their respective channels.
The painting system itself stays layer based. Individual paintable sections have their own stacks with visibility, opacity, duplication, image import and merging. The brush uses continuous strokes rather than simply placing disconnected stamps, and pressure-sensitive tablets are supported.
Brush behaviour combines tip, texture and colour information. The wider toolset includes airbrush and spray behaviour, stamps, symmetry, clone-style work, fills, sanding, wear and detail operations. The result is more Photoshop-on-the-model than Houdini-for-the-material, which will either sound reassuring or deeply disappointing depending on how many node graphs are already open on the second monitor.
The paint store inside the colour picker
Real Paints is where MechaPaint stops looking like another 3D texture application. The database contains more than 13,000 real paint colours from 38 brands. These range from miniature and modelling paints to sprays and household colours, with brands including Vallejo, Tamiya, Citadel, Mr. Hobby, AK Interactive, The Army Painter, Scale75, Reaper, Rust-Oleum, Krylon and Sherwin-Williams.
Each paint entry includes the manufacturer’s catalogue identifier. Match The Brush takes the currently selected digital colour and searches the physical paint database for the closest alternatives. The matching process uses CIEDE2000 colour distance in Lab colour space and returns the 40 nearest paints. That makes the feature more than a branded swatch list. An artist can pick a colour on the digital model and obtain candidates that can actually be ordered, opened and applied to an object. And yes, for the 3D-printng crowd, this s amazing. Just sayin’
Brand and product-line filters narrow the search to paint ranges available in the workshop. Selected paints can appear as small jars in the viewport, and clicking a jar loads the corresponding colour onto the brush. The project Paint List records the physical products in use and can generate a shopping list grouped by brand and sorted by use.
Palette Match approaches the problem from the opposite direction. Rather than finding a physical equivalent for one colour, it remaps an entire painted layer to a limited collection of paints already available.
That collection can come from selected swatches, virtual paint jars or both. Intermediate shades can be approximated using Floyd-Steinberg style diffuse dithering or an ordered 8 x 8 pattern. Matching can operate in OKLab or RGB, with further controls for serpentine processing, faint-pixel cutoff, pattern spread and gradient endpoints.
The practical result is a digital surface that can be approximated with an actual finite set of paints. For miniatures, props and painted 3D prints, that is a much more useful concept than designing a perfect digital material that nobody can reproduce once the object leaves the screen.
A photograph is no longer just reference
MechaPaint’s image tools follow the same workshop logic. Photographs are not limited to floating reference panels. They can become material information, displacement or actual geometry. PhotoMesh converts one photograph into textured geometry. The generated result can remain as relief or become a closed solid. Depth can be adjusted, and the resulting object can pass through MechaPaint’s UV rebuilding workflow before export.
The quality still depends on the source. Even illumination and a near-square camera angle are preferable because shadows can become false depth and perspective distortion becomes part of the resulting geometry. Single-image reconstruction has not overturned optics. It has simply made them somebody else’s problem slightly later in the afternoon. LightMesh gives the process more direct control. It converts image brightness into height on a flat surface, with live Height and Blur controls. Further parameters cover inversion, normalisation, edge flattening, edge averaging, stair-stepping, resolution and texture-source selection.
The geometry does not have to remain continuous. LightMesh can also turn the image into square voxel-like cells or pointy-top hexagonal structures. The generated object keeps separate Original and Heightmap layers together with a visible overlay. Because that height information remains paintable, an artist can modify it with MechaPaint’s regular tools and rebuild the geometry afterwards.
Height also connects back into the PBR workflow. Data can move between LightMesh and the PBR Height channel, while Generate Normal from Height can create a new normal layer from the current height information without destroying normal work that already exists.
Photo Material takes the same concept in the other direction. A photograph can become the starting point for a six-channel material containing colour, normal, roughness, metallic, ambient occlusion and height. The 2.0 workflow includes de-lighting, perspective correction and tiling repair so the image is treated as source material rather than merely projected onto the model and wished good luck.
This is one of the better examples of how MechaPaint’s individual features connect. A photograph can provide material information, that information can become height, height can become geometry, and the result remains paintable throughout the process.
AI stays optional
MechaPaint’s AI tools sit beside the conventional painting system rather than underneath it. The local route connects to a ComfyUI server. MechaPaint can test the server connection, send a selected area through locally installed image models and workflows, and return the processed result to the painted asset.
The AI Brush workflow for 2.0 works on a selected square region of the model. MechaPaint captures the patch, sends it to the configured image service and projects the returned result back into the corresponding location. The instruction sent to the image system remains visible to the artist. This is useful both creatively and operationally because the operation is not hidden behind a generic “improve” button whose technical contribution consists largely of suspense.
The release supports two broad deployment approaches. One uses a user-supplied Google image-service API key with per-request billing. The other points the application at a local ComfyUI installation. The local route is the more interesting option for controlled production environments. Processing can remain on studio hardware, and the rest of MechaPaint does not require AI or an internet connection. The generative component is therefore optional rather than infrastructure the application refuses to function without.
Reload instead of repaint
The DCC workflow is built around file interchange rather than host plug-ins. MechaPaint can read common production and interchange geometry including FBX, OBJ with MTL, GLB, glTF, DAE, STL, PLY, 3MF, LWO, USD, USDA and USDC. Animation can be brought in through FBX, DAE, glTF, GLB and BVH when working with an already rigged model.
For LightWave users, LWO2 and LWO3 objects are read directly, covering files from LightWave 6 through current versions. LightWave surfaces become independently paintable parts inside MechaPaint. Raster input covers PNG, JPEG, PSD, TIFF, TGA, BMP, EXR and HDR. Photoshop ABR brush sets are accepted, raster images can become custom brush shapes, and installed TTF or OTF fonts can be used for text. More important than the list itself is how model revision works. A model can be edited upstream, saved over the existing source and reloaded into MechaPaint. Reload Model rebuilds the painted layers on the replacement geometry.
For iterative asset production, that is far more interesting than another supported extension. Artists can keep modelling and surface work as separate processes without assuming that topology becomes sacred the moment painting starts. The system still has sensible boundaries. USD, USDA and USDC are geometry input paths, not evidence of a full USD scene round trip. Likewise, reading a Blender or Maya export does not mean MechaPaint is attempting to preserve every application-specific shader, modifier or scene relationship.
Engine delivery is mostly plumbing
The engine workflow concentrates on packaging rather than integration. Texture output can be generated as merged content or per layer, and either per submesh or across the whole model. The 2.0 export system includes PNG and TGA output with presets for Unity URP, Unity HDRP, Unreal Engine, Godot, glTF, Roblox and Substance-oriented workflows.
Those presets handle the sort of naming and channel packing that nobody puts in a promotional trailer but everybody notices when it is wrong. Geometry can be exported through FBX, GLB, OBJ with MTL and STL. UVs can be rebuilt or combined, and orientation presets help prepare assets for specific destinations.
Roblox receives more dedicated treatment than a generic “game engine” checkbox. MechaPaint can prepare SurfaceAppearance PBR sets, classic Shirt, Pants and T-Shirt templates, R15 clothing, a 15-part Studio body kit and Dynamic Head assets.
Polytoria has its own clothing template support. Grass-card generation can produce assets aimed at Unity, Unreal and Godot, including colour, normal, translucency and packed texture data, wind-weight information and card meshes.
The licence is uncomplicated
MechaPaint runs on Windows and macOS. On Windows, the stated baseline is Windows 10 version 21H1, build 19043, or newer, with a 64-bit x86 CPU supporting SSE2 and graphics capable of DirectX 10, 11, 12 or Vulkan using supported vendor drivers. On macOS, Monterey 12 is the minimum. The universal application supports Apple Silicon from M1 onward as well as Intel x64 systems and requires Metal-capable graphics.
Ordinary painting does not require an account or internet connection. The commercial licence is perpetual. The regular price is $79 and there is a launch price of $39.50. One purchase covers Windows and macOS and includes one year of free upgrades. Builds received during that year remain usable permanently, and another payment is only required if the user wants upgrades released after that included period.
The free version has no time limit and exposes the full application, but texture exports are watermarked.
The interesting part is the overlap
MechaPaint 2.0 is most convincing when several of its workflows overlap. A photograph can become a material. Its height information can become relief. That relief can become geometry. The geometry can be painted. The digital colours can be matched to actual paints. The finished asset can be exported for a game engine or sent toward a 3D printer. If required, a selected region can be sent through local ComfyUI without turning the entire application into an AI front end.
A specialised character-texturing department with an established Substance pipeline may not need most of that. A freelancer, indie studio, model maker, prop department, visualisation artist or small team moving between digital and physical output has a clearer use case.
The risk is the same one faced by every expanding toolbox. More features eventually demand more interface discipline. MechaPaint is already broad enough that workflow organisation matters as much as whatever clever utility arrives next. For now, the tools still share a recognisable purpose: get an existing asset into the application, solve the surface or fabrication problem directly on it, then return the result to the rest of the pipeline without trying to take the pipeline hostage.
| Product | MechaPaint |
| App type | Standalone 3D painting and asset-preparation application |
| Platforms | Windows and macOS |
| Core workflow | Import an existing asset, paint or build material information directly on the mesh, export textures or geometry back into the production pipeline |
| PBR channels | Base colour, normal, roughness, metallic, ambient occlusion, height |
| Physical-paint workflow | More than 13,000 real colours from 38 brands, CIEDE2000 matching, restricted-palette remapping and paint-list generation |
| Photo workflows | PhotoMesh, LightMesh and Photo Material |
| Geometry workflow | Image-derived relief or solids, editable height data, normal generation, real-scale export |
| AI workflow | Optional local ComfyUI processing or external image-service processing |
| Model input | FBX, OBJ/MTL, LWO, USD, USDA, USDC, glTF, GLB, DAE, STL, PLY, 3MF |
| Animation input | FBX, DAE, glTF, GLB, BVH |
| Image input | PNG, JPEG, PSD, TIFF, TGA, BMP, EXR, HDR |
| Geometry output | FBX, GLB, OBJ/MTL, STL |
| Engine workflows | Unity URP, Unity HDRP, Unreal Engine, Godot, glTF, Roblox |
| Windows | Windows 10 21H1 / build 19043 or newer; x64 CPU with SSE2; DirectX 10/11/12 or Vulkan-capable GPU |
| macOS | macOS Monterey 12 or newer; Apple Silicon M1 or later or Intel x64; Metal-capable GPU |
| Input | Mouse or pressure-sensitive pen tablet |
| Internet requirement | Not required for ordinary painting |
| Licence | Perpetual, one-time purchase; one year of free upgrades |
| Launch price | $39.50 |
| Regular price | $79 |
| Free version | Full application with no time limit; exported textures are watermarked |
| Download | Windows and macOS |
| Documentation | MechaPaint Docs |
