If you searched "slime chunk finder" for a Bedrock world and got a page full of Java seed-based tools, none of it applies to you. Bedrock slime chunks are not derived from the world seed. The Minecraft Wiki's Slime page documents Bedrock's slime-chunk algorithm as seed-independent: slime chunks "are generated at the same coordinates in every world" on Bedrock, which is the opposite of how Java places them.

That single fact breaks the entire Java slime-farming workflow, not just one step of it. This guide covers what actually works on Bedrock: how to locate a slime chunk without a seed, why the farm itself needs to be shaped differently because of individual spawning, and the swamp alternative that behaves the same on both editions.

Coming from a Java guide, including ours? Our Java slime farm guide is built entirely around seed-derived slime chunk coordinates. That workflow, plug your seed into a finder, jump to the coordinates, does not exist on Bedrock. Read on rather than trying to adapt it.

RateNo published slimeballs-per-hour figure for either spawn method
XP level1 XP small, 2 XP medium, 4 XP large (same values both editions)
Build timeDepends on dig time to locate a chunk plus spawn floor area
DifficultyIntermediate

The headline difference: no seed, no finder

On Java Edition, slime chunks are calculated from a formula that mixes the world seed with each chunk's coordinates. Every chunk in the world is deterministically slime or not-slime the moment the seed is set, which is exactly why Java seed finders exist: feed in the seed, and the tool solves the same formula the game uses.

Bedrock Edition does not do this. Per the wiki, Bedrock's slime chunk placement is independent of the world seed, generated at the same fixed coordinates across every world. There is no seed-based formula for a finder to reverse, because the seed is not an input to the calculation at all.

This means two different Bedrock worlds, with two completely different seeds, place slime chunks at the same coordinates relative to the world origin. It also means a "Bedrock slime chunk finder" that asks for your seed is solving the wrong problem, if such a tool claims to work, treat it skeptically against the wiki's documented behavior.

What a Bedrock player does instead

Since there is no seed to feed a calculator, locating a slime chunk on Bedrock comes down to two practical options:

  1. Dig and observe at the fixed-coordinate pattern. Because Bedrock's slime chunk layout repeats at the same coordinates world to world, community-mapped coordinate patterns (spaced out at fixed intervals from the world origin) are the closest Bedrock equivalent to a "finder", but they are a coordinate pattern to check, not a seed calculation. Travel to a candidate location, dig down below Y=40, and confirm.
  2. Direct observation underground. Mine out a chamber below Y=40 in an unconfirmed area and wait. Slimes are green and visually obvious; if you see one appear on a lit or unlit floor below Y=40 with no swamp biome nearby, you are standing in a slime chunk. This is slower but requires no external tool or claimed coordinate list.

There is no seed to plug in. On Bedrock, finding a slime chunk means going down there and looking, not solving for it at your keyboard.

Once you have confirmed a chunk, the same logic that makes Java slime-chunk farming worthwhile still applies: that chunk stays a slime chunk permanently, since Bedrock's placement is fixed, not random per session. The dig is a one-time cost.

Individual spawns change what the farm needs to be

This is the second major mechanical split, and it directly changes how big a Bedrock slime farm needs to be to produce comparably.

The Minecraft Wiki documents Java Edition spawning slimes in groups of four at a time within a slime chunk below Y=40. Bedrock spawns them individually, one at a time per spawn attempt, not in a four-pack.

That is not a cosmetic difference. A Java farm gets a burst of four slimes filling the mob cap slots from a single successful spawn roll. A Bedrock farm gets one slime per successful roll, at whatever the underlying per-chunk spawn-attempt rate is. To fill the same number of cap slots in comparable time, a Bedrock farm leans more heavily on:

  • A larger spawn floor area. More valid spawn surface inside the slime chunk means more chances for an individual spawn to land, which is doing the work that Java's four-at-once grouping does automatically.
  • Multiple spawn floor layers, stacked with enough vertical clearance for slimes to spawn on each, all still below Y=40 and all inside the confirmed slime chunk boundaries.
  • Efficient funneling, since with individual spawns there is no burst to catch all at once, a continuously running collection system matters more than a periodically-checked one.

Do not build a Bedrock slime farm at Java-guide dimensions and expect a matching per-hour rate. The spawn shape underneath it is different: four-at-once versus one-at-a-time. Oversize the spawn floor relative to a Java design targeting the same chunk footprint.

No official per-hour slimeball figure is published by the wiki for either spawning method, so treat any specific rate you see quoted online as an individual builder's measured result on their own farm, not a guaranteed number for yours. Measure your own output after building.

Building the slime-chunk farm

With a confirmed slime chunk in hand, the build itself follows the same underlying requirements documented for slime spawning, adjusted for Bedrock's individual-spawn shape:

  1. Confirm the chunk boundaries, not just one coordinate. A slime chunk is a full 16x16 column; know where it starts and ends so your spawn floors don't waste space outside it.
  2. Dig spawn floors strictly below Y=40. Slime-chunk slimes spawn at any light level, so darkness is not required here the way it is for most other hostile mobs, but the Y=40 ceiling is absolute. A floor even one block above it produces nothing.
  3. Stack multiple floor layers with clearance between them (slimes need vertical room to spawn as their size varies: small, medium, and large slimes take different amounts of space). More layers compensate for individual, rather than grouped, spawning.
  4. Funnel to a central collection point. Water streams or agitator-based movement toward a drop shaft works the same on Bedrock as the underlying block mechanics are shared between editions; the funneling geometry itself is not part of what differs here.
  5. Kill chamber at the bottom, sized to one or two hits so drops are collected efficiently, with a fall or a simple damage method finishing off survivors.
  6. AFK inside the chunk's loaded range. Keep your simulation distance high enough that all spawn floors stay active; see our render vs. simulation distance guide for how that setting governs what stays ticking while you're away.
Mechanic Java Edition Bedrock Edition
Slime chunk source Derived from world seed + coordinates Fixed coordinates, independent of seed
Finder tool Seed-based calculator works directly No seed-based finder applies; dig and observe
Spawn grouping below Y=40 Groups of four per spawn event Individual, one per spawn event
Swamp spawn window Y=51 to Y=69, light 7 or less, moon-phase dependent Same: Y=51 to Y=69, light 7 or less, moon-phase dependent
Published rate (slimeballs/hour) Not published by the wiki Not published by the wiki

The swamp alternative

Swamp spawning is the one part of this guide where the two editions agree. Per the wiki, slimes in swamp biomes spawn:

  • Between Y=51 and Y=69 inclusive, on the surface.
  • At a light level of 7 or less.
  • With frequency tied to moon phase: more often near a full moon, and never on a new moon, since the spawn check rolls against the moon's current illumination.

Because this mechanic is identical on both editions, a swamp slime farm is the more portable design if you'd rather not hunt for a fixed-coordinate slime chunk at all. It trades the slime-chunk farm's always-on nature (works any time, any weather, once built) for a build that only produces well at night and drops off hard around a new moon. Since it doesn't depend on Bedrock's seed-independent chunk placement or the individual-versus-grouped spawn distinction, a swamp farm built from general spawning-mechanic knowledge works without edition-specific adjustment beyond the general spawning differences covered in our Java farms on Bedrock guide.

Choosing between the two: a slime-chunk farm is more work to locate (no seed shortcut) but runs continuously. A swamp farm is easier to confirm (find a swamp, check the Y range and light level) but is night-and-moon-phase gated. Neither editions' numbers transfer to a slimeball-per-hour promise since none is published.

Pros

  • Once a slime chunk is confirmed, it is permanent: Bedrock's fixed-coordinate placement means it never changes across world regeneration the way a seed-matched Java chunk also doesn't
  • Swamp spawning mechanics are identical across editions, so that method needs no edition-specific redesign
  • Slime-chunk spawns ignore light level entirely, so spawn-proofing effort can go elsewhere

Cons

  • No seed-based finder exists for Bedrock; locating a chunk costs real dig time or reliance on a fixed-coordinate pattern
  • Individual spawning means a Bedrock farm needs more spawn floor area than a Java farm targeting the same output
  • No published slimeballs-per-hour figure exists for either spawning method, so you cannot pre-calculate expected yield

Frequently asked questions

Do slime chunks work the same on Bedrock as Java?

No. Java derives slime chunks from the world seed combined with chunk coordinates, so a seed-based finder can calculate them instantly. Bedrock's slime chunk placement is independent of the seed and generates at the same fixed coordinates in every world, per the Minecraft Wiki. A Java seed finder has nothing to calculate on a Bedrock world.

Can I use a Java slime chunk finder on my Bedrock world?

No. The tool would need the seed to be an input to the chunk-placement formula, and on Bedrock it isn't one. Any result it gives you for a Bedrock world is not describing that world's actual slime chunks.

Why does my Bedrock slime farm produce fewer slimes than a same-sized Java design?

Java spawns slimes in groups of four per successful spawn event below Y=40; Bedrock spawns them individually, one per event. A Bedrock farm needs a larger spawn floor area or more floor layers to reach comparable output, since it isn't getting the four-at-once burst Java gets.

Does light level matter for slime-chunk spawning on Bedrock?

No, and this matches Java: slimes in a slime chunk below Y=40 spawn at any light level on both editions. Light level only matters for the swamp-biome spawning method, where it needs to be 7 or less.

Is the swamp method easier than finding a slime chunk on Bedrock?

It can be, since it doesn't require locating a fixed-coordinate slime chunk at all, just a swamp biome. But it only produces well at night in the Y=51 to Y=69 range with light 7 or less, and moon phase gates it further: it never spawns on a new moon. A slime-chunk farm runs continuously once built; a swamp farm does not.

How many slimeballs per hour should I expect?

Neither the wiki nor this guide publishes a figure for either spawning method. Output depends on your spawn floor size, layer count, and collection efficiency. Build the farm, run it, and measure your own rate rather than targeting an assumed number.


Sources & further reading: