Which Minecraft edition you have usually comes down to what you bought it on, not a choice you made on purpose. Buy on a PC through the Microsoft Store or minecraft.net, and modern purchases include both Java Edition and Bedrock Edition in one launcher. Buy on Xbox, PlayStation, Nintendo Switch, Android, iOS, or Fire TV, and you have Bedrock Edition only. Java Edition never left desktop: Windows, macOS, and Linux are still the only places it runs.
Which platforms run which edition
- Windows, macOS, and Linux run Java Edition through the Minecraft Launcher.
- Windows, Xbox, PlayStation, Nintendo Switch, Android, iOS, and Fire TV all run Bedrock Edition, tied to one Microsoft account across every device.
- A PC copy of Minecraft: Java and Bedrock Edition unlocks both, switchable from the same launcher.
- Realms, Minecraft Education, and most console retail copies are Bedrock only.
Everything below assumes you already know, or are about to find out, which one you're running. The two editions share a name and a block palette, and not much else under the hood.
Customization, mods versus add-ons and behavior packs
This is the split players misunderstand most, and it isn't a naming difference. Java's mod loaders, Fabric, Forge, and NeoForge, load Java bytecode straight into the game. A mod can rewrite rendering, add new items with full custom logic, replace vanilla systems outright, and reach anywhere the game's code reaches. That is also why a mod can crash a session, conflict with another mod's changes to the same system, or need a matching loader and Minecraft version before it will even load. Browse Java mods and check the loader-support notes on a page like Fabric API before adding anything.
Bedrock has no loader and no code injection. Its add-ons pair a resource pack, what things look and sound like, with a behavior pack, what things do, both written in JSON against a sandboxed scripting API that Mojang controls. An add-on can reskin mobs, script new behavior for existing entities, and add custom items and blocks, but it cannot touch the renderer, rewrite core systems, or do anything the scripting API doesn't expose. Packs live in the Bedrock installation's %appdata%\Minecraft Bedrock\users\shared\games\com.mojang folder, split between resource_packs and behavior_packs. Better on Bedrock is a good example of how far a well-built add-on can push that sandbox. Browse Bedrock add-ons to see the range.
Neither system replaces the other. Java mods reach deeper but are more fragile between versions and loaders. Bedrock add-ons are more stable across updates because Mojang controls the scripting surface, but that same sandbox is a hard ceiling: an add-on will never do what a Java mod that rewrites engine code can do.
Resource packs and texture packs
Java and Bedrock both support resource packs, and a popular pack's name often exists twice for exactly that reason: the two formats are not interchangeable. A Java resource pack is a .zip with a pack_format number tied to a Minecraft version range and PNG textures addressed by the game's own file paths. A Bedrock resource pack, usually distributed as .mcpack, uses a UUID-based manifest and its own folder layout, and Bedrock's texture resolution and animation JSON differ from Java's. A creator publishing to both editions is maintaining two separate builds, not one file with two extensions. Browse resource packs to compare builds across both editions.
Shader loaders per edition
Java shaders run through a loader, either Iris or the older OptiFine, that hooks into the game's rendering pipeline and lets a shader pack replace lighting, shadows, water, and reflections wholesale. You download a shader pack, drop it into the shaderpacks folder, and select it from the loader's menu. Bedrock has no equivalent loader. Its Render Dragon rendering engine is closed to user shader files, so visual overhauls on Bedrock come from resource packs simulating lighting with textures and lighting data, or from hardware-gated lighting features Mojang ships directly into the engine. Neither is a shader pack you can download and swap the way Java's are.
That is the real limit worth naming: a Java player with a mid-range GPU can chase a heavy shader preset for its own sake, while a Bedrock player on the same hardware has no download path to that level of visual control, regardless of budget.
Servers, multiplayer, and cross-play
Bedrock's biggest structural advantage is cross-play. Every Bedrock platform, console, mobile, and Windows, joins the same Bedrock servers and Realms through one account system, no extra setup required. Java servers are a separate ecosystem built on software like Paper and Spigot, with their own server plugins for permissions, economy, and moderation. The two networks don't talk to each other without help. Geyser is the tool that bridges them: it runs alongside a Java server and translates the Bedrock protocol so Bedrock players can join, no Java purchase required on their end.
Geyser closes most of the gap, but not all of it. Some Java-only UI, sound cues, and block behaviors still render differently, or not at all, for a Bedrock player connecting through it, and the server owner has to opt in and configure it rather than it working by default.
Performance and hardware
Java Edition runs on the JVM, which trades some raw performance for the flexibility mods need. A heavily modded Java instance can demand a strong CPU and a healthy RAM allocation just to stay stable. Bedrock's Render Dragon engine is native C++, built to run the same game acceptably on a phone, a console, and a gaming PC. That is why Bedrock is usually the smoother choice on lower-end hardware, and why Java asks for more tuning, more RAM, and more patience once mods enter the picture.
Which edition gets new features first
Java Edition has traditionally received new features first, through public snapshots that run for weeks before a full release, while Bedrock ships its own beta channel on a separate schedule. Since both editions moved to the same quarterly year.drop release cadence in 2026 (Bedrock switched over at 26.0 on 10 February 2026, after 1.21.132 in January 2026 closed out its old numbering), the gap between the two has narrowed, but Java's snapshot culture still tends to put new mechanics in front of players earliest. Treat this as a soft trend, not a rule: some features have landed on Bedrock first, and the release schedule is the kind of thing that keeps shifting.
Which edition should you pick
If you already own one edition and your friends play it, switching rarely pays off. Bedrock's cross-play and Geyser both exist specifically so a mixed friend group doesn't need everyone on the same edition, and repurchasing Minecraft for the other edition just to match a friend is money most players don't need to spend.
- Pick Java if deep customization matters most: Fabric, Forge, and NeoForge mods, Iris or OptiFine shaders, and a PC you're willing to tune.
- Pick Bedrock if you're on console, mobile, or want the game to run well without tuning, and you're fine with add-ons instead of mods.
- Already own one and mostly happy: stay put. Geyser and Bedrock's native cross-play cover most of the multiplayer gap either way.
- Curious what a resource pack, shader, or mod actually changes before picking a side? Read what resource packs, shaders, and mods actually change first.
Whichever edition you land on, that same split carries through the rest of the catalogue too. Maps, seeds, and skins all publish separate Java and Bedrock builds, same as everything else on this page.
Frequently asked questions
How do I know if I have Java or Bedrock Edition?
Check where you bought it. A Microsoft Store or minecraft.net PC purchase made in the last few years usually includes both editions in one launcher, with a version switcher near the top. A console, phone, or tablet copy is Bedrock only. If you're looking at a launcher without a switcher, an older or gifted PC copy may be Java only.
Can Java and Bedrock players play together?
Not directly. Bedrock players cross-play with each other across every Bedrock platform by default. To play with Java players, a Java server needs Geyser installed, which translates the Bedrock protocol so Bedrock clients can connect to a Java server. There's no equivalent path in the other direction; a Java client can't join a native Bedrock server or Realm.
How do I convert a Java world to Bedrock?
Mojang doesn't ship a built-in converter, because the two editions store worlds in different formats with different block and entity IDs. Third-party converters such as Chunker read a Java world's region files and rebuild them as a Bedrock world, remapping blocks and entities as closely as the two formats allow. Expect some loss on anything block-ID-specific, like blocks added by mods or very recent versions the converter doesn't recognize yet, so back up the original save first.
Do Java mods work on Bedrock, or Bedrock add-ons work on Java?
No, and this is the most common mix-up. A Java mod is code that runs on the JVM; Bedrock has no JVM and no code injection path, so a .jar mod simply won't load there. A Bedrock add-on is a JSON-and-scripting-API pack built for Bedrock's engine, and Java has no add-on importer that reads it. The two systems don't share a file format, an install location, or a scripting surface.
Which edition is better for shaders?
Java, without much competition. Iris and OptiFine give Java a real shader pipeline: download a pack, drop it in, and the loader replaces lighting and rendering wholesale. Bedrock's Render Dragon engine doesn't expose that pipeline to user files, so Bedrock's visual upgrades are resource packs simulating light rather than true shader packs.
