Comparison · Tools

DSMapStudio vs Smithbox: Complete Comparison (2026)

Tested on v1.11.1 Updated 2026-06-09

DSMapStudio vs Smithbox: Complete Comparison (2026)

Mod FromSoftware games for any length of time and you hit this fork: tutorials point at DSMapStudio, but people keep recommending Smithbox for newer Elden Ring patches — and it's not obvious whether they're rivals, whether you need both, or which your mod should use. Smithbox is a direct fork of DSMapStudio, actively maintained by vawser, while DSMapStudio's last release (v1.11.1, June 2024) is now effectively a stable legacy build. Same DNA, same core editors; the deciding factors are your game, your patch, and whether you need ongoing updates. This isn't about a "winner" — both are open-source and built on the same foundation.

Quick answer

  • DSMapStudio for pre–Shadow of the Erdtree Elden Ring and the Souls games (Demon's Souls, Dark Souls 1–3, Bloodborne, Sekiro) — stable, proven, what most tutorials assume.
  • Smithbox for the latest Elden Ring patches (1.12+, post-SotE) and the most current AC6 support, or whenever you want active bug fixes and don't want to unpack your game first.

On current Elden Ring, the practical answer is almost always Smithbox. On an older guide or a Souls game, DSMapStudio is perfectly fine.

What each one is

DSMapStudio — the original integrated modding tool: Map, Param, and Text editors in one application across nine titles. The foundation the community standardized on, and what most written tutorials (including this site's) assume. Last release v1.11.1 (June 2024); development has effectively moved to its fork, so it no longer gets updates for new game patches, but for everything it already supports it stays reliable.

Smithbox — a direct fork of DSMapStudio by vawser. It inherits the editors and adds continued development: newest Elden Ring patches, current AC6, ongoing fixes and quality-of-life. The most noticeable practical difference for a new user is that Smithbox doesn't require UXM unpacking — it reads the game's packed files directly, removing DSMapStudio's most error-prone setup step. Because it's a fork, the editing concepts transfer either direction.

Feature comparison

FeatureDSMapStudioSmithbox
Map Editor
Param Editor
Text Editor
Latest Elden Ring (1.12+ post-SotE)
Elden Ring pre-1.12
Dark Souls 1–3, Bloodborne, Sekiro
Armored Core 6Experimental
Requires UXM unpackingYesNo
Active development✗ (legacy, v1.11.1)
Open-source (MIT)

Game compatibility

GameDSMapStudioSmithboxRecommended
Elden Ring 1.12+ (post-SotE)Smithbox
Elden Ring pre-1.12Either
Armored Core 6ExperimentalSmithbox
Dark Souls 3Either
Dark Souls: Remastered / PTDEEither
Dark Souls 2: SOTFSEither
BloodborneEither
SekiroEither
Demon's SoulsEither

When to use DSMapStudio

When you're modding a game it fully supports and stability matters more than new features: the Souls trilogy, Bloodborne, Sekiro, Demon's Souls, and pre-1.12 Elden Ring. Also when you're following an existing written tutorial (including this site's), since the menus and steps line up exactly — and when a mod you're collaborating on was built against DSMapStudio and a specific game version, matching the tool avoids friction.

When to use Smithbox

On current Elden Ring (1.12+), modding Armored Core 6, or whenever you want a tool still getting fixes — plus the easier first-time setup from skipping UXM. If you keep hitting "Unknown DCX format" because your game auto-updated past what v1.11.1 reads, switching to Smithbox is the direct fix that keeps you on the latest patch.

Can you use both?

Yes — separate portable apps, so installing one doesn't affect the other, and many modders keep both (DSMapStudio for an older project or a Souls game, Smithbox for current Elden Ring). Both edit the same regulation.bin and map files, so the game-side output is compatible. Just don't share a single tool's project folder between them blindly — treat each project as belonging to the tool that created it, and keep vanilla baselines matched to the game version.

The relationship

Think of Smithbox not as a competitor but as the successor — a fork that picked up active development where DSMapStudio's slowed, on the same codebase and concepts. DSMapStudio remains the foundation that established the integrated Map/Param/Text workflow; Smithbox carries it forward to the newest games and patches. Everything Smithbox does well, it does because DSMapStudio built the base first.

Pick by game and patch, not loyalty. New and on current Elden Ring? Start with Smithbox. Following the guides here or modding a Souls game? Install DSMapStudio, create a project, and for combining Elden Ring mods the merge regulation.bin guide applies to both tools. Patch-compatibility details: Unknown DCX format and the Elden Ring setup page.

Watch it in action

Community video guides this article draws on — credit to their creators.

Smithbox Installation Guide & Param Editing / CSV Importing — Elden Ringby Ryvaris · watch on YouTube →