Export a Minecraft skin as a textured OBJ
This Minecraft skin OBJ exporter converts a modern 64×64 skin PNG into a simple textured player mesh. Open a local skin, choose Classic or Slim arms, and download a ZIP containing minecraft-player.obj, skin.mtl, and the unchanged skin.png.
The mesh is built from six separate rectangular parts: head, torso, right arm, left arm, right leg, and left leg. Every part has front, back, left, right, top, and bottom faces. Each face receives texture coordinates from the corresponding base-layer rectangle in the selected skin layout.
Everything runs in the current browser. The PNG is not uploaded, the OBJ is not generated on a server, and the exported model is not stored in an account or database.
What the exporter creates
OBJ is a text-based geometry format supported by many modeling, rendering, and conversion applications. The generated file declares vertex positions, texture coordinates, quad faces, six named objects, one material, and a reference to skin.mtl.
The MTL file defines a simple unlit-looking diffuse material and points to skin.png through map_Kd. Keep the OBJ, MTL, and PNG in the same folder after extracting the ZIP. Moving only the OBJ usually makes the importing application display a white model because the material and image can no longer be found.
The model uses skin pixels as spatial units. Its feet begin at Y=0, the legs reach Y=12, the torso and arms reach Y=24, and the head reaches Y=32. The body faces forward along positive Z. Applications may use a different up axis or scale convention, so import settings can rotate or resize the model without changing its UV data.
Classic and Slim geometry
Classic and Slim skins use the same 64×64 image size but different arm widths. Classic arms are four model units wide. Slim arms are three units wide. The exporter changes the physical arm boxes and reads the corresponding UV widths when Slim is selected.
Choosing the wrong model can stretch a three-pixel sleeve across a four-unit arm or read a transparent column that was not intended to appear. If the skin model is unknown, use the Minecraft skin model detector before export.
The head, torso, and legs are identical between the two presets. Each limb remains a separate object so an importer can select, rotate, hide, or reorganize it. The OBJ does not include a bone hierarchy, skin weights, animation clips, constraints, or an armature.
Base layer and overlays
This first reliable OBJ export maps the base skin layer only. The original PNG still contains hat, jacket, sleeve, and trouser overlay pixels, but the mesh does not create the slightly enlarged second set of boxes needed to display them.
That limitation is intentional. A correct outer-layer export needs additional geometry, careful depth offsets to avoid z-fighting, separate face UV mapping, and importer testing. Baking the overlay into the base texture would also be misleading because transparent and raised details behave differently.
Use the Minecraft skin layer viewer to inspect base and outer artwork before export. If an important hat, jacket, cuff, or hair detail exists only on the overlay, it will not appear on the current OBJ geometry.
UV mapping and image orientation
Minecraft stores body faces as rectangles in a texture atlas. OBJ stores texture coordinates as normalized values between zero and one. The exporter divides source pixel positions by 64 and reverses the vertical image coordinate so the top-left PNG convention maps to the bottom-left UV convention commonly used by OBJ importers.
Every face receives four independent texture coordinates. Vertices are also repeated per face rather than shared across the entire box. This produces a larger text file than a heavily optimized mesh, but it keeps the atlas seams explicit and makes the export easier to inspect.
Some applications flip textures vertically on import or interpret face winding differently. First confirm that the importer loaded skin.mtl and skin.png. If the texture is upside down, change the application’s image-orientation setting rather than editing the source skin destructively.
Importing the ZIP
Extract all three files into one directory. In Blender, an OBJ importer can load minecraft-player.obj; other applications may provide an Import or Open command. Confirm that material search paths include the extracted directory.
OBJ is a static exchange format. It is useful for still renders, blockout references, simple printing experiments, conversion tests, and moving the six cuboids into another tool. It is not a complete Minecraft entity, Bedrock geometry file, Java model definition, resource pack, or playable skin.
The source PNG remains the authoritative skin file. Do not replace it with a screenshot of the imported model. If artwork needs correction, edit the 64×64 source with the Minecraft skin editor, export a new PNG, and generate the OBJ package again.
For physical and in-game derivatives that do not need a mesh, use the Minecraft skin papercraft generator, Minecraft skin statue material planner, or Minecraft skin to totem converter. Each tool creates a different local output instead of relabeling OBJ data.
OBJ versus glTF
OBJ was selected for the first model export because its geometry and UV records are human-readable, the material reference is small, and the resulting ZIP can be checked with ordinary archive and text tools. A user can verify vertex counts, object names, face indices, and texture filenames without specialized binary parsing.
glTF 2.0 is better suited to structured scenes, modern physically based materials, compact buffers, and animation workflows. A reliable glTF export needs indexed binary buffer views, accessors, node transforms, material definitions, image handling, MIME declarations, and validation in independent viewers. A .gltf file may also depend on external .bin and PNG files, while .glb requires correct binary container alignment.
For those reasons this page does not relabel the OBJ as glTF or provide an unverified GLB button. glTF remains technically feasible, but it should be released only after schema validation and cross-viewer testing. OBJ is the current deterministic deliverable.
Privacy and responsible use
File decoding, geometry generation, UV calculation, MTL generation, ZIP assembly, and download happen locally. The site does not receive the filename, pixels, selected model, OBJ text, or archive.
Only export skins you created or have permission to use. Converting artwork to a 3D exchange format does not grant copyright, trademark, publicity, or commercial rights. Keep attribution and license requirements when moving a model into another project.
SkinEditor.org is independent and is not associated with Mojang or Microsoft. Minecraft names are used descriptively to explain the compatible texture layout. The model is a simple recreation from standard rectangular dimensions, not an extracted official game asset.
Frequently asked questions
Does the ZIP contain the texture?
Yes. It contains the unchanged uploaded file as skin.png, plus OBJ and MTL files.
Can I animate the model?
The six parts are separate objects, but there is no armature or animation. Add rigging in a 3D application.
Does it include the outer clothing layer?
No. The current mesh maps base-layer faces only.
Is OBJ the same as a Minecraft model file?
No. OBJ is a general interchange format and cannot be imported as a playable skin by itself.
Is glTF export available?
Not yet. It is feasible, but requires additional buffer, material, packaging, and cross-viewer validation.