Editor · Minecraft · Local browser workflow
Skin editor
/minecraft-skin-editor
Open resourcePixel editing workspaces for supported game formats
Compare local Minecraft skin and Roblox Classic Clothing editors by canvas, model, layers, touch workflow, input, and PNG output.
11 matching resources
Editor · Minecraft · Local browser workflow
/minecraft-skin-editor
Open resourceEditor · Minecraft · Local browser workflow
/minecraft-skin-editor-3d
Open resourceEditor · Minecraft · Local browser workflow
/minecraft-skin-editor-2d
Open resourceEditor · Minecraft · Local browser workflow
/minecraft-skin-editor-mobile
Open resourceTool · Minecraft · Local browser workflow
/tools/minecraft-skin-color-replacer
Open resourceTool · Minecraft · Local browser workflow
/tools/minecraft-skin-tint
Open resourceEditor · Minecraft · Local browser workflow
/minecraft-cape-editor
Open resourceEditor · Roblox · Local browser workflow
/roblox-skin-editor
Open resourceEditor · Roblox · Local browser workflow
/roblox-shirt-maker
Open resourceEditor · Roblox · Local browser workflow
/roblox-pants-maker
Open resourceEditor · Roblox · Local browser workflow
/roblox-tshirt-maker
Open resourceThis skin editors directory lists the working pixel-editing pages available on SkinEditor.org. Search by format or filter the cards to Minecraft or Roblox. The correct editor is determined by the file you need to produce, not by a generic promise to edit every kind of game skin.
Minecraft editors work with the game’s character texture layout. Roblox editors in this directory focus on Classic Clothing images: Shirt, Pants, and T-shirt. They do not create Layered Clothing meshes, cages, rigs, or accessories. Establishing that boundary before editing prevents a flat PNG canvas from being mistaken for a 3D production tool.
The main Minecraft Skin Editor combines a 2D UV canvas with an interactive model preview. It supports Classic and Slim arm intent, base and overlay visibility, body-part controls, drawing, erasing, fill, color sampling, history, local draft recovery, PNG upload, and download. The document remains a 64×64 RGBA image throughout the normal workflow.
The 3D page emphasizes live model inspection and rotation while preserving access to precise pixel controls. The mobile page uses the same valid skin document and editing engine but presents guidance for touch input, smaller screens, browser downloads, and the limits of phone file handling. These are purposeful entry points rather than three unrelated editors.
Classic and Slim do not merely change a label. Classic arms use four-pixel-wide geometry; Slim arms use three-pixel-wide geometry with different UV usage. Select the intended model before detailed sleeve work and confirm the result in the 3D preview.
The Shirt Maker opens a native 585×559 RGBA canvas with local import and PNG output. It supports pixel drawing, erase, fill, undo, reset, transparent areas, and visible zoom. The canvas size is a necessary outer property, not a complete Shirt surface map.
Use current authorized Roblox documentation for exact panel placement. Keep seam-sensitive details away from uncertain borders until the layout has been tested in Studio. A browser editor can preserve pixels and dimensions; it cannot remotely prove how every avatar configuration will display them.
The Pants Maker uses the same outside dimensions as a Classic Shirt but a different semantic destination. It provides a focused Pants workspace so instructions, checks, and next steps do not imply Shirt mapping merely because both images are 585×559.
Plan waist, leg, side, and back continuity with an appropriate reference. Export a new PNG, run the Pants checker, inspect transparency, and test in Studio. Relabeling a Shirt file as Pants does not rearrange its regions.
The T-shirt Maker creates a square graphic for the torso front. It is suited to badges, emblems, logos, and front-facing art. It does not wrap sleeves, sides, or the back like a Classic Shirt.
The workspace can place and scale a local image, add drawing changes, preserve transparency, and export a square PNG. Choose it when the desired result truly is a front graphic, not as a shortcut for wraparound clothing.
Start blank when the design is original and the target format is known. Import an existing PNG when you own it or have permission to modify it and want to correct colors, transparency, details, or composition. Inspect unknown files with a checker first.
Keep the source separate from downloads. Editing tools create new browser results, and local draft recovery is not a durable archive. Save milestone versions with descriptive names so an unsuccessful change can be reversed even after browser history is gone.
Use the smallest tool that matches the change. A brush changes selected pixels; erase changes alpha; fill replaces a connected area; color sampling reads an existing value. Undo and redo should describe document changes rather than unrelated interface actions.
Zoom changes the view, not the stored pixel dimensions. Crisp enlarged squares do not mean the exported file is larger. Conversely, a browser may visually smooth a preview without changing the source. Validate the downloaded PNG when dimensions are important.
Selected files remain in browser memory and are not sent to an image upload service. There is no account, public project, database-backed history, or community gallery. Local storage may hold a recoverable draft on the same device when the editor clearly says so.
The editors do not sign in to Minecraft or Roblox, publish assets, spend currency, or bypass moderation. Official importing, Studio testing, account eligibility, and rights remain separate responsibilities.
Use the main editor for the complete workflow, the 3D entry when model inspection is central, and the mobile entry for a touch-oriented setup.
No. They share outer dimensions but serve different mapped surfaces.
No. It creates a square front graphic.
Yes. Published editor workflows are anonymous and local-first.
Related paths
Continue with a compatible tool, template, or guide without starting the task again.