Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is MCEdit?
MCEdit is a third-party saved-game editor for Minecraft that works more like a 3D world and terrain editor than a typical save-file tool. Because a Minecraft save contains every element of the world, MCEdit lets you open that world and edit it directly rather than changing a few numbers in a file. The project has been developed since 2010, originally to let Classic levels be played in the full version of Minecraft, and has since grown into a full-featured editor that was undergoing a thorough rewrite for version 2.0.
What it is useful for
- Reworking large areas of an existing world without rebuilding them block by block in-game.
- Editing terrain and structures at world scale, which is the kind of task the site frames as closer to map and terrain editing than to save editing.
- Working with the Java edition versions listed on the page; Bedrock, Windows 10, Xbox, PS4 and Pocket are listed as not supported.
Practical considerations
MCEdit is a separate utility and is not affiliated with Minecraft, Mojang AB or Microsoft. The page distinguishes MCEdit 1.0 from the in-development MCEdit 2 line, so check which version matches your Minecraft version before starting: MCEdit 1.0 lists Java 1.7 through 1.11 and Forge 1.7, while MCEdit 2 beta notes updated block knowledge for Minecraft 1.10. If you play on a console or mobile version, this tool will not open your world.
A sensible next step is to back up the world you intend to edit, then confirm your Minecraft version against the supported list on MCEdit before downloading.
Which Minecraft versions does MCEdit support?
MCEdit supports Minecraft Java Edition versions 1.7 through 1.11, plus Forge 1.7, according to the download page on MCEdit. It does not support Bedrock, Windows 10, Xbox, PS4, or Pocket editions. The page also notes that block knowledge was updated for Minecraft 1.10, so the later 1.11 support may be less complete in practice.
Practical implications
- Java players on 1.7–1.11: This is the intended audience; world editing and map conversion are the main uses.
- Forge 1.7 modpacks: Supported, which matters if you want to edit modded worlds.
- Newer Java versions or console/mobile: Look elsewhere; this tool won't open those worlds.
As a next step, check your world's version before downloading, and back up the save first—editing tools can alter world data irreversibly.
How do I install and download MCEdit for my platform?
MCEdit is downloaded directly from its official site, and the version you pick depends on the Minecraft edition you play. According to the site's own download section, MCEdit 1.0 supports Java Edition versions 1.7 through 1.11 and Forge 1.7, while Bedrock, Windows 10, Xbox, PS4 and Pocket editions are listed as not supported. The site also notes that MCEdit 2 was in Beta as of September 2016, with Mac OS X downloads available and documentation aimed at plugin authors underway.
Choosing a version
| Your situation | Sensible starting point |
|---|---|
| Playing Java Edition 1.7–1.11 (or Forge 1.7) | MCEdit 1.0, the stable release described on the site |
| On macOS and want the newer rewrite | MCEdit 2 Beta, since Mac downloads are noted as available |
| Playing Bedrock, console or mobile | Neither version, per the site's supported-versions list |
| Writing plugins | MCEdit 2, alongside the plugin documentation linked from the site |
On the site, use the Download link in the top navigation to reach the downloads, and the Documentation link for setup and usage notes. Because MCEdit edits saved game files directly, back up your world folder before opening it in the editor, and close Minecraft first so the files aren't locked.
The main trade-off is stability versus features: MCEdit 1.0 is the long-standing release, while MCEdit 2 is a thorough rewrite that the site describes as still in Beta, so expect rough edges and report issues through the site's issue link. If your Minecraft version is newer than 1.11 on Java, check the download page for current compatibility before assuming it will open your world.
For community help and version-specific questions beyond the official pages, r/Minecraft and the Minecraft forums are common places players discuss world-editing tools.
What can I do with MCEdit's world editing features, such as rotating or copying builds?
MCEdit is a third-party saved-game editor for Minecraft that works on world files rather than inside the running game. Because a Minecraft save contains the whole world, its editing model is closer to a 3D map or terrain editor than to a traditional save-game tool. In practice, you open a world, select a region, and apply operations to it.
What the editing model supports
The site describes MCEdit as a full-featured world editor developed since 2010 and now being rewritten for version 2.0. Its development notes highlight a free rotation feature in the 2.0 line, demonstrated in a video by the developer. That points to the kind of work you are asking about: taking an existing build or terrain selection and turning it, rather than rebuilding it block by block.
Copying builds fits the same selection-based workflow. You mark the area containing a structure, duplicate it, and place the copy elsewhere in the world or in another save. This is the main reason players use a world editor: moving a base, repeating a design, or rearranging terrain without manual placement.
Practical uses
- Relocating or duplicating structures. Select a house, farm or redstone build, copy it, and paste it at new coordinates.
- Rotating a build to fit a different site orientation, using the rotation feature shown in the 2.0 development notes.
- Reshaping terrain around a build so a copied structure sits correctly.
- Working outside the game, which suits large or repetitive changes that would be tedious in creative mode.
Trade-offs to weigh
The page lists Java editions 1.7 through 1.11 and Forge 1.7 as supported, while Bedrock, Windows 10, Xbox, PS4 and Pocket are explicitly not supported. If your world is from a Bedrock-based platform, this tool is not the right fit. The 2.0 rewrite was still in beta when these notes were written, so expect the mature 1.x line and the newer 2.0 line to differ in features and stability.
Next step
Back up the world folder before editing, then check the Download and Documentation pages to confirm which version matches your Minecraft release. For players who mainly want in-game building aids, Minecraft covers the official game; for world-format details, the community wiki at Minecraft Wiki is a useful reference.
How do I write or install plugins for MCEdit 2?
MCEdit 2's plugin documentation is aimed at plugin authors and is linked from the site's "Documentation" page; the page notes that documentation for plugin authors was "underway," so expect developer-oriented material rather than a polished tutorial. Installation is the part with a clear caveat: the site describes MCEdit 2 as a Beta and invites issue reports, and it lists supported Java versions (1.7–1.11, Forge 1.7) for MCEdit 1.0 while stating Bedrock, Windows 10, Xbox, PS4 and Pocket are not supported. Treat any plugin work as beta-era experimentation, not a stable platform.
Practical path for a builder or server admin
- Confirm you actually need a plugin. Many world-editing tasks (terrain shaping, block replacement, structure copying) are core editor operations; plugins add custom brushes, filters or workflow tools. If a built-in tool covers it, skip the plugin route.
- Read the author documentation first, then look at the source. The site links to source code and a translation page, which are the most reliable references when prose docs lag behind the beta.
- Test on a copy of a world, never the original. Saved-game editing touches every element of the world, so a bad plugin run can be costly. Keep a backup and a small test world for iteration.
- Match versions deliberately. A plugin written against one block/version set may misbehave on another; the site's version list gives you the compatibility baseline to check against.
Choosing between writing and installing
| Situation | Better route | Trade-off |
|---|---|---|
| You need a common edit (fill, replace, copy) | Use built-in tools | No custom logic, but no maintenance burden |
| You need a repeatable custom operation | Write a small plugin | Requires reading the author docs and testing; beta APIs can change |
| You want an existing workflow fast | Install a community plugin | Depends on someone else's maintenance and version support |
If you are new to this, start by reproducing a simple built-in operation as a plugin in a test world; that teaches the API surface faster than reading reference pages alone. For broader Minecraft tooling context, Minecraft is the official source for game versions, which matters when matching a plugin to a supported release.
What are the differences between MCEdit 1.x and MCEdit 2 Beta?
The main difference is maturity versus direction. MCEdit 1.x is the finished, long-standing editor; MCEdit 2 Beta is the ground-up rewrite that, as of the page's September 2016 post, had "most of the vital features" implemented but was still in beta with bugs to report.
Practical comparison
| MCEdit 1.x | MCEdit 2 Beta | |
|---|---|---|
| Status | Legacy codebase, complete | Beta rewrite, features still landing |
| Best for | Actually editing a world today | Testing the new interface and newer features |
| Minecraft support | Java 1.7–1.11 and Forge 1.7 per the download page | Block knowledge updated for 1.10 per the beta post |
| Platforms | The established download | Mac OS X builds newly available at beta |
| Extensibility | Existing behavior | Plugin-author documentation underway |
The page confirms neither edition supports Bedrock, Windows 10, Xbox, PS4 or Pocket editions — both are Java-focused.
What this means in practice
If you have a survival world with a terrain mistake to fix or a build to move, 1.x is the safer choice: it is the version whose feature set is settled. Choose 2 Beta if you want to try the newer editing approach — the development digests highlight features like free rotation — and are willing to hit rough edges and file issue reports.
A concrete example: a player preparing a Java 1.11 map for a server would open it in 1.x, since that version range is explicitly listed. Someone on 1.10 curious about the rewrite could install the beta alongside, keeping a world backup before either tool touches it.
Next step
Open the Documentation page before downloading, then check the version list against your exact Minecraft Java version; for anything you intend to keep, work on a copy of the save.
User reviews (0)