TEdit: the Terraria map editor that has to chase every game update

What TEdit actually edits beyond the tile grid

The project describes itself as a standalone open source map editor for Terraria that lets you edit maps almost like paint. That framing undersells it. The longer description on the repository page goes into world settings such as time and bosses downed, chest editing, sign changes, and the ability to build dungeons, castles and cities and attach rewards for adventurers.

The distinction from a texture or sprite tool is that a Terraria world file stores tiles, walls, liquid, doors, chests with their contents, NPCs, signs and spawn data in one binary structure. TEdit reads and rewrites that structure, so the output is a playable world rather than an art asset. For a player who wants to design a map and then actually play it, that is the whole point.

The primary language is C#, and the topics are simply `tedit` and `terraria`. There is a homepage, docs.tedit.dev, which is where the usage documentation lives, and a Discord invite for support questions.

The README itself is short, essentially a links page: documentation, Discord, the developer blog at binaryconstruct.com, source, downloads and a Crowdin link for translating the interface. The repository is owned by TEdit, while the README title and the developer blog both use the name BinaryConstruct, which is the long-time maintainer behind it.

Following Terraria's world file version on every release

This is the part of the project that tells you what kind of software it is. Each recent release leads with a compatibility banner rather than a feature list. TEdit 5.2.5-beta0, published 2026-08-24, opens with a note that it supports Terraria 1.4.5.8 with world file version 326. TEdit 5.2.4, four days earlier, supports Terraria 1.4.5.7 with world file version 325.

A version number in the file format means a TEdit build is only correct for one game version. Open a world saved by a newer Terraria in an older editor and the editor does not have the definitions to interpret it. The practical consequence is that after a Terraria update, you wait for TEdit rather than the other way round, and if you maintain worlds across updates you keep copies.

The 5.2.4 release body also names something readers of such tools care about: modded world save fixes. Terraria modders change the world format independently of the base game, so an editor that ignores mods silently corrupts their saves. That line is evidence the save path is treated as the fragile part of the project rather than a detail.

Version 5.2.5-beta0 also adds legacy support for Windows Phone, which is an odd line to find and a reasonable one in a project that has to reach back across many years of Terraria players' saves.

Two build scripts for two UI histories

The tree shows `build.ps1` alongside `build-avalonia.ps1` and `build-legacy.ps1`, which is a compact history of the project's architecture in three filenames. The legacy path is the original Windows build, and the Avalonia path is a cross-platform rewrite, Avalonia being the .NET UI framework that can target Windows, Linux and macOS from one codebase.

There is a `reactiveui-notes.md` at the root, which points to the ReactiveUI library and suggests the rewrite adopted a model-view-viewmodel framework rather than doing manual event wiring. A `.config/` directory at the top is the conventional home for a local dotnet tool manifest, and `.vscode/` is checked in for editor settings.

The build tooling is PowerShell rather than a Makefile or a task runner, so a source build on Linux or macOS means either PowerShell Core or running the .NET CLI directly. The README badge points at an AppVeyor project, so continuous integration for this path ran on AppVeyor rather than on the GitHub Actions workflows common in newer repositories. The `.github/` directory exists, but the release notes do not describe it as the primary CI.

Two build systems for one application is exactly the cost you would expect from a tool that has to support whatever machines its players have, and it is a cost a new contributor pays at the very first step.

Repository housekeeping that hints at the maintenance workflow

Several root files describe how the project is kept current rather than what it does. `renovate.json` configures automated dependency updates, `cliff.toml` configures generated changelogs, `crowdin.yml` manages localization, and `ISSUE_TEMPLATE.md` and `CONTRIBUTING.md` shape incoming contributions. There is also a `PRIVACY.md` and a `SOURCES` file listing where the project's assets come from.

The release notes confirm the automation is doing real work. A large share of the entries in 5.2.4 and 5.2.5-beta0 are dependency bumps, and the contributor lists include `renovate[bot]` alongside named human contributors. In the 5.2.5-beta0 notes, the human-authored changes are small: Windows Phone legacy support, world property reconciliation and settings UI tweaks, with the rest being a Jint update and MonoGame content builder updates.

Jint is a JavaScript interpreter for .NET, and its presence as a maintained dependency suggests the editor evaluates user or config JavaScript somewhere in its workflows. The README does not document that as a feature, so treat it as an implementation detail visible only in the dependency list rather than a supported extension point.

`tiles.json` at the root and the `schematics/` directory suggest that tile definitions and reusable building shapes are maintained as data, which is how an editor supports thousands of Terraria tile variants without a source change per tile.

A changelog link that points at the wrong branch

One inconsistency is worth flagging for anyone verifying the project's history. The repository's default branch is `main`, and the README badge and pull links reference `main`. But the README's Change Log link points at `github.com/TEdit/Terraria-Map-Editor/commits/master`, naming a branch that is no longer the default.

Both facts come from the repository itself, and neither cancels the other. The practical reading is that the branch was renamed from `master` to `main` and one link in the README was not updated. If you follow that Change Log link expecting history, expect a redirect, a 404, or a page that no longer reflects current work. The GitHub Releases page, which the README also links, is the reliable place to read what changed, and the generated changelogs configured by `cliff.toml` suggest release notes are compiled from commit history rather than maintained by hand.

The licensing picture has a similar gap. The repository is tagged NOASSERTION, which is what GitHub reports when its license detection is not confident, yet a LICENSE file is present in the root. A named license file and an unrecognized license field are not the same claim, and the difference matters if you intend to contribute artwork, translations or code. Crowdin handles translations under its own terms, and the `SOURCES` file presumably credits the assets, but neither is a substitute for reading the LICENSE text. Treat the terms as unsettled until you read it.

Where TEdit sits against the other map editors

The alternative approaches split along two lines. The first is editing in game with a mod. Terraria has a large mod scene, and world-editing mods give you tile brushes inside the running game, with the enormous advantage that they cannot produce a file the game refuses to load, because the game is the one saving it. The cost is that you need a working mod setup and a world you are willing to play in while editing.

The second is an offline editor, which is what TEdit is. The advantage is separation: you design without the game running, you can open a world you cannot currently play, and you have undo, layers of metadata and settings editors that a mod UI would not bother to build. The cost is the version coupling described above, plus the fact that a hand-built world has to satisfy every constraint the game enforces, including tile reachability and NPC spawn rules, and TEdit will happily let you save a world that fails those checks.

Mobile and online map editors also appear repeatedly in search traffic around this project. Those are separate products with separate constraints, usually web-based or Android apps with limited format coverage. The version banner in every TEdit release is a good filter: a tool that does not name the world file version it supports is not tracking Terraria's format closely enough to be a substitute for one that does.

For read-only inspection, TEdit's own view of a world is faster than launching the game. For anything you intend to keep, match the TEdit build to your Terraria version first.

Editorial conclusion

TEdit is the tool to reach for when you want a Terraria world you designed rather than one you rolled, and it covers more than tile painting: world settings, chest contents, signs, NPCs and rewards are all editable. Its hard constraint is version coupling. A build is valid only for the exact Terraria version it was written against, so a player mid-update should wait for a matching TEdit build instead of opening an older one. The repository is C# with a MonoGame and Avalonia lineage and moves quickly, with the last push on 2026-09-28 and releases through August. One thing to settle before building from source: the repository is tagged NOASSERTION for licensing while a LICENSE file sits in the root, and only someone who reads both can say what applies. Grab a release build from the GitHub releases page first, and read the 1.4.5.8 support note on 5.2.5-beta0 before saving over a world you care about.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. TEdit/Terraria-Map-Editor on GitHub