Yet another Minecraft Bedrock Manifest Generator (with V2, V3 & Script API support)
Enable special engine features like ray tracing, chemistry, or scripts. Learn more
Required: Add a 'script' module under Behavior Pack Modules to enable Script API options.
Configure resource subpacks for different memory tiers. Learn more
Select which type of manifest you want to generate.
Choose the manifest format version, either V2 or V3.
V2 is the stable, widely-supported format.
V3 is currently in preview and includes support for pack settings (sliders, toggles, dropdowns) and uses "memory_performance_tier" for subpacks.
Note
Manifest V1 is not supported in this generator.
Fill in the manifest details.
For some version input fields, there is a toggle next to the input field that lets you toggle between a Semantic Versioning (SemVer) array (like [1, 0, 0]), a SemVer string (like "1.0.0"), or SemVer proxy objects.
Configure modules and Script API dependencies.
Add "data" or "script" modules for behavior packs. When you add a script module, the Script API dependency selector becomes available, letting you pick from all native Minecraft modules like @minecraft/server, @minecraft/server-ui, and more. Versions are updated in real-time.
Configure capabilities.
Capabilities declare special features your pack requires. Add capability identifiers (e.g., "chemistry", "script_eval", "raytraced", "pbr") to the capabilities array in your manifest. See the Capabilities section for details on each option.
Copy or download your generated manifest JSON file.
The Minecraft Manifest Generator generates manifest.json file for Minecraft Bedrock Add-Ons (behavior and resource pack), world templates or skin packs. This file tells the game essential information about the pack.
When developing behavior packs that contain scripts, you must specify the Minecraft Script API modules your code depends on. Native engine modules like @minecraft/server and @minecraft/server-ui allow your JavaScript/TypeScript code to interact with the game engine. This generator fetches the latest native module versions from multiple official Minecraft sources, and you can choose your required module and version to declare it under dependencies in the manifest.
Capabilities declare special features your pack requires or supports:
Subpacks allow you to select between different add-on 'configurations' in the game settings, with the intention of loading different set of texture resolutions on different memory capacities.
memory_tier property.memory_performance_tier property.The folder_name field in each subpack entry specifies the name of the folder to be used for this subpack.
For example, a subpack with folder_name set to subpack_low will be located in the following path:
ResourcePack
├── manifest.json
└── subpacks
└── subpack_low
└── textures
This creates a requirement on the capacity of memory needed to select the resolution. Each tier increases memory requirement by 256 MB.
The table below shows the memory tier alignment for each platform Minecraft supports:
| Memory Performance Tier | Platform | Memory Tier | Memory Range (GB) |
|---|---|---|---|
| 1 | Nintendo Switch | ≤11 | 2-4 |
| 2 | PS4, PS4 Pro, Xbox One, Xbox One S, ~60% Mobile | 12-16 | 4-5 |
| 3 | Xbox One X, Xbox Series S | 18-20 | 6-8 |
| 4 | Xbox Series X, PS5 | 24-28 | 8-12 |
| 5 | PS5 Pro, ~70% PC | ≥32 | >12 |
Important
This feature is still experimental and requires manifest V3 to use.
To ensure consistent performance across various platforms, Minecraft Bedrock enforces texture memory budgets measured in texels (1 pixel = 4 bytes of uncompressed memory). Devices automatically select the highest compatible subpack version matching their hardware tier without exceeding the budget limit:
| Memory Performance Tier | Add-On Budget | Resource Pack Budget | World Budget |
|---|---|---|---|
| Tier 1 (Low-end) | 150 MB | 300 MB | 750 MB |
| Tier 2 | 225 MB | 450 MB | 1 GB |
| Tier 3 | 300 MB | 600 MB | 1.5 GB |
| Tier 4 | 600 MB | 1.2 GB | 3 GB |
| Tier 5 (High-end) | 800 MB | 1.6 GB | 4 GB |
Check out Minecraft Texture Budgets Documentation & FAQ for more information.
Manifest V3 introduces dynamic, configurable in-game settings. Creators can define settings of type:
Below is a demo of the settings UI in-game:

In-game settings UI showing slider, toggle, dropdown, and label controls.
You can retrieve the value of pack settings in-game using Molang with the following queries:
query.get_pack_setting('ns:slider_name') - Returns the value of a sliderquery.is_pack_setting_enabled('ns:toggle_name') - Check if toggle is enabledquery.is_pack_setting_selected('ns:dropdown_name', 'dropdown_option_name') - Check if a dropdown option is selectedFor more details, see the official Minecraft Settings Documentation on Microsoft Learn.