Terraria separates identity from environment: player characters live in .plr files and worlds live in .wld files. That makes a complete backup a two-part job. Copy both directories, including .bak companions, before editing or moving systems. Steam can independently move individual characters and worlds to cloud storage, so an apparently missing local file may have a counterpart under Steam userdata. SaveEditor.com keeps those locations distinct instead of presenting one universal Terraria save path.
Known Terraria save-file structure
The researched filename or folder pattern is Players*.plr
Worlds*.wld
*.bak. File-extension context: .plr, .wld, .bak The documented format notes are: Characters and worlds are separate files: .plr for players and .wld for worlds. Local .bak companions can provide rollback material. Multiplayer characters and worlds should therefore be backed up as separate sets.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. A world file and a player file have different structures and cannot replace one another. Cloud status can also differ per file. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: Windows: %USERPROFILE%DocumentsMy GamesTerraria
Steam cloud copies may appear under <Steam-folder>userdata<user-id>105600remoteplayers and worlds | macOS: $HOME/Library/Application Support/Terraria/ | Linux / Steam Play: $XDG_DATA_HOME/Terraria/ (normally ~/.local/share/Terraria/). Storefront context: Steam, GOG Galaxy. Steam can keep cloud-designated player/world files under its userdata remote tree. The normal local Terraria directory still separates Players and Worlds. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
Back up both Players and Worlds plus their .bak files. If a character and world belong together, keep them in the same dated archive even though they are separate files. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam Cloud and GOG Galaxy are documented. On Steam, cloud movement is enabled per character/world rather than being assumed for every local file. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: If a character or world is missing, check both the local directory and Steam remote location. Before using a .bak copy, preserve the current .plr/.wld and the backup so the recovery remains reversible. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Windows/macOS/Linux locations, .plr/.wld patterns, Steam remote paths, and per-item Steam cloud behavior were reviewed against current PCGamingWiki coverage.