Keeping maps, encounter material, creature statistics, and campaign notes inside one Obsidian vault addresses a very specific frustration: the disruption of jumping between a world-building tool and a separate virtual tabletop. Fabian presents Atlas as his solution to that problem, and the integration goes considerably deeper than simply displaying maps inside Obsidian. Notes can be pinned directly to locations, maps can link to other maps, tokens can connect to stat blocks, and those relationships remain part of the same campaign workspace.
The map functionality is especially convincing because several features are designed around actual session preparation rather than novelty. Atlas remembers map positions, supports nested maps, offers fog of war, drawing, measurement, configurable square and hex grids, and allows multiple scenes or snapshots to be created from the same underlying map. Restoring a snapshot takes only a moment in the demonstration, while the ability to locate a token directly from its associated stat block could be genuinely useful when a crowded encounter becomes difficult to manage.
Integration with existing Obsidian material is another major strength. Fantasy Statblocks content can be attached to tokens, recognized dice expressions can be rolled directly, and pinned notes can be previewed or edited without abandoning the map. The asset manager adds collections, folders, tags, filters, encounters, token and map importing, and campaign exports. Most importantly, exporting a collection can include the interconnected maps, tokens, stat blocks, and notes, making Atlas useful not only for running a campaign but potentially for packaging one for another user.
The player-view system reflects Fabian's own hybrid tabletop workflow particularly well. A second window can mirror the game master's map on another display, while the GM can control which grid elements, resource bars, images, and other information players see. Freezing the player camera while preparing something elsewhere, then returning everyone to the desired view, is a thoughtful touch. Showing an image from an Obsidian note directly on the player display also turns material already stored in the vault into usable presentation content without requiring another application.
Atlas is presented as completely free, open source, offline, local, and free of accounts, advertising, telemetry, and built-in AI features. Those are claims about the project's current design and intentions rather than independently demonstrated guarantees here, but they form a coherent philosophy around user ownership. The ability to move ordinary files, export campaign collections, modify the source code, and integrate other Obsidian plugins reinforces that philosophy more concretely than the repeated assurances alone.
The walkthrough becomes less effective when it tries to cover nearly everything at once. Asset filters, imports, widgets, resource bars, initiative tracking, timers, clocks, keyboard shortcuts, theme integration, reporting tools, snapshots, and collection settings arrive in rapid succession, often accompanied by improvised commentary and small detours. Fabian is clearly comfortable with his own software, but newcomers are asked to absorb a substantial amount of terminology and interface behavior without a tightly structured beginner workflow. The demonstration also naturally reflects the developer's perspective; it shows what Atlas can do, but provides little evidence about installation friction, stability during extended play, multiplayer limitations, or how easily an unfamiliar user can learn it.
Even so, the presentation succeeds at showing that Atlas is more than a rudimentary map viewer. System-agnostic widgets, customizable counters and timers, hotkeys, theme support, initiative tools, player-facing controls, and extensibility suggest a project designed around flexible tabletop workflows rather than one particular ruleset. The strongest case is consequently not that Atlas replaces every dedicated VTT for every group, but that players already invested in Obsidian can consolidate a surprising amount of campaign preparation and tabletop management into the environment where their material already lives.
Pros
- Deep integration between maps, Obsidian notes, tokens, stat blocks, dice rolls, and existing vault content.
- Snapshots, nested maps, persistent positions, token locating, and multiple scenes provide practical campaign-preparation tools.
- Player view includes useful controls for camera behavior, grids, resource visibility, initiative, and presenting images.
- Collections, tagging, filtering, encounters, and comprehensive exports give the asset system substantial depth.
- Local-first, offline, open-source design fits naturally with Obsidian's file-based workflow.
- Keyboard shortcuts, configurable widgets, themes, and system-agnostic options provide considerable customization.
Cons
- The feature-heavy walkthrough becomes sprawling and can be difficult for a newcomer to absorb.
- Frequent conversational detours and improvised demonstrations weaken the organization of an otherwise informative showcase.
- Installation, initial setup, and a simple start-to-finish beginner workflow receive relatively little attention.
- The developer demonstration cannot establish long-term stability, ease of use for unfamiliar users, or how Atlas compares under real campaign conditions with dedicated VTT platforms.
Atlas makes a persuasive case for keeping campaign management and tabletop play inside the same Obsidian environment, with unusually deep connections between maps, notes, creatures, encounters, and player-facing material. The walkthrough could introduce that depth more methodically and leaves some practical questions unanswered, but it demonstrates an ambitious and thoughtfully integrated tool with clear value for Obsidian-centered tabletop groups.
