Pack upload guidelines

Before you upload

A project can be submitted for review when it has all four of these:

• A description of at least 80 characters that says what the pack changes, what it needs, how to install it and any known issues (R-META-1).
• An icon that shows this pack (R-META-3). Screenshots are optional, but they help players decide.
• At least one version with its file, or for Utilities a link to the publisher's official release page.
• A license that matches any work you build on (R-IP-3, R-IP-7).

Upload only your own work, or work you have documented permission to share, and credit any bases, forks and third-party assets with a link to the original (R-IP-1, R-IP-2).

Accepted files

• Files are hosted on Bedrock Graphics. Only Utilities can link to an external download, and players see the destination address before it opens (R-LINK-1, R-SAFE-6).
• Archives must be checkable: no programs, scripts or installers, no password protection, no more than 10,000 entries and no archives hidden inside archives (R-SAFE-2).
• A manifest.json is recommended. A missing manifest is only a warning, and pack.mcmeta is never required (R-QUAL-5).
• Publish resolutions, editions and fixes as versions of one project, with increasing version numbers and a short changelog (R-QUAL-3, R-QUAL-4).

How to publish

1. Create the projectIt starts as a draft only you can see. Pick the category carefully: it cannot be changed later. The subcategory can.
2. Add the detailsFill in the checklist above and upload a version. Saving never sends the project for review.
3. Submit for reviewSelect Submit for review. Most reviews finish within 2 business days, and you can keep editing meanwhile.
4. Get a decisionStaff publish it, or ask for changes and name the rules involved. Fix them, then resubmit.

New versions of a published project are checked automatically, and new creators' versions are also reviewed by staff before they go live. Your current version stays available meanwhile. See How review works for the details.

Names, links and branding

• "Minecraft" can only be a secondary part of a project name, for example "Your Pack for Minecraft Bedrock" (R-MC-2). Do not claim or imply that a project is official (R-MC-1).
• Names describe the pack, are not stuffed with keywords and do not copy another creator's name (R-META-5).
• Downloads are free. No ad gates, link shorteners or monetised redirects in any link field, description or download (R-LINK-2, R-LINK-3).
• Support links such as Patreon, Ko-fi, Discord or a source repository are welcome, as long as the download does not depend on them (R-LINK-4).
• Links use https and go where their label says (R-LINK-5).

Not allowed

• Malware, destructive or deceptive code, and scripts that collect personal data (R-SAFE-1, R-SAFE-5).
• Re-uploads, mirrors or ports of other creators' projects without permission (R-IP-4).
• The game itself, modified game clients, Marketplace content or bulk game files (R-MC-3).
• Sexual content, hate or harassment, gore beyond typical Minecraft violence, and personal data about anyone (R-PROH-1 to R-PROH-7).
• Spam, impersonation, and faked ratings or downloads (R-PROH-8).

The full rule list explains each rule and its usual outcome. If you think a decision is wrong, you can appeal it once.