For Minecraft Bedrock, the usual way is to block the portal itself rather than trying to truly disable the Nether. Bedrock does not have a simple server.properties switch like Java, so the practical options are a behavior pack or a repeating command block that removes or nullifies Nether portals as they form or when players try to use them.

Simple server/world method

  • Use a repeating command block set to Always Active.
  • Run a command that detects Nether access and teleports players back, or removes portal blocks near them.
  • This is a workaround, not a full Nether disable, but it is the standard Bedrock approach.

Behavior pack method

  • Install a behavior pack that blocks Nether portal creation or portal function.
  • This is cleaner for a realm or custom world if you want a more permanent solution.
  • Bedrock support pages note that portal-blocking behavior packs are a valid way to restrict Nether access.

One-command workaround

A commonly used command-block workaround is to constantly delete portal blocks around players so the portal cannot stay active. The idea is to run it on repeat in a loaded chunk so no one can complete the trip.

Best choice

  • For a realm or server , use a behavior pack.
  • For a single world , use a repeating command block.
  • If you want the simplest reliable answer, Bedrock’s Nether is generally restricted , not fully disabled.

Example setup

Put a repeating command block in spawn chunks and make it always active, then have it remove nether_portal blocks around players or teleport anyone who enters the Nether back to the Overworld. That keeps players from using the portal even though the dimension itself still exists.

TL;DR: On Bedrock, you usually stop players from entering the Nether by blocking portals with a behavior pack or a repeating command block, because there is no built-in full disable switch like Java has.