Fix black pixels, holes and arm strips caused by skin opacity or model mismatch.
Verification status: reference checklist. No claim of completed game-client import tests.
A skin texture has a base layer and a separate outer layer.
Transparent base pixels may appear black or create holes depending on edition and renderer; the outer layer can use transparency. A legacy 64×32 texture requires correct limb mapping when converted, not just an empty extension. Java and Bedrock rendering and import support differ; inspect the result in your target client.
Conceptual comparison: keep the base opaque; use transparency on the outer layer.
Step by step
Inspect the base and outer layers
General · Java and Bedrock; version varies
Fill unintended transparent pixels on base surfaces with opaque color; keep transparency only where intended on the outer layer.
Check the model
General · Java and Bedrock; version varies
Choose Classic or Slim to match arm texture layout. A mismatch can produce missing or dark arm strips.
Convert legacy textures correctly
General · Java and Bedrock; version varies
Use a converter that maps legacy limbs into a modern 64×64 layout, then inspect all faces.
Export and check again
General · Java and Bedrock; version varies
Export a PNG retaining alpha where appropriate. Preview the texture and verify in the target game client.
Questions & answers
Why are base pixels black?
Transparent base pixels can render black or as holes; fill the base surfaces with opaque pixels.
Can the outer layer be transparent?
Yes, transparency is used on the outer layer.
Why is there a black arm strip?
Check that the selected Classic or Slim model matches the texture layout.
Can I just resize a 64×32 file?
No. Legacy limb faces need to be mapped correctly to the modern layout.
Are Java and Bedrock identical?
Their rendering and file support can differ. Test the exported skin in the intended client.
MCSkinGen