Released first in Japan in October 2009 and internationally in January 2010, Bayonetta is a single player action game developed by PlatinumGames and originally published by Sega for PlayStation 3 and Xbox 360, with later releases on Wii U, Windows PC, Nintendo Switch, PlayStation 4, and Xbox One. The game’s identity is built around fast, stylish combat and chapter based progression, which gives it a natural segmented rhythm that speedrunners can study, optimize, and repeat with consistency.
As a speedgame, Bayonetta thrives because it constantly offers the runner a choice between “safe” combat and “fast” combat. Its core toolkit rewards precision, especially the dodge timing that triggers Witch Time, and it layers that on top of weapon loadouts, magic driven burst damage, and mobility options that let you stay aggressive while moving through arenas and set pieces. A typical full game run is trying to do the obvious thing, reach the ending as quickly as possible, but the way it gets there is what makes it distinctive. The route is a constant negotiation between mandatory encounters and the fastest known ways to delete them, plus clean movement through traversal sections where small hesitations compound across a long, chapter to chapter game.
What separates Bayonetta from a lot of similar character action runs is how clearly the game communicates performance through its end of fight and end of chapter evaluation. The underlying system tracks things like time, combo points, and damage for scoring, which means the game itself is already built to notice efficiency, even if speedrunning is chasing pure completion time rather than ranks. On the public leaderboard side, the scene commonly frames full game play around New Game and New Game+ categories, with platform groupings such as PC and Console, and it records both real time and a load removed time to make comparisons fair across hardware and versions.
Bayonetta’s speedrunning roots formed in the way a lot of late 2000s action games did: players started timing themselves before there was a single, agreed upon public leaderboard. Early talk often treated “speedrun” as a practical challenge run built around what the game already tracked. People compared chapter performance through the in game Play History, worried about how updating times might overwrite earlier medals, and used separate save files to preserve unlock progress while still chasing faster clears.
Those early conversations also show how quickly the scene began testing the edges of what was possible. Even in casual forum advice, you can see the same pattern that later defines formal routing: find a way to keep the tools you want, then look for methods that let you bulldoze mandatory fights faster than intended. A good example is how quickly community chatter circulated the “infinite magic flute” idea as a way to trivialize resource constraints and accelerate combat, which is the kind of discovery that pushes a game from “fast playthrough” into a route shaped by specific tech.
As record keeping consolidated, the community’s “standard goal” for full game runs settled into categories that make sense for Bayonetta’s structure and unlock economy. On Speedrun.com, the public board centers on full game completions split between New Game Normal and New Game+, with additional rule sets and legacy groupings that preserve earlier competitive eras rather than erasing them. That framework reflects a long running reality of the game: because weapons and accessories matter, runners have always cared about which starting state the category assumes, not just the finish line.
Timing norms evolved alongside that formalization. For a long stretch the community treated versions as competing together and timed runs in real time, even while acknowledging that platform performance could change the feel of the run. As the leaderboard matured, standards tightened to reduce hardware advantages, especially once PC tooling made consistent load handling possible. That is why later rule updates introduced separate PC and console tracks, moved older submissions into legacy categories to preserve history, required PC runners to cap and display 60 FPS, enabled load removed submissions through LiveSplit’s game time comparison, and required console submissions to include bootup footage to establish an even start.
Re releases and ports were the background pressure behind many of those decisions. The community has long recognized that some versions run closer to a stable 60 FPS and load more quickly than others, and that installed copies often behave better than physical media. The result is an origins story that begins with informal chapter time bragging and forum experimentation, then gradually shifts into a ruleset built to keep different platforms comparable without pretending they all perform the same.
As Bayonetta’s routes solidified, the scene needed a central place where times, rules, and category definitions could live in public without getting lost across scattered posts and reuploads. For modern Bayonetta speedrunning, that “public record” role is filled by Speedrun.com, where the game’s page anchors the leaderboards and keeps the supporting infrastructure in the same place, including a forums space, a guides directory, a resources tab, and a clear submission pathway for new runs.
Over time, organization shifted into a two track rhythm that is familiar across a lot of speedgames. Fast conversation, quick questions, and informal troubleshooting tend to live on Discord, while rule changes and board level decisions are documented publicly in forum threads so they can be referenced later. The Bayonetta community itself has described using its Discord for sharing updates while still posting major announcements on the Speedrun.com forums, which reflects an intentional split between live discussion and permanent record keeping. In parallel, broader Bayonetta fandom spaces on Reddit sometimes act as a front door for newcomers looking for where the active community gathers, even when the actual speedrun standards live elsewhere.
Knowledge preservation in Bayonetta is also deliberately structural rather than personality driven. The game’s Speedrun.com hub collects guides that explain skips, boss strategies, and category level planning, and it also hosts practical runner tools like split files and save files so practice can start from a consistent base. Community posts have also encouraged runners to contribute or request additional resources, with the understanding that these shared docs and files become the long term memory of the scene.
On the verification side, the culture is built around traceable evidence and predictable process. A submitted run is expected to include a usable video, and timing is treated as what the video shows from the category’s start condition to its end condition, not merely what a timer overlay happens to display. Moderators are generally given a window to process submissions, and Speedrun.com’s own moderation guidance emphasizes both reasonable turnaround expectations and openness to feedback about rules and board organization through public forums or Discord.
On Speedrun.com, Bayonetta’s full game board is built around a small set of primary categories that function like the game’s Any% family. The core tracks are New Game Normal and New Game+, and the leaderboard also preserves a few variant rule sets as their own categories, including a dedicated NG Infinite Flute Glitch category and an NG+ Alfheim Rules category that formalizes how those optional challenge rooms are handled.
The board is explicit about what it is measuring and how it stays comparable across hardware. Full game runs are recorded in Real Time Attack, and the community also supports Load Removed Time as an additional timing method, so the same run can show both the real world completion time and a standardized time that removes loading where tools allow it.
A major identity choice for Bayonetta’s modern leaderboards is the platform policy. The game is split into PC and Console tracks, with the stated goal of keeping competition fair across different performance and loading conditions, while still preserving earlier submissions in legacy categories so the historical record is not lost. On PC, runners are required to cap and display 60 FPS throughout the run, and they may submit loadless timing using a LiveSplit setup that compares against Game Time. Console submissions, by contrast, are expected to include bootup footage as part of the verification standard.
Category structure also reflects how Bayonetta is actually played at a high level. The leaderboards include character filtering for full game runs, and the site also hosts Individual Level boards that separate chapters, with a rule toggle for Alfheim Rules versus No Alfheim Rules, which shows how significant those optional portals can be for defining what “counts” in a segment.
Finally, some rules are culture-setting rather than route-setting. Cosmetic and button prompt mods are treated as disallowed, which keeps visual presentation consistent for verification, while character choice itself is broadly accepted, including special cases like King Zero.
Bayonetta speedrunning matured around a simple idea: if you can keep attacking while you evade, you can turn “mandatory combat” into something closer to a movement section. The technique that best captures that evolution is dodge offset, which lets runners cancel into a dodge without losing their place in a combo string, so the run can stay aggressive while still staying safe. In practice, that means faster access to the heavy hitting enders the game rewards, and more consistent damage output even when the route is forcing you to fight.
From there, the scene’s biggest leaps came from combat tech that collapses boss health bars and shortens long encounters. The most famous example is the Durga and Lt. Col. Kilgore weapon swap sequence often called the Kilgore glitch, which uses a specific combo timing and a weapon set switch to produce an extremely high damage kick flurry, and runners explicitly pair it with dodge offset to keep it stable under pressure. When this kind of tech becomes reliable, the route stops being about surviving bosses and becomes about reaching each boss with the right tools and enough resources to execute the fastest known kill pattern.
Movement and traversal optimizations followed the same arc, from “run clean” to “use the game’s mobility system as a skip engine.” The community’s routing language is full of technique names because purchases and unlocks are part of the speed strategy, including options like Stiletto, After Burner Kick, and the Beast Within forms such as Panther Within and Crow Within. One long lived example of that mindset is the Panther Within jump into dodge burst, documented as a way to clear gaps that would otherwise force slower solutions, which illustrates how a single movement trick can change what a chapter even requires you to do.
Item and glitch usage also shaped the run into distinct branches. Magic flutes became more than a combat convenience because flute based behavior, including the well known “infinite flute” handling described by early players, enabled route ideas that either erase difficult fights or bypass sections that would otherwise be locked into slower pacing. That impact is large enough that the community preserves it as a separate competitive identity, with an explicit “NG Infinite Flute Glitch” leaderboard category alongside the standard New Game runs.
Finally, the run got faster and more consistent because the scene invested in tooling and standardization, not just new tricks. Modern Bayonetta competition separates PC and console runs, requires PC runners to cap and display 60 FPS, and supports load removed timing through LiveSplit integration, which reduces platform advantages and makes comparisons cleaner. Practice infrastructure also improved through shared resources, including category split files and downloadable save files hosted on the game’s Speedrun.com resources tab, which helps newer runners start from the same baseline and helps experienced runners grind specific segments efficiently.
One of the biggest milestones for Bayonetta speedrunning was the moment the game’s competitive history stopped living primarily in scattered posts and personal timing notes and started being preserved in a shared, structured archive. The Speedrun.com hub functions as that public record, and the existence of a deep guides library is part of what makes the scene feel “mature.” When a game has boss strategy writeups, skip tutorials, chapter specific tech pages, and standardized setup guidance all collected in one place, it changes how knowledge survives. It stops being a rumor passed runner to runner and becomes something newer players can study and build on.
A second landmark is the set of route overhauls that come from tech becoming reliable enough to plan around. Bayonetta is a game where one stable combat shortcut can reshape entire chapters because so much of the runtime is tied to mandatory fights and scripted set pieces. As the community documents these breakthroughs, they move from “trick” to “route spine,” and that is also when verification standards get sharper, because moderators and runners have to agree on what counts as intended play versus a category defining exploit. The fact that the leaderboards formally recognize separate rule identities, including a dedicated Infinite Flute Glitch category alongside the main New Game categories, shows how the scene chose to preserve different philosophies of play rather than force everything into one definition.
A third milestone is cross platform standardization, because Bayonetta’s feel and pace can change based on performance and loads. The community’s decision to separate PC from console submissions, introduce an autosplitter, require PC runs to cap and display 60 FPS, support load removed timing through LiveSplit integration, and move older submissions into legacy groupings was not only a rules update. It was a statement about competitive fairness and historical preservation at the same time, keeping the modern board consistent while still protecting the record of earlier eras.
Finally, marathon showcases have repeatedly acted as “watershed visibility” moments for the game. Bayonetta appeared in the Awesome Games Done Quick 2012 tracker during the early years of Games Done Quick, which is the kind of placement that signals a game is readable, exciting, and marathon friendly. More recently, Bayonetta returned as a featured full game run in Awesome Games Done Quick 2024, showing how the community’s modern route can serve both competition and audience storytelling.
Reclaimer — New Game Normal — 1:29:13 (LRT) / 1:30:43 (RTA) — Date achieved: “2 years ago” (as listed on Speedrun.com; relative to Feb 2, 2026) — Platform/version: PC (USA/NTSC), Jeanne — A modern benchmark run with detailed notes on movement and animation-cancel optimization, plus an explicit personal milestone of first achieving the category WR on May 14, 2022.
J62_GT — New Game+ — 1:10:20 (LRT) / 1:11:35 (RTA) — Date achieved: “1 year ago” (relative to Feb 2, 2026) — Platform/version: PC (JPN/NTSC), Normal, Bayonetta — A fast New Game+ Normal reference run, with the VOD flagged “video at risk” (useful to archive for long-term historical tracking).
J62_GT — New Game+ — 1:11:41 (LRT) / 1:12:58 (RTA) — Date achieved: “1 year ago” (relative to Feb 2, 2026) — Platform/version: PC (JPN/NTSC), Non-Stop ∞ Climax, Bayonetta — A top-end example of how New Game+ routing shifts under the highest difficulty ruleset, also carrying the “video at risk” flag.
Reclaimer — New Game Normal — 1:35:46 (RTA) — Date achieved: “1 year ago” (relative to Feb 2, 2026) — Platform/version: XboxOne (USA/NTSC), Jeanne — A clear “console benchmark” run with notes on port-specific quirks (performance, audio, and some hit/weave oddities), which is exactly the kind of detail that becomes valuable when comparing versions over time.
psychedelist — New Game Legacy — 1:37:53 (LRT) — Date achieved: “4 years ago” (relative to Feb 2, 2026) — Platform/version: PC (EUR/PAL), Jeanne, No Infinite Flute Glitch — A preserved “Legacy” snapshot from before the modern PC/console separation and submission requirements, useful for understanding how the board’s standards evolved.
Rouxls_ — New Game Legacy — 1:58:31 (LRT) — Date achieved: “6 years ago” (relative to Feb 2, 2026) — Platform/version: PC (USA/NTSC), Bayonetta, No Infinite Flute Glitch — An older “Obsolete” Legacy-era run (with a “video at risk” notice) that still matters as part of the preserved competitive record.
Mr. — New Game Legacy — 2:09:40 (RTA) — Date achieved: “5 years ago” (relative to Feb 2, 2026) — Platform/version: PS4, Bayonetta, No Infinite Flute Glitch — Notable partly because the moderator note shows hands-on verification (the run was retimed after a submission error), which is the kind of governance detail that shapes a leaderboard’s credibility.
PlatinumGames. “Bayonetta.” Accessed February 2, 2026. https://www.platinumgames.com/works/bayonetta
Sega. “Bayonetta.” Accessed February 2, 2026. https://www.sega.com/bayonetta
Nintendo. “Bayonetta for Nintendo Switch.” Accessed February 2, 2026. https://www.nintendo.com/us/store/products/bayonetta-switch/
Steam. “Bayonetta on Steam.” Accessed February 2, 2026. https://store.steampowered.com/app/460790/Bayonetta/
PlayStation Store. “Bayonetta.” Accessed February 2, 2026. https://store.playstation.com/en-us/product/UP0177-CUSA07111_00-BAYONETTACP10000
Wikipedia. “Bayonetta (video game).” Accessed February 2, 2026. https://en.wikipedia.org/wiki/Bayonetta_(video_game)
Speedrun.com. “Bayonetta.” Accessed February 2, 2026. https://www.speedrun.com/bayonetta
Speedrun.com. “Bayonetta – Guides.” Accessed February 2, 2026. https://www.speedrun.com/bayonetta/guides
Speedrun.com. “Bayonetta – Resources.” Accessed February 2, 2026. https://www.speedrun.com/bayonetta/resources
Speedrun.com. “Bayonetta Series.” Accessed February 2, 2026. https://www.speedrun.com/series/bayonetta_series
Speedrun.com. “Update on the Leaderboards, PC + Console Submission Requirements, & Autosplitter.” Forum thread. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/forums/o70h5
Speedrun.com. “Note about version differences.” Forum thread. Accessed February 2, 2026. https://www.speedrun.com/id-ID/bayonetta/forums/dw220
Speedrun.com. “Are cosmetic mods allowed in runs?” Forum thread. Accessed February 2, 2026. https://www.speedrun.com/es-ES/bayonetta/forums/r3wxn
Speedrun.com. “An update of sorts.” Forum thread. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/forums/lm55a
Speedrun.com. “New Game Normal in 01:38:06 by fgsame.” Run page. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/runs/ydwj8n0m
Speedrun.com. “New Game+ Normal Legacy in 01:47:46 by Reclaimer.” Run page. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/runs/ywk1283y
Speedrun.com. “New Game Normal in 01:34:17 by J62_GT.” Run page. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/runs/zng6xq8m
Speedrun.com. “New Game Legacy in 01:58:31 by Rouxls_.” Run page. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/runs/yojjgnjm
Speedrun.com. “New Game Legacy in 02:49:27 by DECosmic.” Run page. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/runs/me4owjqy
Speedrun.com. “New Game Normal Console in 02:20:13 by Iona_Rose.” Run page. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/runs/mk8gpg5m
Speedrun.com. “NG+ Infinite Flute Glitch in 02:11:59 by dreagledr.” Run page. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/runs/8y871xdz
Speedrun.com. “NG Infinite Flute Glitch in 03:33:21 by RJFritz.” Run page. Accessed February 2, 2026. https://www.speedrun.com/bayonetta/runs/zp4k5q8z
Speedrun.com. “Site Rules.” Accessed February 2, 2026. https://www.speedrun.com/support/learn/site-rules
Speedrun.com. “Moderation Rules.” Accessed February 2, 2026. https://www.speedrun.com/support/learn/moderation-rules
Games Done Quick. “Awesome Games Done Quick 2024 Schedule.” Accessed February 2, 2026. https://gamesdonequick.com/schedule/46
Games Done Quick. “Run Index – Awesome Games Done Quick 2024.” Accessed February 2, 2026. https://tracker.gamesdonequick.com/tracker/runs/AGDQ2024
Games Done Quick. “Run Detail – Awesome Games Done Quick 2012 (bayonetta).” Accessed February 2, 2026. https://tracker.gamesdonequick.com/tracker/run/923
Speed Demos Archive. “Bayonetta.” Speed Demos Archive Knowledge Base. Accessed February 2, 2026. https://kb.speeddemosarchive.com/Bayonetta
Speed Demos Archive. “Bayonetta.” Forum post thread. Accessed February 2, 2026. https://forum.speeddemosarchive.com/post/bayonetta_150.html
Speed Demos Archive. “Full Game List (Alphabetical).” Accessed February 2, 2026. https://speeddemosarchive.com/gamelist/
GameFAQs. “Question about Speedrun.” Bayonetta message board thread (April 10, 2010). Accessed February 2, 2026. https://gamefaqs.gamespot.com/boards/946346-bayonetta/54315021
GameFAQs. “Can someone explain Dodge Offset to me?” Bayonetta message board thread (February 3, 2010). Accessed February 2, 2026. https://gamefaqs.gamespot.com/boards/946346-bayonetta/53348462
GameFAQs. “How do you do the Kilgore glitch.” Bayonetta message board thread (September 11, 2011). Accessed February 2, 2026. https://gamefaqs.gamespot.com/boards/946346-bayonetta/60296834
GameFAQs. “Bayonetta – dodge offset help!” Bayonetta message board thread (November 27, 2010). Accessed February 2, 2026. https://gamefaqs.gamespot.com/boards/946346-bayonetta/57289943
GameFAQs. “The Bayonetta Combat Guide.” Bayonetta message board thread (December 20, 2010). Accessed February 2, 2026. https://gamefaqs.gamespot.com/boards/946346-bayonetta/57542774?page=2
Glitch City Laboratories Archives. “Bayonetta Leg gun glitch/exploit.” Forum thread (February 6, 2015). Accessed February 2, 2026. https://archives.glitchcity.info/forums/board-120/thread-7189/
Reddit. “Any tips for a new Bayonetta runner?” r/speedrun thread. Accessed February 2, 2026. https://www.reddit.com/r/speedrun/comments/292m9p/any_tips_for_a_new_bayonetta_runner/
Reddit. “Is there an official Bayonetta Discord server?” r/Bayonetta thread. Accessed February 2, 2026. https://www.reddit.com/r/Bayonetta/comments/11zvphx/is_there_an_official_bayonetta_discord_server/
Reddit. “AGDQ 2024 – Bayonetta speedrun by Reclaimer.” r/Bayonetta thread. Accessed February 2, 2026. https://www.reddit.com/r/Bayonetta/comments/199mvoi/agdq_2024_bayonetta_speedrun_by_reclaimer/
YouTube. “Bayonetta Speedrun Skips Tutorial & Explanation.” Accessed February 2, 2026. https://www.youtube.com/watch?v=U53IwaLxRVA
YouTube. “Advanced Bayonetta speedrun movement tutorial.” Accessed February 2, 2026. https://www.youtube.com/watch?v=ZEp1LnpQatE
YouTube. “Bayonetta Speedrunning Boss Fight Strategies.” Accessed February 2, 2026. https://www.youtube.com/watch?v=6SWUYMdJBd0
YouTube. “Bayonetta Speedrun Strat (for New Game+).” Accessed February 2, 2026. https://www.youtube.com/watch?v=AA5XqKNk1W4
YouTube. “Bayonetta by Galasrinie in 1:46:15 – Fleet Fatales 2020.” Accessed February 2, 2026. https://www.youtube.com/watch?v=3OM-1VRoZIc
LiveSplit. “LiveSplit.” Accessed February 2, 2026. https://livesplit.org/