How to Fix Minecraft Resource Pack Not Loading on Your Server
If your Minecraft server resource pack is not loading — or players see the old pack after an update — this guide covers every cause and how to fix it. Most issues come down to four things: a wrong URL, a SHA1 mismatch, a stale UUID, or a broken pack.mcmeta. MinecraftPack fixes all four automatically.
Cause 1 — Wrong Resource Pack URL (Most Common)
Minecraft requires a direct download URL — a link that returns the raw ZIP bytes immediately. If the URL points to a share page (like a Google Drive share link ending in /view?usp=sharing or a Dropbox page), the server downloads an HTML page instead of the ZIP, and the pack silently fails.
How to tell: In your server console you may see Couldn't download server resource pack or no error at all — players simply don't see a pack prompt.
Fix: Use MinecraftPack (minecraftpack.net) to host your pack. It automatically generates the correct ?export=download Google Drive URL — not the share page. Copy the output URL directly into resource-pack in server.properties.
Cause 2 — SHA1 Hash Mismatch
The resource-pack-sha1 field in server.properties must exactly match the SHA1 hash of the ZIP file at the URL. If you re-upload the pack (even with the same filename), the file bytes change and the hash changes. A SHA1 mismatch causes Minecraft clients to reject the download silently.
How to tell: The server console logs Couldn't download server resource pack or clients see "Failed to download resource pack". The pack prompt may appear but the pack fails to apply.
Fix: Every MinecraftPack upload recomputes the SHA1 from the exact bytes that get hosted and outputs it in the config block. Re-upload on MinecraftPack and copy the new resource-pack-sha1 value. Never hand-edit the hash.
Cause 3 — Stale UUID (Players See Old Pack After Update)
The resource-pack-id field (required since 1.20.3) is a UUID that Minecraft clients use to identify a cached pack version. If the UUID does not change when you update the pack, clients continue serving their locally cached old version — even if the file at the URL has been updated.
How to tell: You updated the pack on the server, restarted, and rejoined — but textures/sounds are still the old ones. The pack prompt may not even appear because the client thinks it already has the correct version.
Fix: Re-upload the new pack version on MinecraftPack. A fresh UUID is generated automatically for every upload. Copy the new resource-pack-id into server.properties and restart the server. Every player will be prompted to re-download on their next join.
Cause 4 — Broken pack.mcmeta Structure
If pack.mcmeta is missing or placed inside a subfolder instead of at the ZIP root, Minecraft cannot read the pack. The pack may download successfully but fail to apply — players see no texture or sound changes despite accepting the prompt.
How to tell: After accepting the pack prompt, nothing changes. The pack selector in singleplayer shows the pack as incompatible or broken.
The required structure:
pack.mcmeta— at the root of the ZIP (not inside any folder)pack.png— optional, 64×64 iconassets/minecraft/textures/— texture overrides
Common mistake: Right-clicking a folder and choosing "Compress" creates a ZIP with a subfolder inside. Select all files inside the folder first, then compress the selection. MinecraftPack validates the upload and shows an error if the structure is wrong.
Cause 5 — Server Not Fully Restarted
Changes to server.properties only take effect after a full server restart. Running /reload or /stop followed by a start from within the console is sufficient, but some hosting panels have a "Restart" button that only sends SIGTERM and may not cleanly restart the process. Check that the server actually stopped and started again.
Some hosting panels (Pterodactyl, Apex, Shockbyte, Bisect) also have a web-based server.properties editor that saves to a different location than the one the server reads. If you edited via the panel, also check the raw file to confirm the changes are there.
Cause 6 — require-resource-pack Kicking Players
If require-resource-pack=true is set in server.properties, players who decline the resource pack prompt are kicked immediately. This can appear as a "connection lost" error with no obvious reason, leading players (and sometimes admins) to think the pack itself is broken.
Fix: If the pack should be optional, set require-resource-pack=false. If you want it required, add a clear join message (via a plugin or MOTD) telling players they must accept the pack to play on this server.
Quick Diagnostic Checklist
| Check | What to look for | Fix |
|---|---|---|
| URL type | Starts with https://drive.google.com/uc?export=download | Re-upload on MinecraftPack to get the correct URL |
| SHA1 length | Exactly 40 hex characters | Re-upload to recompute |
| UUID freshness | Changed after every pack update | Re-upload to get a new UUID |
| pack.mcmeta location | At root of ZIP, not in a subfolder | Repackage the ZIP correctly |
| Server restart | Full stop + start, not /reload | Restart cleanly via hosting panel |
| Console errors | "Couldn't download" or "Failed to hash" | Re-upload; check URL is accessible |
Frequently Asked Questions
Why is my Minecraft server resource pack not loading?
The most common causes are: wrong URL type (share link instead of direct download), SHA1 mismatch (hash doesn't match the file), stale UUID (clients serve cached old version), or broken pack.mcmeta (placed in a subfolder). MinecraftPack fixes the URL, SHA1, and UUID automatically.
What does 'Couldn't download server resource pack' mean?
This console error means the Minecraft server tried to download the resource pack from the URL in server.properties but failed. Check that the URL is a direct download link (not a share page), that the file is publicly accessible, and that the SHA1 in server.properties matches the file.
Why do players still see the old resource pack after I updated it?
The resource-pack-id UUID has not changed. Minecraft clients cache packs by UUID and won't re-download if the UUID is the same. Re-upload on MinecraftPack to get a fresh UUID, paste the new resource-pack-id into server.properties, and restart the server.
What is a SHA1 mismatch in Minecraft resource packs?
A SHA1 mismatch means the hash in server.properties does not match the SHA1 of the file at the resource-pack URL. Minecraft rejects the pack. Always copy the SHA1 directly from MinecraftPack after uploading — never compute it manually or copy from an old upload.
My resource pack downloads but nothing changes — why?
Most likely pack.mcmeta is in a subfolder instead of at the root of the ZIP. Minecraft downloads the file but cannot parse the pack structure. Repackage the ZIP: select all files inside the pack folder, then compress the selection (not the folder itself).
Can I fix resource pack issues without reuploading?
If the SHA1 or UUID is wrong, you must re-upload to get new correct values — there is no safe way to manually edit the hash to match a different file. If only server.properties needs updating (like changing require-resource-pack), you can edit that file directly and restart.