/effect — Java vs Bedrock

Key differences

• Bedrock uses a single-form /effect — no give/clear subcommands. The arguments after the target tell the command what to do.
• Bedrock's clear form is `/effect <target> clear`, not `/effect clear <target>` like Java.
• Bedrock effect IDs match Java exactly (speed, jump_boost, etc.) — the namespace prefix is optional.
• Both editions cap duration at 1,000,000 seconds (~11.5 in-game days). Bedrock additionally rejects negative durations.

Bedrock examples

Copy-pasteable. Run in chat with cheats enabled.

• /effect @p speed 30 1

  Speed II for 30 seconds. Note: no `give` subcommand.

• /effect @p clear

  Remove all status effects from the nearest player.

• /effect @e[type=zombie] strength 999 5 true

  Give all zombies Strength VI for 999 seconds with hidden particles.

Java examples

For contrast — these are the canonical Java forms.

• /effect give @p minecraft:speed 60 2

  Give the nearest player Speed III for 60 seconds.

• /effect give @s minecraft:night_vision infinite 0 true

  Permanent night vision with hidden particles.

• /effect clear @p

  Remove all effects from the nearest player.

FAQ

What's the difference between /effect in Java and Bedrock?

/effect exists in both editions but the syntax differs — see the "Key differences" section above. The most common gotcha is that Java's component syntax (square brackets after the item ID) doesn't work in Bedrock.

Why doesn't my Java /effect command work in Bedrock?

Bedrock has stricter syntax and doesn't support Java's modern component-based item syntax. If you copied a command from a Java tutorial, Bedrock will likely reject it silently or run a partial version. Use the Bedrock examples on this page as templates.

Does /effect work the same on consoles and mobile?

Yes — Bedrock Edition is the same codebase on Windows 10, Xbox, PlayStation, Switch, iOS, and Android. The syntax shown here works on every Bedrock platform.

Other edition comparisons

• /give — Java vs Bedrock
• /summon — Java vs Bedrock