Released in 2016, Dark Souls III is an action role playing game developed by FromSoftware and published internationally by Bandai Namco Entertainment for PlayStation 4, Xbox One, and Windows PC. Speedrunning it is a race through a bleak, interconnected world built around stamina based movement, precise combat, and boss gates that define progression. A typical run is less about “clearing everything” and more about choosing the shortest reliable path to an ending, building just enough power along the way to keep mandatory fights fast and consistent.
It speedruns well because its core systems reward clean execution and smart routing. Sprinting, rolling, and stamina management create a constant tradeoff between raw speed and survival, while bonfires and warps let runners structure the run around efficient checkpoints rather than long backtracks. The game’s layouts are stable and learnable, but enemy behavior and boss patterns add just enough variability that top runs still feel “alive,” with runners adapting on the fly instead of following a single script. What makes Dark Souls III distinct from many similar action RPG speedruns is how tightly its movement, resource decisions (levels, upgrades, and equipment), and boss strategy intertwine: the fastest routes are usually the ones that minimize detours while still setting up a small number of high leverage upgrades that turn major fights into quick, repeatable executions.
Dark Souls III speedrunning grew out of an already organized Souls scene, so its earliest routes did not form in a vacuum. Early record keeping was anchored by public leaderboards on Speedrun.com, with discussion and routing knowledge circulating through the long running Souls community spaces that fed into the modern SoulsSpeedruns hub. Runs were shared widely through early video uploads and livestream archives on YouTube and Twitch, while broader conversation and quick route notes also surfaced on places like Reddit alongside dedicated community channels.
The first “standard” goal settled quickly into what most players intuitively think of as a completion run: start a fresh character and finish the game, with categories defined by how many restrictions the runner accepts rather than by reinterpreting the endpoint. Just as important as the goal was the timing norm. Because load times and framerate vary heavily across platforms and setups, the scene standardized on in game time (IGT) as the official measure, and built end of run proof around showing the game’s recorded time after the ending requirements are met. That decision shaped early competition, since it moved the focus away from hardware dependent loading differences and toward clean execution, consistent routing, and boss strategy.
As the game’s life cycle progressed, route formation became tied to version realities. Some of the most influential early routes were defined by specific tricks and the patch environments where those tricks were practical, which is why Dark Souls III eventually developed clear version policies and category splits instead of treating “Any%” as a single timeless ruleset. You can still see that lineage in how the scene separates downpatched glitch categories from “current patch” play, and in how certain major strategies became important enough to justify their own category identity rather than being handled as informal gentleman’s agreements.
As Dark Souls III matured into a long running speedgame, its community developed around a familiar division of labor: a public archive where categories and results are preserved, and a set of faster moving discussion spaces where routes, tech, and rulings get debated in real time. The public record lives on Speedrun.com, where categories, rules, moderator rosters, and accepted submissions are centralized and easy to reference.
Day to day organizing happens in places built for conversation and iteration. The Souls speedrunning scene maintains an active Discord server where runners share splits, troubleshoot setups, propose rule clarifications, and circulate new discoveries, with links surfaced directly from the game’s hub pages so newcomers can find the right room quickly. Broader discussion also spills into platforms like Reddit, while runs and learning culture are heavily shaped by streaming and VOD ecosystems on Twitch and YouTube, where tutorial videos, marathon style showcases, and personal progression logs help turn private practice into shared knowledge.
Verification culture is formal enough to protect competitive integrity, but practical enough to keep the boards moving. Runs are submitted to Speedrun.com with the required proof and category compliance, then reviewed by moderators against the posted rules and the expectations those rules imply, such as clear run visibility and any defined evidence requirements. In the background, site level moderation guidelines frame what moderators are responsible for and how quickly submissions should be processed, which helps keep communities aligned on what “normal” looks like even when games have very different submission volumes.
Knowledge preservation is where Dark Souls III’s scene feels especially “Souls like” in its craftsmanship. In addition to the leaderboard ruleset, the community maintains a dedicated reference hub at SoulsSpeedruns, which serves as a stable home for rules, category definitions, and the kinds of routing notes that would otherwise disappear into chat logs. The result is a culture where new runners can enter through the public boards, level up through shared documentation and tutorials, and eventually contribute back by refining strategies and helping keep standards consistent.
On speedrun.com, Dark Souls III’s leaderboard structure is built around a handful of “mainline” goals that tell you what the community considers a complete run. The headline categories cover beating the game as fast as possible (Any%), clearing every boss encounter (All Bosses), and then offering parallel boards for Glitchless versions of those goals. The scene also keeps separate spaces for rulesets that intentionally limit certain high-impact strategies (Any% Restricted), as well as a “latest version” ruleset meant to keep everyone on a shared modern baseline (Any% Current Patch). For runners who want a tighter scope or a harder constraint, there are boards like All Bosses (No DLC) and All Bosses (SL1).
Even though you will see real time in streams and splits, the public record is primarily tracked as in-game time (IGT). Using IGT matters in Dark Souls III because it largely neutralizes hardware and load-time differences across platforms, and it makes comparisons cleaner when runners are on different setups. Because IGT is the standard, runs are expected to show their final IGT on the Load Game screen, and the ruleset explicitly allows common “check-the-clock” behaviors like quitting out or force-closing the game so the IGT can be displayed for verification.
Category definitions also come with specific finish requirements so there is no ambiguity about what “counts.” For the main completion categories hosted on the Souls community ruleset, a run is considered complete when the game reaches the end-state tied to linking the flame and the runner advances through the post-ending prompt (the moment where the game presents the choices for what to do next, such as beginning the next journey or returning to the title). That end condition is written to be easy to verify on video and consistent across runs.
The bigger “identity” decisions come from version policy and what the community permits in terms of setup. Downpatching is allowed, and several categories are associated with specific app and regulation versions because particular skips and techniques exist only on certain patches. The rules also draw a bright line against altering gameplay via mods or outside tools, require a fresh character rather than starting from a prepared save, and expect runs to be done offline to avoid network-side unpredictability. Together, those rules are meant to preserve comparability while still allowing the “intended” speedrun tech for each version-defined category.
Finally, the submission rules on speedrun.com shape what a legal VOD looks like. Dark Souls III moderators have formalized standards around things like long pauses in menu screens (so runs are not padded with extended breaks) and ensuring key gameplay elements are not hidden in the recording. The leaderboard also requires audible game sound in new submissions, with game music specifically excluded from meeting that requirement. These policies are less about route choice and more about making verification fair and consistent.
Dark Souls III runs became faster and more consistent as the community moved from “fast playthrough” routing into deliberate sequence-breaking. Instead of treating progression as a fixed chain of areas, runners began targeting the smallest set of mandatory gates, then building routes around skipping or collapsing whole segments of travel. Over time, that mindset produced a recognizable toolbox of skips and movement solutions that show up across multiple categories, even when the exact order of bosses and upgrades changes.
As discoveries accumulated, the route stopped being defined only by clean execution and started being defined by what the ruleset allowed. Techniques like boss and area skips, ladder and elevator clips, and other traversal breaks created “paradigm shifts” where the optimal run was no longer a slightly cleaner version of yesterday’s run, but a new structure entirely. Some strategies were powerful enough to earn special attention in category design, including rulesets that carve out specific high-impact glitches while still allowing the rest of the Any% ecosystem to breathe.
Version policy became part of the technical story because many headline tricks and damage expectations depend on patch behavior. The scene’s answer was to normalize downpatching for categories tied to particular versions, while also supporting modern rulesets that keep runners on a shared current baseline. That split lets historical routes remain playable and comparable without forcing every runner into the same patch environment.
Tooling helped convert that technical complexity into something trainable. Practice became more systematic with dedicated utilities like the Souls speedrunning practice tool and save management workflows that make it easier to drill individual skips, menus, or boss patterns without rebuilding a run from scratch each attempt. Timing and consistency also improved through standardized setups in tools like LiveSplit, where runners can activate the game time integration and compare against in-game time splits that match leaderboard expectations.
What emerged is a scene where “getting faster” is usually about reducing variance as much as raw speed. Boss strategies evolve toward repeatable posture, spacing, and stamina plans that limit unpredictable outcomes, while routes evolve toward fewer risky transitions and cleaner checkpoint usage. The end result is a mature style of Souls speedrunning where execution, knowledge, and rules literacy all matter, because the fastest run is often the one that is both technically ambitious and reliably reproducible.
One of the defining milestones for Dark Souls III speedrunning was the early shift from straightforward “fast completion” routing into full sequence-breaking, where a small number of high-impact glitches began to collapse huge pieces of intended progression. As headline techniques rose and fell with patch behavior, the community adapted by treating version choice as part of the competitive landscape rather than an inconvenience. That mindset encouraged formal version splits and normalized downpatching for categories tied to legacy tech, while still leaving space for “modern baseline” boards that prioritize consistency on the newest version.
A second milestone was the scene’s move toward durable infrastructure. Instead of letting route knowledge live only in chats and scattered videos, runners consolidated guidance into stable hubs and written notes, which made the game far easier to learn and helped standardize what “a real run” looks like across categories. The SoulsSpeedruns wiki became a reference spine for categories, terminology, and core resources, while speedrun.com’s guides and documents provided practical route notes that could be shared, revised, and taught from.
Marathon exposure also mattered, not because it “set records,” but because it shaped public understanding of what a Dark Souls III speedrun even is. Appearances at Games Done Quick events like Awesome Games Done Quick 2017, Awesome Games Done Quick 2019, and Summer Games Done Quick 2023 helped make the scene legible to outsiders by showcasing complete runs with commentary, route logic, and the difference between glitch-heavy categories and more “fight-forward” rulesets. That kind of visibility tends to raise the bar for presentation and verification, because a wider audience brings more attention to clarity, rules literacy, and reproducible standards.
Finally, the community’s embrace of in-game time as the competitive baseline became its own quiet milestone. By centering IGT and integrating it cleanly into common timing setups, the scene reduced the impact of hardware and load differences and pushed skill expression back toward execution, routing, and decision-making. That choice also reinforced a culture of shared tooling and shared expectations, where learning the timer, splits, and proof conventions is part of learning the run itself.
olzku23 – Any% – 24:57 – Aug 2025 (listed as “6 months ago” on Feb 11, 2026) – PC – A clear “new era” benchmark for the main category, and the run most mainstream coverage pointed to when people started talking about DS3 dipping under 25 minutes.
Fadis – Any% – 25:46 – Aug 2025 (listed as “6 months ago” on Feb 11, 2026) – PC – A key record-era marker right before the scene’s next major barrier fell, useful as a “what the route looked like just before the breakthrough” reference point.
owen_ – Any% – 28:58 – circa 2024 (listed as “2 years ago” on Feb 11, 2026) – PC – Representative of the modern sub-30 execution standard in unrestricted Any%, a good anchor run for the “mid-route refinement” era.
Distortion2 – Any% – 36:43 – circa 2017 (listed as “9 years ago” on Feb 11, 2026) – PC – One of the foundational public record entries on the modern leaderboard, and a useful bridge between the very early post-launch routing and later, more systematized optimization. (His earlier widely shared 56:19 WR post captures the “first big compression” period right after release.)
Daravae – Any% – 33:54 – circa 2020 (listed as “6 years ago” on Feb 11, 2026) – PC – A strong snapshot of the era where the leaderboard’s top end was consolidating around more mature skips and tighter execution, before later route revolutions pushed times down again.
davidtankre – Any% Restricted (No TearDrop) – 42:31 – circa 2019 (listed as “7 years ago” on Feb 11, 2026) – PC – A historically useful “restricted” benchmark from when the category’s identity leaned hard on conservative routing choices (notably “No Doll Skip” in the leaderboard route notes).
Metroid_Crafter – Any% Restricted (No TearDrop) – 43:06 – circa 2025 (listed as “10 months ago” on Feb 11, 2026) – PS5 – A good example entry for how modern restricted tech (shown as “Ladder Warp” in the leaderboard route notes) travels across platforms, not just PC.
Kuroko – All Bosses – 1:06:53 – circa 2025 (listed as “1 year ago” on Feb 11, 2026) – PC – A defining top-end marker for full-boss routing in the unrestricted All Bosses category, and a clean reference point for what the “fastest full clear” looks like.
R1ght – All Bosses Glitchless – 1:18:34 – Jan 2026 (listed as “1 month ago” on Feb 11, 2026) – PC – A standout for the most marathon-friendly “full clear” family, and a good anchor for explaining how glitchless All Bosses routes are organized (route label shown as “Early Watchers”).
FromSoftware. “DARK SOULS III Release Date Set for March 24, 2016.” Press release, September 12, 2015. Accessed February 11, 2026. https://www.fromsoftware.jp/ww/detail.html?csm=094
Steam. “DARK SOULS™ III.” Store page. Accessed February 11, 2026. https://store.steampowered.com/app/374320/DARK_SOULS_III/
PlayStation. “DARK SOULS III.” Store page. Accessed February 11, 2026. https://store.playstation.com/en-us/product/UP0700-CUSA03388_00-DARKSOULS3000000
Bandai Namco Entertainment America. “Enter the Frozen World of Dark Souls III: Ashes of Ariandel.” News release, October 25, 2016. Accessed February 11, 2026. https://www.bandainamcoent.com/news/ashes-of-ariandel-live
Bandai Namco Entertainment America Inc. “DARK SOULS III – Patch Version 1.15.2.” Announcements, January 12, 2023. Accessed February 11, 2026. https://www.bandainamcoent.com/news/dark-souls-iii-patch-1152
Steam News. “DARK SOULS™ III – Patch 1.15.2 Patch Notes.” January 12, 2023. Accessed February 11, 2026. https://store.steampowered.com/news/app/374320/view/3656393454659154048
Steam News. “DARK SOULS™ III – Dark Souls III regulation update 1.35.” June 14, 2017. Accessed February 11, 2026. https://store.steampowered.com/news/app/374320/view/4648234090309440970
Speedrun.com. “Dark Souls III.” Game leaderboard hub. Accessed February 11, 2026. https://www.speedrun.com/darksouls3
Speedrun.com. “Dark Souls III Resources.” Accessed February 11, 2026. https://www.speedrun.com/darksouls3/resources
Speedrun.com. “Any% in 24:57 by olzku23.” Run page. Accessed February 11, 2026. https://www.speedrun.com/darksouls3/runs/m3vq33qz
Speedrun.com. “Any% in 36:43 by Distortion2.” Run page. Accessed February 11, 2026. https://www.speedrun.com/darksouls3/runs/2ywx6p3m
SoulsSpeedruns. “Dark Souls III.” Wiki hub. Accessed February 11, 2026. https://soulsspeedruns.com/darksouls3
SoulsSpeedruns. “Rules.” Accessed February 11, 2026. https://soulsspeedruns.com/darksouls3/rules
SoulsSpeedruns. “Downpatching.” Accessed February 11, 2026. https://soulsspeedruns.com/darksouls3/downpatching
SoulsSpeedruns. “TearDrop.” Accessed February 11, 2026. https://soulsspeedruns.com/darksouls3/teardrop
SoulsSpeedruns. “Watchers Glitch.” Accessed February 11, 2026. https://soulsspeedruns.com/darksouls3/watchers-glitch
SoulsSpeedruns. “Soul of Cinder Glitch.” Accessed February 11, 2026. https://soulsspeedruns.com/darksouls3/soul-of-cinder-glitch
GitHub. veeenu. “darksoulsiii-practice-tool.” Repository. Accessed February 11, 2026. https://github.com/veeenu/darksoulsiii-practice-tool
FrankvdStam. “SoulSplitter.” Repository. Accessed February 11, 2026. https://github.com/FrankvdStam/SoulSplitter
Grimelios. “LiveSplit.DarkSouls.” Repository. Accessed February 11, 2026. https://github.com/Grimelios/LiveSplit.DarkSouls
Speedrun.com. “Any% Glitchless (Anri’s Straight Sword) Sharp +3 Beginner Route Notes.” Guide. Accessed February 11, 2026. https://www.speedrun.com/darksouls3/guides/fjebi
Games Done Quick. “Run Detail: Dark Souls 3 Any%.” BubblesDelFuego at Awesome Games Done Quick 2017. Accessed February 11, 2026. https://tracker.gamesdonequick.com/tracker/run/2117
Games Done Quick. “Dark Souls 3 by SayviTV in 1:01:45 – AGDQ 2018 – Part 148.” YouTube video. Accessed February 11, 2026. https://www.youtube.com/watch?v=Yb2zHjDIj7E
Games Done Quick. “Dark Souls 3 by ThorW in 1:27:47 – SGDQ2017 – Part 131.” YouTube video. Accessed February 11, 2026. https://www.youtube.com/watch?v=q1xYYnOk1D4
Kotaku. Patrick Klepek. “Dark Souls 3 Glitch Lets Speedrunners Completely Break The Game.” July 20, 2016. Accessed February 11, 2026. https://kotaku.com/dark-souls-3-glitch-lets-speedrunners-completely-break-1783985667
PC Gamer. Steven Messner. “Seven must-watch speedruns from Awesome Games Done Quick.” January 16, 2017. Accessed February 11, 2026. https://www.pcgamer.com/seven-must-watch-speedruns-from-awesome-games-done-quick/
PCGamesN. Sam Foxall. “AGDQ 2017’s Dark Souls 3 run shows the trials of marathon speedrunning.” January 15, 2017. Accessed February 11, 2026. https://www.pcgamesn.com/dark-souls-iii/dark-souls-iii-agdq-2017
GamesRadar+. “8 years after release, a stunning new Dark Souls 3 speedrun world record has been set.” August 3, 2025. Accessed February 11, 2026. https://www.gamesradar.com/games/dark-souls/8-years-after-release-a-stunning-new-dark-souls-3-speedrun-world-record-has-been-set-and-i-started-scratching-my-head-about-75-seconds-into-watching-it/
SteamDB. “DARK SOULS™ III Patches and Updates.” Accessed February 11, 2026. https://steamdb.info/app/374320/patchnotes/
darksouls3.wikidot.com. “Game Patches.” Accessed February 11, 2026. https://darksouls3.wikidot.com/game-patches