What is bedrock-tools.dev?

Free web tools for Minecraft: Bedrock Edition creators, made by the Owls Cubed studio. No accounts, no paywalls - pick a tool and go.

Tools

• Search Samples - search any bedrock-samples version by file name and file contents, filter by type, preview textures (PNG/TGA), view .geo.json models in 3D, listen to sounds (including FSB), and download single files, a selection, or the whole resource_pack / behavior_pack as one zip.
• Resource pack checker - upload a .zip and check it against vanilla bedrock-samples: find vanilla PNGs hiding inside, lint the pack (long paths, broken JSON, manifest issues, missing texture refs) and see which vanilla files it doesn't touch.
• Addon integrity - upload a behavior or resource pack and resolve its whole reference graph (client entities → geometry, animations, render controllers, textures; sound_definitions → files). Broken links are reported and vanilla bedrock-samples references are recognised, so only real problems show up.
• Path length audit - list every file whose path exceeds the 80-character limit that Bedrock consoles enforce, measured from the pack root.
• Pack merger - combine two or more resource packs into a single downloadable pack, with a conflict report and special .material handling that merges the material objects instead of letting one pack overwrite the other.
• Geometry viewer - drop a .geo.json model and orbit it in 3D (drag to rotate, scroll to zoom, toggle 3D/Text, switch between models), and add a .png/.tga texture to preview it mapped onto the model. Also available inline in Search via the 👁 button on any model file. It’s a quick preview only - for real modelling and texturing use Blockbench.
• Version diff - compare two bedrock-samples versions: new and removed registry IDs (blocks, items, entities and more - copy their typeIds), plus every added, removed or changed file with line-by-line diffs and a zip of all changed files.
• File history - browse a bedrock-samples version's file tree and track how any file changed across versions, with per-version downloads.
• Sound explorer - browse sound events of a bedrock-samples version, see which files each event resolves to and play them in the browser.
• Registry browser - searchable tables of all block, item, entity, effect and other IDs from a bedrock-samples version, with diffs between versions.
• Molang playground - type a Molang expression and instantly see the value it evaluates to, with an editable variable environment and syntax-error checking. Runs the real bridge-core Molang engine locally in your browser.
• Archive diff - upload two archives of your own and see exactly what differs between them, down to individual lines.
• Manifest generator - a linked BP + RP manifest pair with fresh UUIDs, optional script modules and texts/*.lang localization.
• Useful links - a curated directory of external references: official Microsoft Learn docs, the scripting-API changelog, format-version guides, sample repositories and creator tools like Blockbench, Snowstorm and bridge.

Where the data comes from

All vanilla data comes from Mojang's official bedrock-samples repository. New game versions are picked up automatically every hour.