Direct answer

A Java Edition server can offer a resource pack through a publicly reachable direct download URL. Configure the pack URL and optional hash in server.properties; hosting a file on a local disk path is not enough.

Recommended procedure

  1. Build a valid resource-pack ZIP with the appropriate pack metadata for the intended Minecraft version.
  2. Host the ZIP at a stable public HTTPS URL that responds with the file itself, not an HTML landing or login page.
  3. Compute the SHA-1 of the exact ZIP you uploaded; add its lowercase hexadecimal value to resource-pack-sha1 if your server version supports that field.
  4. Set resource-pack to the absolute URL in server.properties and optionally customize the prompt or requirement settings.
  5. Restart and connect with a fresh test profile or clear cached server packs to verify download.

Why this matters

The client must download the file from its own network; a URL accessible only from the server will not work. Updating the ZIP without updating its SHA-1 can leave players with a stale pack.

Practical example: Example: a Dropbox or file-sharing link can look valid in a browser but return a preview webpage rather than the ZIP bytes that Minecraft expects. Use a direct public download and verify the archive begins as a ZIP. A new file uploaded under the same URL still needs an updated hash in server.properties.

How to verify the result

  • Open the resource-pack URL in an incognito browser and confirm it downloads a ZIP.
  • Connect from a separate computer and watch whether the client offers and applies the expected textures.
  • If it fails, inspect redirects, MIME/download response, archive structure and the displayed client error.

Version and compatibility notes

  • Pack metadata format changes between Minecraft versions; validate it for the targeted clients.
  • Do not expose private URLs or temporary authenticated download links in public configuration.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000