How to build an XP farm on Bedrock Edition: mob cap, spawn radius, and simulation distance

A Java XP farm guide will tell you to build a dark room, AFK somewhere between 24 and 128 blocks from it, and let the per-player mob cap fill the room. Follow that advice on Bedrock and the farm underperforms or stalls, because Bedrock spawns mobs against a completely different system: no per-player cap exists, the global cap is a flat 200, and the actual spawn radius is set by a graphics setting most players never touch.

This guide covers the Bedrock spawning model, verified against minecraft.wiki/w/Mob_spawning, and a dark-room design built around it rather than around Java's numbers.

Why Java's spawning numbers do not transfer

Java's hostile mob spawning runs on two caps stacked together: a global cap that scales with loaded chunks (mobCap x chunks / 289, base 70 hostile mobs) and a per-player cap, where any mob within 128 blocks of a player counts against that specific player's allowance. Multiplayer mob switches on Java exploit the per-player cap directly: pull mobs toward a spot where one player's cap is claimed, and other players (or the switch mechanism itself) can manipulate who "owns" the spawn budget.

Bedrock has no per-player cap at all. Per the wiki, Bedrock uses a single global cap of 200 mobs, regardless of difficulty, plus population control limits that cap how many of each mob type can exist within a 9 chunk by 9 chunk region. There is no player-specific budget to claim or starve, which means the entire premise behind a Java mob switch does not exist on Bedrock.

Java also spawns mobs anywhere within a 128-block sphere of a player and despawns them instantly past 128 blocks. Bedrock ties its spawn radius to a setting, not a fixed sphere, covered next.

Simulation distance is the setting that decides whether your farm spawns at all

This is the single biggest practical difference for Bedrock XP farm builders. On Java, render distance and spawn radius are effectively decoupled from a single player-facing slider in the way Bedrock's are. On Bedrock, simulation distance directly governs how far from the player mobs can spawn:

• At simulation distance 4 (a common default, especially on lower-end devices), mobs spawn roughly 24 to 44 blocks from the player.
• At simulation distance 6 or higher, the spawn radius extends further, toward roughly 96 to 128 blocks horizontally, though it stays bounded by whatever simulation distance is actually set rather than jumping straight to Java's fixed 128-block figure.

If your farm's spawn platforms sit outside the radius your current simulation distance produces, they simply will not spawn mobs, no matter how well the room is sealed and lit. This is a setting problem, not a build problem, and it is worth checking before troubleshooting anything else.

Building the dark room around Bedrock's actual radius

The core XP farm shape doesn't change: a sealed, unlit, spawnable-floor room that funnels mobs toward a fall or damage chamber where the player lands the final hit for XP (fall damage and lava kills give no XP on either edition). What changes is where you place it and where you stand.

1. Set simulation distance deliberately, then build to it. Decide what simulation distance you'll actually play with (higher gives a larger spawn radius but costs performance) and treat that number as fixed before placing the farm. Building at 44 blocks out and then playing with simulation distance 4 (24-44 block radius) leaves no margin; keep the AFK spot and farm comfortably inside the radius your setting actually produces.

2. Maximize spawnable floor inside that radius, not outside it. Because the global cap is a flat 200 shared across the whole loaded world, not a fenced-off per-player budget, a bigger, more efficient spawning floor within a shorter radius generally outperforms a large farm built far away hoping for a bigger sphere. Dense, dark, fully-covered floor space close to the AFK spot is the lever that actually matters here.

3. Respect the 9x9 chunk population control. Bedrock limits how many of each mob type can exist within a 9x9 chunk region. A single-species farm (all zombies, say) won't be throttled by other mob types competing for the same regional slots the way a mixed-spawn area might be, so a dedicated, walled spawning floor that excludes other spawn surfaces nearby tends to perform more consistently.

4. Standard fall-and-collect kill chamber. Funnel spawned mobs with water streams to a central drop of 23+ blocks (enough to bring most mobs to near-death without killing them outright), then a narrow kill spot where the player delivers the final blow for XP. This part of the build is edition-agnostic; the mechanics that changed are all upstream, in where mobs spawn and how many can exist at once.

5. AFK spot placement. Stand where your farm's spawnable floor sits within the radius your simulation distance setting produces, not at a distance copied from a Java guide. There is no per-player cap to position yourself against; the only positioning question on Bedrock is whether the floor is inside the radius at all.

On Bedrock, the graphics settings menu is part of the farm. Simulation distance decides whether the room you built can spawn anything at all.

On rates

The wiki publishes the mob cap and spawn-radius mechanics above but no mobs-per-hour or XP-per-hour figure for Bedrock, and this site does not invent one; a prior version of this article family was corrected for exactly that. Actual throughput depends on your simulation distance setting, how much spawnable floor sits inside the resulting radius, and how many other mobs across the loaded world are competing for the shared 200 global cap. Time your own farm with a hopper-and-comparator item counter rather than trusting a Java-sourced number.

Frequently asked questions

Does a Java mob switch work on Bedrock?

No. Java mob switches work by manipulating the per-player mob cap, and Bedrock has no per-player cap at all, only a flat global cap of 200 shared across the world. There is nothing for a Java-style switch to act on. See why Java farms fail on Bedrock for the broader pattern.

Why is my Bedrock XP farm not spawning anything?

The most common cause is simulation distance. Bedrock's spawn radius is tied directly to that setting: at simulation distance 4, mobs only spawn 24 to 44 blocks out. If your farm sits further than your current simulation distance allows, check that setting before assuming the build itself is broken.

What simulation distance do I need for an XP farm on Bedrock?

There's no single published minimum; it depends on how far your spawnable floor sits from the AFK spot. Setting 6 or higher extends the spawn radius toward roughly 96-128 blocks, giving more room to work with than the 24-44 block radius at setting 4, provided your device or server can sustain it.

What is the mob cap on Bedrock, and does difficulty change it?

A flat global cap of 200 mobs, and it does not change with difficulty (unlike some other Bedrock difficulty-scaled mechanics). Population control additionally limits how many of each mob type can exist within a 9x9 chunk region.

Does fall damage give XP on Bedrock like it doesn't on Java?

No XP either edition. A mob killed purely by fall damage, lava, or similar environmental damage gives no experience on Bedrock or Java. XP farms bring mobs to near-death automatically and rely on the player landing the final hit.

Can I copy a Java XP farm's AFK distance to Bedrock?

No. Java's AFK distance math assumes a fixed 128-block spawn sphere and a per-player cap; Bedrock's spawn radius is instead set by simulation distance and shares one global cap with no player-specific budget. Rebuild your AFK placement around your actual simulation distance setting rather than a distance copied from a Java guide.