bridge.

Overview

bridge. is a Minecraft Bedrock Add-Ons IDE for creators who want a workspace dedicated to packs and worlds rather than a general-purpose code editor. Its strongest case is bringing project setup, editing, previews and in-game syncing into one tool; mobile users must download their project to fully save progress.

It creates behavior packs, resource packs, skin packs and world templates with the required files and configuration. Projects live outside Minecraft’s com.mojang folder by default, helping keep source work separate from the game’s installed content and safer if Minecraft is uninstalled. When ready, bridge. can sync supported packs and worlds to that folder.

Text and tree editing offer different routes through project data. The tree editor is suited to users with limited JSON knowledge, while the text editor supplies schema validation and syntax feedback. Dynamic completions and validation account for format versions and experimental toggles, which is useful when building for different Bedrock targets.

Key features

• Pack and world projects: Create behavior packs, resource packs, skin packs and world templates with their setup handled by the IDE, rather than assembling the basic project structure yourself.
• Text and tree editors: The tree mode can help newcomers avoid syntax errors; text editing provides schema checks and points out syntax problems for users who prefer direct file work.
• Previews without Minecraft: Inspect models, textures, animations, collision boxes, entity seats and particle effects without loading the game. That makes iteration less dependent on repeatedly opening Minecraft.
• Dash compiler and extensions: The built-in Dash compiler supports compiler plugins. An extension API and store also accommodate community tools, editors, viewers, presets and themes, giving experienced users room to tailor the workspace.
• Import, export and syncing: Import .mcaddon and .mcpack projects, and export .brproject, .mcaddon, .mcworld and .mctemplate formats. Syncing sends behavior packs, resource packs, skin packs and worlds to Minecraft’s com.mojang folder.
• GitHub-friendly projects: The project structure can be used with GitHub for collaboration and version control, a practical fit for teams or creators who want tracked changes.
• Offline web app: The maker says the installed web app works offline and behaves like a native app. On mobile, however, the browser lacks an API needed to fully save work, so users must download the project to preserve progress.

Pricing

bridge. is free and open source under the GPL-3.0 License. There is no paid tier or trial to weigh against a free-plan cap, so it suits creators who want a dedicated Bedrock workflow without a software subscription. The trade-off is practical rather than a published quota: mobile users need to download projects to completely save progress.

Platforms

bridge. is available on the web, Windows, macOS, Linux, iOS and Android. The wide platform range is useful for creators switching between desktop and mobile, though the mobile save requirement makes phones and tablets a less seamless place to do sustained project work than the platform list alone suggests.

Who it's for

Choose bridge. if you make Minecraft Bedrock Add-Ons and want project scaffolding, structured editing, previews and Minecraft syncing in a single IDE. It is particularly suitable for newer creators who may benefit from tree editing, and for more experienced makers who value compiler plugins, extensions, multiple version targets or GitHub-based collaboration. It is less suitable for mobile-first work that depends on browser saving, or for someone seeking an editor not centered on Bedrock pack and world creation.

Pros and cons

• Pro: Project setup covers four Bedrock pack and world types, reducing the initial configuration work.
• Pro: Previews span models, textures, animations, collision boxes, entity seats and particles without requiring Minecraft to be loaded.
• Pro: The tree editor offers a way to work with structured data without extensive JSON knowledge, while text mode provides validation.
• Pro: Projects stay outside the game folder by default, and can later be synced into Minecraft when ready.
• Con: Mobile users have to download projects to fully save progress, adding a manual step to the workflow.
• Con: Its focus is specifically Minecraft Bedrock Add-Ons, so it is not the right fit for unrelated software development.

Alternatives

Minecraft Add-on Editors is a useful next stop for readers comparing tools in this category.

• Blockbench is another free option across web, mobile and desktop platforms; choose it if you want an alternative rather than bridge.’s Bedrock IDE workflow.
• Minecraft Launcher is free to download, but accessing games requires ownership or a time-limited demo. Choose it to launch Minecraft, not to replace a dedicated Add-Ons IDE.
• Visual Studio Code is a free editor for web and desktop platforms. It may suit readers looking for a broader editor, while bridge. is purpose-built for Bedrock Add-On projects.
• AddonCrate Studio is a free alternative for desktop and extension platforms.
• Bedrocken is a free VS Code extension that requires VS Code ^1.87.0; choose it if you prefer working through that editor.
• Blockception Minecraft Bedrock Development is a free VS Code extension for Minecraft Bedrock Addons and Minecraft Education Edition, making it relevant if Education Edition is part of your work.
• Crafty Craft is a freemium option for Android, iOS and macOS, with a three-day free period before its Go Pro Monthly plan costs $15.99 a month. Consider it if you prefer a mobile-oriented option and are comfortable weighing a paid premium plan.
• Addons Maker for Minecraft PE offers a free ad-supported plan with core editors, templates and export, plus a trial followed by a $3.99 a month premium plan. It may fit readers seeking a mobile add-on maker with templates and an export option.

Verdict

bridge. is a strong choice for Bedrock Add-On creators who want project setup, editing, previews and syncing in one free, open-source IDE. Its breadth is the main reason to choose it; look elsewhere if mobile browser saving is central to your workflow, since completely saving progress there requires a download step.