Popular tools
Start with frequently used creation and checking workflows.
Create, upload, edit, check, and download pixel skins without installing software. Your image stays in your browser, and no account is required.
Tool directory
One shared pixel engine supports focused workflows. Each indexed page will have its own input rules, output, examples, and purpose.
Draw and erase exact pixels on a responsive 64 × 64 local canvas.
Open toolOpen a local PNG for a model-aware preview without publishing the file.
Open toolInspect a standard file before editing and preserve its exact pixel dimensions.
Open toolConvert legacy, HD, Classic, and Slim files with explicit local presets.
Open toolInspect every mapped face with Classic or Slim geometry and layer controls.
Open toolExplore resources
Move directly to a focused tool, converter, template, guide, diagnostic, or newly released workflow.
Start with frequently used creation and checking workflows.
Change dimensions or model layouts with explicit output rules.
Download first-party blank and guided design files.
Learn dimensions, creation steps, and platform-specific workflows.
Diagnose import, size, and blurry-output problems.
Try the latest local model, conversion, and layer utilities.
Edit accurate 64 × 64 skins, then use dedicated checker, converter, layer, viewer, model detector, and avatar workflows.
Create, resize, recolor, inspect, and preview Classic T-shirt, Shirt, and Pants files with dedicated Roblox dimensions and rules.
Simple workflow
Create a transparent document or choose a valid 64 × 64 PNG from your device.
Use exact pixel tools, color control, undo, redo, and local recovery.
Review the result on a model-aware 3D preview with layer and body-part controls.
Export a clean PNG locally with no watermark or cloud project.
SkinEditor.org is a free online skin editor for people who want to make a new pixel character, adjust an existing design, check a file, or prepare artwork for a game avatar. The goal is simple: open the tool, start drawing, and download the result without creating an account. The editor currently provides a local 64 × 64 PNG workspace with a pencil, eraser, color picker, undo, redo, local draft recovery, upload, and download. Every pixel operation happens in the browser. Your image is not sent to an upload API, added to a public gallery, or attached to a user profile.
This workflow is especially useful when you already have a Minecraft-compatible skin and only need to change a few details. You can upload the PNG, replace colors pixel by pixel, erase unwanted areas, recover a draft after refreshing the page, and export another PNG. Starting from a blank transparent canvas is also supported. The first editor milestone focuses on reliable local editing before expanding into more advanced model previews, body-part controls, format conversion, and platform-specific checkers.
The working editor is designed around the most common skin-editing tasks rather than a complicated design application. Use the pencil to add exact color pixels, switch to the eraser when an area should become transparent, and use undo or redo when an edit does not look right. The canvas uses nearest-neighbor rendering so pixel edges stay sharp instead of becoming blurry. A 64 × 64 source file remains 64 × 64 when downloaded; the enlarged workspace is only a visual zoom that makes individual pixels easier to select.
Uploading is intentionally strict. The current workspace accepts PNG images that are exactly 64 × 64 pixels. Rejecting unsupported dimensions protects the source document from accidental resampling and makes the result predictable. Dedicated converters for legacy 64 × 32 files, high-definition 128 × 128 files, Classic and Slim arm layouts, and Roblox clothing templates belong in separate tools because those jobs have different inputs and validation rules. Keeping these tasks separate also gives each page a clear purpose instead of pretending one generic canvas can safely handle every game format.
Begin by opening the editor. Choose New Skin for a transparent 64 × 64 document, or choose Upload PNG to work from a file stored on your device. Select the pencil and a color, then draw directly on the enlarged pixel canvas. Dragging paints a continuous path, while a short click changes one pixel. Choose the eraser to remove pixels and restore transparency. Undo stores the document state from the beginning of a drawing gesture, so a mistaken stroke can be reversed as one action. Redo restores an action that was just undone.
The editor saves one anonymous draft in local browser storage. If you refresh or return on the same browser, the draft can be restored automatically. This is a convenience feature, not cloud storage: another device will not see the project, clearing browser site data removes it, and there is no account synchronization. When the design is ready, choose Download PNG. The browser creates the file locally and uses a timestamped filename so repeated exports are easier to distinguish.
Minecraft is the first fully planned platform because its common character skins use a compact pixel atlas that works naturally in a browser editor. Standard modern skins are usually represented as 64 × 64 PNG files with body faces arranged in specific regions. A visual design can look correct on a flat image but still map incorrectly if pixels are placed on the wrong arm, leg, head, or overlay region. For that reason, the broader Minecraft tool set is being built as connected but distinct workflows: an editor for drawing, a checker for diagnosing file problems, converters for known layout changes, and a 3D viewer for checking how the atlas wraps around a model.
Classic and Slim models also need separate treatment. Their arm widths are different, so converting between them is not merely changing a label. Future model-aware tools will identify the relevant texture regions, preview the result, and explain where a conversion can lose or invent pixels. Java, Bedrock, legacy, and high-definition workflows will receive their own compatibility notes rather than sharing vague instructions. Until those validators are finished, the live editor clearly limits itself to a standard 64 × 64 PNG workspace.
Roblox Classic Clothing tools remain in development as a separate workflow rather than being presented as the same format as a Minecraft skin. The planned work covers focused T-shirt, Shirt, and Pants workflows, template-aware checks, image utilities, and model previews. Their template regions and preview behavior differ from a 64 × 64 character atlas. Layered Clothing is more complex again because it involves 3D meshes, rigging, skinning, cages, and platform validation. A flat pixel editor cannot truthfully claim to complete that entire pipeline.
The Roblox roadmap therefore keeps its document model, template mapping, checker, and preview separate from the live Minecraft editor. Pages may describe the intended task and current limitations, but the homepage continues to mark the tool family as In development until its complete launch checklist is accepted. This distinction matters: a Shirt template should not be validated with Minecraft dimensions, and a Minecraft PNG should not be described as a ready-to-upload Roblox Layered Clothing asset.
No registration is required to use the local editor. SkinEditor.org does not need your name, email address, password, birthday, payment details, or avatar username for the current drawing workflow. The tool does not create a public copy of uploaded artwork. Draft recovery uses storage controlled by your browser, and the final file is produced through the browser download process. This reduces the privacy, copyright, and moderation risks that come with a public skin-hosting community.
The site may eventually display contextual advertising to support free operation, but ads must remain visually separated from upload, download, undo, and drawing controls. Google Analytics loads with the website and measures page views, navigation, and a small set of editor milestones such as starting, making a first edit, exporting, resuming a draft, or encountering a known error. These events never include image pixels, filenames, chosen colors, or draft contents. The privacy policy is kept aligned with the actual data flow rather than describing account and payment systems that do not exist.
Use the main skin editor when the source is already a 64 × 64 PNG and the goal is to draw or erase pixels. Use a checker when you are unsure why a game rejects a file, when transparent holes appear in a base layer, or when the model type is unclear. Use a converter only when the input and output formats are known, such as legacy-to-modern dimensions or Classic-to-Slim arms. Use a viewer when you need to inspect the front, back, sides, and overlay without changing the texture. Use a platform template tool when making Roblox clothing or another format that is not a Minecraft skin atlas.
Separating these intents makes the site easier to use and improves accuracy. It also means every future SEO page must earn its place with a real tool, a distinct preset, an original template, or a verified solution. Pages will not be published merely because “maker,” “creator,” and “editor” are similar phrases. The current editor is the first usable foundation: anonymous, local, focused, and ready for progressively more capable platform adapters.
Yes. The current browser editor is free and does not require an account, subscription, credits, or payment information.
No. The live 64 × 64 editor decodes, edits, stores, and exports the image in your browser. There is no skin upload API or public gallery.
Use a PNG file that is exactly 64 × 64 pixels. Other dimensions need dedicated converters so that pixels are not silently stretched or discarded.
The workspace uses pointer events and a responsive layout, so it can be used with touch. More advanced mobile gestures, 3D preview, body-part focus, and platform-specific tools will be added and tested separately.
No. SkinEditor.org is an independent tool. It is not an official product of, approved by, or associated with Mojang, Microsoft, or Roblox. Third-party names are used only to describe compatible formats and workflows.
Uploads, drawing, draft recovery, and PNG export happen on your device. There is no account database, cloud project, or public skin gallery behind the editor.