PVPRP
Fix a Minecraft resource or texture pack that is not showing up. Check Java .zip files, Bedrock .mcpack imports, folders, pack.mcmeta, and version errors.
Tutorial
If one of these appears in-game, your Java folder is correct and the broken pack is probably packaged wrong. Bedrock users should follow the .mcpack steps below.
If your Minecraft texture or resource pack is not showing up, the file is usually in the wrong game folder, missing its real .zip extension, inside an extra folder, or made for Bedrock instead of Java. For Java Edition, start with the Open Pack Folder button in Minecraft so you know you are using the correct game instance.
This is one of the most common texture pack problems. The good news is that the fix is usually simple. You do not need to reinstall Minecraft or delete your worlds. Work through the checks below in order and your pack should show up again.
In Java Edition, open Options → Resource Packs → Open Pack Folder and place the pack there. This is safer than guessing the path because Prism Launcher, Modrinth App, CurseForge, and other launcher profiles can each use a different Minecraft folder.
Press Win + R, paste this, and press Enter.
%appdata%\.minecraft\resourcepacks
Open Finder, choose Go to Folder, and paste this.
~/Library/Application Support/minecraft/resourcepacks
Open this folder in your file manager. Hidden files must be visible.
~/.minecraft/resourcepacks
pack.mcmeta is directly inside it. If you zip it again, zip the pack contents instead of wrapping them in one more outer folder.
Java accepts a correctly built folder or a real lowercase .zip. Show filename extensions and check that the download is not pack.zip.txt, pack.zip.html, pack.zip.zip, .rar, or .7z. If Finder calls it a Document, the name is a random ID, or it has no .zip ending, Minecraft may ignore it. If the archive opens normally, add the .zip extension. If it will not open, download it again.
If opening the folder shows another folder before pack.mcmeta, Minecraft may not detect it. The pack files need to be at the top level.
Java usually uses .zip. Bedrock usually uses .mcpack. Renaming a Java zip to .mcpack does not convert it, and a Bedrock file will not show up in Java's resource pack menu.
Close the resource pack screen and open it again. If needed, restart Minecraft after moving the file.
Do not place a Bedrock pack in Java's resourcepacks folder. Open the real .mcpack file so Minecraft imports it, then open the world's Resource Packs → My Packs screen and activate it. A custom Bedrock pack also needs a valid manifest.json at its root.
If Minecraft says the import succeeded but an updated pack does not replace the old one, the creator may need to increase the version in manifest.json. Follow the full Bedrock installation guide for Windows, phone, tablet, and console limitations.
Open the zip or folder and look at the first level inside it. A normal Java resource pack should usually contain files and folders like this:
pack.mcmeta and an assets folder at the top level. pack.png is optional. Make sure the metadata file is not really named pack.mcmeta.txt and contains valid JSON. If those files are hidden inside another folder, move that inner folder or use a correctly packed zip.
Do not extract it yet. Just open it to inspect what is inside.
If pack.mcmeta is buried inside another folder, Minecraft may ignore the pack.
Put the actual pack zip or correctly structured folder into resourcepacks.
Go back to Minecraft and reopen the resource pack menu to force a refresh.
If the pack is in the correct folder but still does not appear, open the Resource Packs screen once, close Minecraft, and inspect .minecraft/logs/latest.log. Search for the pack filename near the bottom of the log.
min_format, or max_format errors point to an invalid pack.mcmeta for that game version. Changing metadata can make Minecraft recognize a pack, but it does not automatically convert older textures or models.
If Minecraft shows a red warning, it has already detected the pack. That is different from the pack being absent from the list. The warning usually means the pack format does not match your game version, and many PvP packs still work fine on newer versions.
If the pack appears in the menu but has a warning, try enabling it. If textures look normal in-game, you are fine. If textures are missing or broken, search for a pack made closer to your Minecraft version.
That means Minecraft recognized the pack, so the folder and zip are probably fine. Custom skies are not a normal vanilla texture feature and may need OptiFine or another compatible skybox mod. Use the custom sky troubleshooting guide for the correct client settings and mod checks.
If your current pack is broken, try a different Java pack from PVPRP. Start with popular 16x or PvP packs because they are usually easier to run and test.
Join Now
