WorldEdit vs FastAsyncWorldEdit for Java Servers

Pick WorldEdit if you play single-player, run a Fabric or NeoForge setup, or want the editor EngineHub maintains across the widest range of platforms. Pick FastAsyncWorldEdit if you run a Paper or Spigot server where large edits matter and a plugin is acceptable. Both are Java Edition only.

Facts here come from EngineHub's WorldEdit page and the Modrinth listings for both projects. We read documentation and release listings. We did not run either tool or time any edit.

The two editors side by side

What WorldEdit and FastAsyncWorldEdit are

WorldEdit is an in-game map editor with selections, schematics, copy and paste, brushes and scripting. EngineHub describes it as a way to create, replace or delete tens of thousands of blocks in seconds, and its listing says there are over 100 functions.

WorldEdit

@me4502 · Java Mod

JavaFabric, NeoForgev 1.17.1 to 1.21.5

Checked Aug 27, 2026Source and install notes ↗

FastAsyncWorldEdit, called FAWE, is a fork of WorldEdit. Its own description says it has large speed and memory improvements and considerably more features. Both repositories carry the same WorldEdit License file, which states GNU GPL version 3, so the licence does not separate them.

FastAsyncWorldEdit

@IntellectualSites · Server Plugin

JavaBukkit, Paper, Purpur, Spigotv 1.16.5 to 1.21.11

Checked Jul 9, 2026Source and install notes ↗

Platforms and versions each supports

This is the sharpest difference. WorldEdit ships as a mod for Fabric and NeoForge and as a plugin for Bukkit-based servers, with Sponge also listed on EngineHub's page and Folia builds listed on Modrinth. That is why it is the only one of the two that works in a single-player world. Its Forge builds stopped at 1.20.4, and its single Quilt build is for 1.20.2.

FAWE is a server plugin. Its current builds cover Paper and Spigot from 1.16.5 to 26.3. Its Bukkit and Purpur builds stopped at 1.21.3, so a Purpur server on a newer Minecraft version has no listed FAWE build. Nothing on its Modrinth page marks it as a client-side tool: players join a server that has it and install nothing.

On the oldest versions, WorldEdit reaches much further back (Paper from 1.6.4, Spigot from 1.4.6). If you run an old server, that range may decide the question.

Speed claims in each project's own docs

We give no speed number because none is sourced. What each project says about itself is as follows.

• WorldEdit: you can quickly create, replace or delete tens of thousands of blocks in seconds. It gives no benchmark and no comparison to other tools.
• FAWE: it calls itself a fork with huge speed and memory improvements, and says it is insanely fast in its slowest mode. All editing is processed asynchronously, with some tasks split up on the main thread.
• FAWE lists three placement modes, each with higher throughput than the one before: Bukkit-API blocks, chunk placement through server internals (the default) and a world mode used to generate new worlds or regions.
• FAWE also says that other plugins depending on WorldEdit get faster simply because FAWE is installed, and that its Bukkit-API mode is still faster than any other plugin on Spigot. Both are the project's own statements, not independent results.

The direction is consistent. FAWE presents speed as its reason to exist, while WorldEdit presents it as one of several strengths.

Commands the two have in common

FAWE keeps API compatibility with WorldEdit, and its feature list is written as additions to WorldEdit's: more brushes and tools, more mask and pattern syntax, and support for formats such as structure blocks.

The extra commands are on FAWE's side. It lists over 200 commands against WorldEdit's over 100 functions, though the two counts may not measure the same thing. FAWE-specific examples from its page include //lazycopy for instant copying of any size, //inspect and //history rollback for searching and restoring changes, and //fast to bypass logging. WorldEdit's own examples include //deform, //g with a mathematical expression, JavaScript scripting and /jumpto. The WorldEdit guide covers the shared basics, and schematics work with either.

When WorldEdit fits

The choice is made for you in a few cases. If you build in single-player, you need the mod form for Fabric or NeoForge, because FAWE has no mod. If you run Folia, Sponge, or a server older than 1.16.5, WorldEdit is the one with listed builds. If your server runs Forge, note that WorldEdit's Forge builds end at 1.20.4 and FAWE has none.

It also fits when you want the simplest setup. Its newest listed build has no dependencies. The trade-off is that the newest build is a beta, and EngineHub's page makes no claim about speed beyond its general wording. Install steps are in how to install mods on Java and how to install server plugins.

When FastAsyncWorldEdit fits

FAWE fits a Paper or Spigot server where several builders make large edits and you want per-player limits, persistent history and rollback. Its page lists limits on entities, tiles, memory, changes, iterations and regions. It names WorldGuard and PlotSquared as supported protection plugins, so it pairs with the setup in how to use WorldGuard.

The trade-offs are real. It is server-side only, its Bukkit and Purpur builds have stopped, and its feature set is larger, so there is more to configure and learn. Its speed statements are its own. If you are unsure whether a plugin or a mod is the right form, read plugins vs mods vs data packs.