FastAsyncWorldEdit, usually shortened to FAWE, is a drop-in fork of WorldEdit built for Paper, Spigot, Bukkit, and Purpur servers. It rewrites the editing engine to run asynchronously and process whole chunk sections at once, so large region edits, cut-and-paste operations, and schematic pastes that take minutes in vanilla WorldEdit finish in seconds. It supports Minecraft 1.16 through the current 1.21.x releases and keeps WorldEdit's command syntax, so existing muscle memory and tutorials still apply.
Why Server Owners Switch from WorldEdit to FAWE
FAWE processes edits through chunk-level placement instead of individual block API calls, which is what gives it the largest speed gains over stock WorldEdit on Paper and Spigot. Any other plugin on the server that depends on the WorldEdit API, including most schematic tools and building utilities, automatically benefits from that speed once FAWE is installed, since FAWE maintains full API compatibility with WorldEdit.
- Over 200 commands, including all standard WorldEdit commands
- Unlimited //undo history, per-world history, and cross-server clipboards
- Per-player limits on entities, tile entities, memory, changes, and iterations
- Additional brushes, masks, and pattern syntax beyond stock WorldEdit
- Automatic repair of partially corrupt schematic files
Installation on Paper or Spigot
- 1.Download the Bukkit-flavor jar from the FastAsyncWorldEdit Modrinth page for your Minecraft version
- 2.Stop the server and place the jar in the plugins/ folder
- 3.Remove any existing WorldEdit jar from plugins/ first; running both at once causes command conflicts
- 4.Start the server; FAWE generates its config files under plugins/FastAsyncWorldEdit/
- 5.Test with a basic command such as //wand or //set stone to confirm the plugin loaded
Compatibility with WorldGuard and PlotSquared
FAWE ships with built-in support for region protection through WorldGuard and plot management through PlotSquared, both maintained by the same IntellectualSites team. Region checks and plot boundaries are respected during FAWE operations, so a player without edit permission in a protected region or another player's plot cannot bypass that protection through brush or pattern commands.
Limits and Permissions
Server admins can cap how many blocks, entities, or iterations a permission group is allowed to edit per command through FAWE's limits configuration, which prevents a single large operation from freezing the server. Permission nodes follow the worldedit.* namespace used by stock WorldEdit, so an existing LuckPerms setup built for WorldEdit carries over without changes.
Watch FastAsyncWorldEdit in Action
FastAsyncWorldEdit plugin overview and command walkthrough
Questions about this entry.
How do I install FastAsyncWorldEdit on a Paper server?
Download the Bukkit-flavor jar from the FastAsyncWorldEdit Modrinth page, remove any existing WorldEdit jar, drop the FAWE jar into your plugins/ folder, and restart the server. FAWE generates its own config under plugins/FastAsyncWorldEdit/ on first launch.
Does FastAsyncWorldEdit replace WorldEdit, or do I need both?
FastAsyncWorldEdit fully replaces WorldEdit. It implements the same WorldEdit API and command set, so other plugins that depend on WorldEdit keep working. Running the stock WorldEdit jar alongside FAWE causes command conflicts and should be avoided.
Is FastAsyncWorldEdit compatible with WorldGuard and PlotSquared?
Yes. FAWE, WorldGuard, and PlotSquared are all maintained by IntellectualSites and are built to work together. Region protection from WorldGuard and plot boundaries from PlotSquared are both respected during FAWE edit operations.
Which Minecraft versions does FastAsyncWorldEdit support?
FastAsyncWorldEdit publishes builds spanning Minecraft 1.16.5 through the current 1.21.x releases for Paper, Spigot, Bukkit, and Purpur. Check the version dropdown on its Modrinth page for the exact build matching your server's Minecraft version.
Does FastAsyncWorldEdit impact server performance?
FAWE is designed to reduce server load compared to stock WorldEdit by processing edits asynchronously and in chunk sections rather than one block at a time. Per-player limits in the config also let admins cap how large a single edit operation can be, which helps prevent lag spikes on shared servers.
