Every new project is reviewed by a person before it is published. This page explains the review steps, the rules we apply, how long reviews take and how to appeal.
The category of a project cannot be changed after it is created. The subcategory can be changed at any time.
Creators see these labels on their dashboard and project pages.
Only you can see this project. Complete the checklist, then submit it for review.
Staff are reviewing this project. You can keep editing while you wait.
Staff asked for changes. Fix the listed items, then resubmit.
This project passed review. Who can see it follows its visibility.
This project was not approved. The decision is final unless an appeal succeeds.
Staff hid this project and its downloads from the public until it is fixed.
Staff removed this project. Its page shows a removal notice.
The page and downloads remain, but the project is not listed.
Automated checks are running.
In review, usually within 1 business day. Your current version stays available.
Available for download.
This version was not approved. Your previous version stays available.
Unpublished by you.
Removed by staff.
The file did not pass the upload checks and is not available.
Most reviews finish within 2 business days. These are targets, not guarantees; complex projects can take longer. A measured median replaces the target once enough reviews have been decided in the last 30 days.
| What | Target |
|---|---|
| First review of a project | Within 2 business days |
| Resubmission after changes | Within 2 business days |
| Update held for review | Usually within 1 business day. Your current version stays available. |
| Malware and child-safety reports | Acted on as a priority |
| Copyright notices | Usually within 3 business days |
| Other reports | Within 7 days |
| Appeals | Within 14 days |
| Fixing a live notice | 14 days by default; the project stays live meanwhile |
Every uploaded file goes through automated checks before a person sees it:
manifest.json is only a warning, and pack.mcmeta is never required);Automation can refuse an upload only for malware or for an archive that breaks the file rules. Everything else is held for a person to review. Final rejections, removals and strikes are always decided by people, and decision messages say when automation flagged something first.
External Utilities downloads open the publisher's own site. Those files are not mirrored or antivirus-scanned by Bedrock Graphics, and the site shows the destination address before it opens.
Staff choose the lightest step that fixes the problem. The steps below are a guide; staff confirm every action, and nothing is restricted automatically.
| Step | When | What happens | What you can do |
|---|---|---|---|
| Guidance | A minor issue on a published project | Nothing changes | Reply in the review thread |
| Changes requested | Before publication | The project stays unpublished and editable | Fix it, then resubmit |
| Live notice | A non-urgent issue after publication, such as missing credit or a wrong link label | The project stays live; only you see the notice | Fix it within 14 days, then mark it fixed |
| Version not approved | A specific update breaks the rules | That version cannot be downloaded; the previous live version stays | Upload a fixed version, or appeal |
| Hidden by staff | A serious or unfixed issue, or a credible malware or illegal-content report under investigation | The page and downloads are hidden from the public; you can still see them | Fix it, then request reinstatement, or appeal |
| Not approved or removed | Stolen content, malware, prohibited content, a valid copyright notice or repeated evasion | The project cannot be resubmitted; a removed page shows a short notice | Appeal, or send a counter-notice for copyright |
| Upload restriction | 2 active strikes | New projects and versions are blocked or fully reviewed for 30 days | Appeal |
| Suspension or ban | 3 active strikes, intentional malware, violent extremism, child-safety violations, evasion accounts or repeat copyright infringement | The account cannot sign in or upload, and its projects are hidden | Appeal by replying to the account email |
Signed-in members can report a project with the Report button on its page. Choose the reason that fits best (inappropriate content, copyright, malware or other) and describe what you found. Malware and child-safety reports are handled first; staff may hide a project while they investigate.
To report a copyright infringement, follow the copyright notice process. For anything else, use the contact form and include the exact project address.
The person who reported something is told the outcome, but not details about the creator.
Decisions cite these rule IDs and the policy version that applied. Link to a rule with its ID, for example #R-IP-1.
Upload only your own work, or work you have documented permission to share.
Credit third-party assets, bases and forks in the description, with a link to the original.
Your license must be compatible with any upstream license. No-Derivatives works cannot be modified; Non-Commercial works cannot be monetised.
No re-uploads, mirrors or "ports" of other creators' projects without permission.
Compiled Newb packs are CC BY-ND 4.0. Upload only your own variant, or an unmodified variant with the variant creator's permission. Credit Newb Shader and the variant creator.
Credit the preset author and BetterRTX. Do not re-upload another author's preset.
The license field must be set and accurate.
Valid copyright notices lead to removal. Counter-notices are handled as described on the copyright page. Repeat infringers lose upload access.
No malware, destructive or deceptive code.
No OS executables, scripts or installers, no password-protected archives, no more than 10,000 entries, and no nested archives that hide content.
No obfuscated, remotely loaded or self-updating script code.
Network or server-admin capabilities and any data sent off-device must be disclosed in the description, with the reason.
No collection of personal data, credentials or tokens, and no webhooks that exfiltrate chat or player data.
External Utility downloads must use https, point to the publisher's official site or release page, match the description, and must not bundle adware.
An update must not introduce behaviour unrelated to the project's description.
The pack imports and works as described on the stated platforms and game versions.
Empty, placeholder, vanilla-identical or trivially altered copies are not accepted.
Publish resolutions, editions and fixes as versions or subpacks, not as duplicate projects.
Updates use increasing version numbers and include a short changelog.
A manifest.json is recommended. A missing manifest is a warning, never a rejection by itself, and pack.mcmeta is never required.
The description explains what the pack changes, its requirements, install steps and known issues (at least 80 characters).
Projects must be in the correct category and subcategory. The category cannot be changed after creation.
The icon and any screenshots show this pack's real result. Screenshots are optional.
Game versions, platforms, RTX or Vibrant Visuals requirements and required tools are accurate.
Names are not misleading, do not impersonate, are not keyword-stuffed and are unique among your own projects.
Author and credits are accurate.
Files are hosted on Bedrock Graphics. External download URLs are allowed only for Utilities.
No ad-gated links, link shorteners or monetised redirects in any link field, description or download.
Content offered here is free to download. No paid-only, early-access-only or pay-to-unlock primary downloads.
Support links (Patreon, Ko-fi, Discord, YouTube, source) are allowed if they do not gate the download.
Links use https, go where their label says, and do not redirect to a different host.
Do not change files or links after approval to get around review.
Do not claim or imply official status or Mojang/Microsoft endorsement.
"Minecraft" may appear only as a secondary part of a name or description. No imitation of the Minecraft logo.
No redistribution of the game, game clients, modded APKs, unlocked builds, Marketplace content or bulk vanilla game files.
No selling, play-to-earn, NFT or crypto gating.
Content must be suitable for Minecraft's audience (see the prohibited content rules).
Modified shader binaries and edited vanilla textures are accepted as resource or preset packs, but not as complete game-file dumps.
No sexual content or nudity.
No hate, harassment or discrimination.
No gore or shock content beyond typical Minecraft violence.
No violent extremism or terrorism.
Any sexualisation of minors leads to immediate removal, a ban and a report to authorities.
No gambling, drugs or weapons trade, or other illegal content.
No personal data or doxxing.
No spam, deception, impersonation, or faked or manipulated stats, ratings or downloads.
Do not evade review, for example by deleting and recreating after a decision or resubmitting the same content as a new project after "Not approved".
No alternate accounts used to evade a restriction.
No abusive conduct toward staff or users in moderation threads or comments.
When the rules change, the policy version and effective date at the top of this page change too. Decisions keep the version that applied when they were made.