What is an ORM texture?
An ORM texture stores three material masks in one image: ambient occlusion in red, roughness in green and metallic in blue. A material can read each channel separately.
Pack your maps
Select grayscale maps of the same dimensions. The red byte of each source pixel is copied into the chosen output channel, so use genuinely grayscale inputs. This tool never silently resizes mismatched maps. Export is an opaque, lossless PNG.
Split an existing texture
Choose Split ORM and select your texture. Download each channel as a separate grayscale PNG. This is useful for inspecting which mask is stored in each channel.
Does it generate missing texture detail?
No. Missing channels use the constant values shown beside the inputs. It does not generate AO or roughness from a color image. Engine import settings still matter: use the appropriate linear mask settings for your engine.
Is this suitable for 16-bit maps or HDR?
No. The browser canvas workflow produces 8-bit channels. Keep professional high-bit-depth masters in your original authoring software. JPG artifacts in source maps remain in the result.
Example: pack only an AO map
Select a 1024 × 1024 grayscale AO image and leave the other two fields empty. The output remains 1024 × 1024. Red contains AO, green is 128 everywhere and blue is 0 everywhere. These are fallback constants, not calculated surface details.
Why matching dimensions matter
A 2048 × 2048 roughness map cannot be packed with a 1024 × 1024 AO map. Prepare all inputs at exactly the same dimensions first. The image converter preserves proportions, so it will not force differently shaped maps into identical squares. Use your texture editor for cropping or resampling decisions.
Use PNG for masks where possible. Check your material's expected channel order before importing: a different packing convention will interpret ORM incorrectly. Splitting an ORM lets you inspect the three stored channels, but cannot recover detail already lost in a source image.