Minecraft Resource Pack Validator

• The texture path doesn't match. A model's "layer0": "mypack:item/ruby" means the file must be at assets/mypack/textures/item/ruby.png. Don't include textures/ or .png in the id.
• Uppercase letters or spaces. Ruby.png and ruby sword.png are invalid resource locations, so Minecraft skips them.
• An undefined texture variable. A face using #side needs "side" in the model's textures or in a parent's.
• A broken animation strip. A 16×40 image can't be split into 16×16 frames. Use an exact stack of frames, or set the frame size in the .png.mcmeta.
• The whole pack is inside a folder. If you zip the folder instead of its contents, Minecraft can't find pack.mcmeta at all.

Since 1.21.4 Minecraft ignores model overrides and reads item definitions from assets/<namespace>/items/. If the validator says your overrides are ignored, run the pack through the CustomModelData converter, then validate again. Combining several plugin packs? Use the Resource Pack Merger first.

• Errors break something in game: a missing texture, an invisible item, a silent sound, or a pack that won't load.
• Warnings are likely problems, like overrides that only work on some versions or JSON only Minecraft's lenient parser accepts.
• Notes are information, such as which versions the pack targets.

When the errors are gone, shrink the download with the Resource Pack Optimizer.

That checkerboard is Minecraft's missing texture. It appears when a model points to a texture file that doesn't exist, a texture variable like #side isn't defined, the PNG is corrupt or not really a PNG, or an animated texture's size doesn't split into equal frames. The validator flags each of these with the file and the fix.

No. The validator runs entirely in your browser. The ZIP is read on your own computer and nothing is sent to our servers, so it's safe for paid or unreleased packs.

References are checked against the vanilla 26.3 asset list, so models and textures you use from vanilla count as present. The pack_format in pack.mcmeta is matched against every release since 1.6.1 to tell you which versions your pack targets.

Yes. From 1.21.4, Minecraft ignores model overrides and reads item definitions from assets/<namespace>/items/ instead. If your pack targets 1.21.4+ and still relies on overrides, the validator reports it and links the CustomModelData converter.

Minecraft only accepts lowercase letters, digits, underscores, dots, dashes and slashes in namespaces and file paths. A file like textures/item/Ruby Sword.png is skipped entirely, so anything that references it shows the missing texture.

No errors means none of the problems the validator knows about were found. It can't see plugin configs, server settings or shaders, and it checks vanilla parents by name only. Always test the pack in game on the version your players use.

No. It checks Java Edition resource packs. To bring custom Java items to Bedrock, use the Java to Bedrock converter.