Released in 1995, Chrono Trigger is a Japanese role-playing game developed and published by Square for the Super Nintendo Entertainment System, with later releases and ports handled under Square Enix across platforms that include PlayStation, Nintendo DS, and Windows. Its identity as a speedrun game is rooted in the same design choices that made it stand out as an RPG in the first place: time travel as a core structure, a story built around jumping between eras, and a famous set of multiple endings tied to when and how you reach the final confrontation. It also introduced New Game Plus, which matters for speedrunning because it creates a completely different kind of “completion” experience where routing is built around carrying power forward rather than building it from scratch.
Chrono Trigger speedruns tend to feel fast and readable for an RPG because the game minimizes friction between movement and combat. Many enemies are visible on the field, and when fights do happen they play out directly on the map instead of cutting away to a separate battle screen, which keeps momentum high and makes avoidance, positioning, and clean pathing a real skill. From there, the run becomes an optimization problem with several layers: moving through towns and dungeons with minimal detours, keeping menus tight, choosing battles that give the right payoff, and shaping party growth so key fights stay consistent without forcing extra grinding. The time travel structure and flexible access to Lavos underpin many route themes, because the game’s narrative “when” is also a gameplay lever runners can exploit.
What makes Chrono Trigger distinct from many other classic JRPG speedgames is how naturally it supports multiple competitive “flavors” under one umbrella. The public leaderboard ecosystem on Speedrun.com reflects that variety with platform boards (including SNES, DS, and PC glitchless) and category families that range from straightforward completion goals (Any%, 100%, All Endings, New Game+) to challenge formats like Low Level, alongside more technical variants such as “Save Corruption.” In practice, that means Chrono Trigger attracts both runners who love clean, low-friction RPG routing and runners who prefer high-ceiling execution built around glitches and rule-defined shortcuts.
Early Chrono Trigger speedrunning took shape in the “archive era,” when the most visible records were preserved as full runs with long-form notes rather than as a constantly updating leaderboard. Speed Demos Archive is a clear window into that stage of the scene: it didn’t just host times, it documented how runners thought about the game, how they segmented or single-segmented attempts, and how they justified route choices in writing. That style of record keeping mattered for an RPG, because the run is as much about planning and consistency as it is about raw execution, and early runners needed a place where that planning could be explained and reviewed.
In those early public records, the default platform focus was the original Chrono Trigger on SNES, and the earliest “standard goal” was straightforward in concept even if it was complex in practice: reach and defeat Lavos as quickly as possible on a fresh file. The runs that got preserved from that period read like a blueprint for what would become modern routing: tighten menu settings, avoid fights wherever possible, take only the battles that pay for themselves, and build the party’s tech progression to keep major bosses stable without detouring into grind. In one prominent early SDA run write-up, the runner explicitly calls out learning enemy avoidance from earlier videos and using community knowledge to beat Lavos before acquiring late-game mobility, which captures the defining early loop of the scene: watch, adapt, document, and refine.
Timing norms also began with a “community-specific rulebook” rather than a single universal standard. On SDA, full-game Chrono Trigger runs were timed using a hybrid approach tied to the game’s internal timer (with real time added afterward), while New Game+ was treated differently under a real-time rule “from start of control,” and the endpoint was defined precisely as the appearance of the final damage number on Lavos. That kind of specificity is exactly what an early scene needs, because it turns “beat the game fast” into something that can actually be compared and verified.
Definitions for completion categories evolved in parallel with those timing norms. Even in the early era, “100%” was not left as a vague promise, but anchored to an in-game checklist, such as completing the optional side quests that Square Enix baked into the late-game structure so that Gaspar confirms there’s nothing left but Lavos. Meanwhile, outside of formal archives, players debated the same boundary questions in places like GameFAQs, especially around New Game+ where “completion” can feel blurrier because power carries forward and the intended progression assumptions shift. Those debates helped push the scene toward clearer written rules over time.
As the game’s re-releases and ports spread across platforms, the scene gradually moved toward a more centralized public ledger on Speedrun.com, where version and platform differences could be reflected as distinct boards rather than arguments inside one category. That’s also where later “branching realities” of the game began to solidify into formal splits, including the separation of heavily glitch-driven play from glitchless expectations, and even specialized branches centered on save corruption. Tool-assisted research and publication culture around TASVideos made some of those boundaries unavoidable by demonstrating just how radically corrupted-save techniques could reshape what “Any%” even means for Chrono Trigger.
Chrono Trigger’s speedrunning community gradually shifted from scattered discussions and personal writeups into a hub-and-spokes structure, with Speedrun.com serving as the clearest public record for categories, rankings, guides, resources, forums, and streams. The game’s Speedrun.com page also points newcomers toward the community’s main gathering places, including an invite to Discord, which functions as the practical day-to-day workshop where runners compare routes, troubleshoot resets, and coordinate races.
That “public record plus live workshop” model shapes how moderation and verification work. Runs are typically submitted through the game’s “Submit run” flow on Speedrun.com, where the runner provides the required details and a video link, and then a volunteer moderator team reviews the submission against the board’s rules. Site-wide guidance emphasizes that video needs to be clear enough to verify, and it also sets expectations that moderation can take time because game moderators handle queues on a volunteer basis. The Chrono Trigger hub visibly lists its moderator roster as part of that structure, reinforcing that verification is community-run rather than automated.
Knowledge preservation in the Chrono Trigger scene tends to be layered. Speedrun.com hosts evergreen guides such as a master document covering categories and a community-maintained wiki link, while deeper “how-to” material often lives in long-form notes, shared documents, and tutorial videos that can be pinned, linked, and reused as teaching tools. When the community organizes events and races, the same pattern repeats: coordination and help channels run through Discord, races and restreams lean on Twitch, and archived material is often kept accessible through YouTube playlists and linked route documents.
On Speedrun.com, Chrono Trigger’s boards are split first by ruleset and version, then by category. The site currently hosts separate leaderboards for SNES, SNES Save Corruption, SNES Glitchless, PC (Glitchless), and NDS, with “miscellaneous” boards like Defeat Magus and Defeat Magus Glitchless kept off to the side for challenge style goals. This structure matters because Chrono Trigger’s different releases and rule philosophies do not always produce apples to apples runs, so the community isolates them into boards where verification expectations and allowed techniques stay consistent.
Within the main SNES Glitched family, the headline categories are Any%, Any% No LSS, 100%, New Game +, All Endings, and Low Level. Conceptually, these categories are all different answers to the same question: what does it mean to “finish” Chrono Trigger quickly? Any% is the pure race to defeat Lavos, while 100% pushes completion by requiring the optional quest line to be fully resolved before the final fight. A long running community definition of 100% is completing the optional side quests that Gaspar references so that he indicates the only remaining task is defeating Lavos. New Game + exists because the power curve collapses once you carry gear and levels forward, so timing norms and route logic diverge enough to merit a separate category.
Timing conventions for Chrono Trigger have historically been a little more specialized than “start the timer, stop the timer.” Speed Demos Archive documents a long standing approach where full game runs use the game’s timer as last seen, plus remaining real time, while New Game + runs use standard real time from first control. It also records a classic endpoint definition for full game completion: the end occurs on the appearance of the final damage number on Lavos. Even when modern boards display a single posted time, those legacy timing notes still help explain why the scene cares so much about consistent start and end points across versions, and why category splits exist when ports change presentation, content, or timing behavior.
Finally, Chrono Trigger’s leaderboards bake in a few “identity” decisions that shape what a legal run looks like. In SNES Glitched categories, the community tracks whether turbo was used, with runs explicitly labeled Turbo or No Turbo. And the presence of both Any% and Any% No LSS signals one of the most important rule lines in the game’s history: whether a specific high impact technique (referred to as LSS in category naming) is allowed or excluded, effectively defining two closely related but philosophically different Any% rule sets.
Chrono Trigger speedrunning matured first through “clean play” optimization, not spectacle. Early published routes emphasized controlling what the player could reliably control: configuration choices like Wait battle mode, faster battle gauge and message speeds, and a command setup that reduced menu friction, paired with practiced enemy avoidance and tight resource planning. Even in the pre-modern era of documentation, runners were already learning lines from one another’s videos and leaning on community-made stat and level charts to hit key damage thresholds without detours.
As routing knowledge consolidated, the biggest jumps came from techniques that turned the endgame into a routing problem rather than a pure execution grind. The most famous of these is Lavos Shell Skip (LSS), which exploits how the game sets position during a gate transition. In the tool-assisted documentation, the skip is explained as opening the menu in a narrow window to preserve “current” coordinates into the next map, letting the party appear in a position that triggers an immediate transition past Shell Lavos. That single concept rewired what “fastest Any%” meant, and it’s why the community eventually supported parallel identities such as Any% and Any% No LSS rather than forcing one route philosophy to erase the other.
Beyond LSS, the scene’s most extreme branch evolved around save-glitch and corruption mechanics: deliberately producing a partially saved file, then loading it to access impossible game states. TAS documentation breaks down how a mid-save reset can create corrupted SRAM data, how that can be reloaded from the file screen, and how item duplication becomes a lever for reaching memory addresses the player could not normally touch. This body of work did not just demonstrate “faster,” it clarified why certain techniques fundamentally change the game’s logic, which in turn encouraged clearer category boundaries and the eventual prominence of dedicated corruption-focused boards.
A related theme is how TAS research and emulator tooling helped speedrunning separate “what’s possible” from “what’s practical.” A TAS submission describing a baseline Any% notes that earlier breakthroughs using mid-frame reset “totally broke the game,” and then explicitly frames its own goal as showcasing tricks while banning memory corruption, with an on-screen overlay built via a Lua script. In other words, the tooling did more than chase theoretical speed; it helped the community understand which methods created a meaningful, runnable category and which ones effectively became their own discipline.
Finally, ports and version behavior pushed strategy forward in a different way: by changing the texture of time loss. In the community’s own discussion, PC/Steam glitchless play is described as faster largely because battle animations, zoning load times, battle speed behavior, and even text speed differ from the SNES experience, which forces route writers to treat “the same category” as a different optimization landscape. That reality is one reason the public hub organizes separate boards by platform and ruleset, and why a maintained “master document” and wiki-style references became central: the fastest way to improve is no longer rediscovering fundamentals, but keeping shared notes current as versions and best practices evolve.
One of the earliest “public memory” milestones for Chrono Trigger speedrunning was the shift from isolated personal attempts to runs that were treated as archival documents. Speed Demos Archive preserved full-game submissions alongside runner notes and strategy explanations, which effectively turned long RPG routing into something teachable and reviewable. That archive style mattered because it established shared expectations for what a complete run looked like, how goals were defined, and how the community talked about risk, consistency, and route logic long before modern hubs became the default.
A second watershed is when Chrono Trigger became a “marathon game” rather than only a leaderboard game. Games Done Quick showcases brought the run to a broader audience, which tends to reward categories that are explainable in real time, have satisfying narrative beats, and can be verified cleanly on stream. A good example is the game’s presence at Summer Games Done Quick with a long-form Glitchless 100% showcase, and later at Awesome Games Done Quick 2026 with a shorter, more focused category (Magus%) that still highlighted high-level planning and execution without needing to lean on “latest record” hype.
The most route-defining milestone type for this game is the moment a single endgame decision became important enough to split identities. The emergence of “LSS,” commonly explained as the Lavos Shell Skip, created two different philosophies of Any% that can coexist competitively: one route that uses a complex skip to bypass the Lavos Shell sequence, and another that commits to fighting it. Marathon programming even leaned into this as a spectator-friendly fork, framing runs as “fight or skip” choices, which reinforced the idea that the category split is not just technical but cultural. The split is reflected directly in the way Speedrun.com presents the game’s SNES glitched categories, where Any% and Any% No LSS are treated as distinct leaderboards.
Another milestone type is “TAS influence becoming real-world structure.” TASVideos publications demonstrated how far corrupted-save behavior and save-glitch mechanics could be pushed, including techniques that rely on intentionally broken save states to produce outcomes that would never appear in a normal playthrough. Once that ceiling exists in documented form, communities often respond by clarifying boundaries and, eventually, separating boards. Chrono Trigger’s public hub now reflects that evolution with a dedicated SNES Save Corruption board alongside more conventional rule sets.
Finally, there’s the quieter but equally important milestone of consolidation: the point where knowledge stops living primarily in scattered posts and starts living in maintained references. The Chrono Trigger hub’s guide section and linked community resources function as a “standard library” for the scene, helping new runners learn a route family and helping veterans preserve decisions as rules and tech shift. When that kind of documentation becomes normal, verification becomes easier, disputes become rarer, and progress becomes less about rediscovering basics and more about refining the edges.
Yu “inichi” Morimoto (Japan) – Full game (SDA “best time,” segmented) – 3:34 (h:mm) – April 5, 2007 – Platform/version: not specified on SDA listing – A foundational “archival benchmark” run preserved by Speed Demos Archive, often cited as an early high-visibility reference point for the game’s speedrun history
Ashewyn_L (United States) – Any% (SNES, glitched) – 2:25:08 – October 31, 2024 – JPN/NTSC SNES – A modern Any% benchmark on the main SNES leaderboard, documented as a world record run in the linked VOD title
Ashewyn_L (United States) – Any% No LSS (SNES, glitched) – 2:46:51 – March 18, 2024 – USA/NTSC SNES – A WR-marked No LSS run that highlights the community’s “route identity split” between faster glitch routes and a No-LSS ruleset
Kari “Essentia” Johnson – 100% (SDA definition) – 5:40 (h:mm) – April 3, 2012 – Platform/version: not specified on SDA listing – A major early reference for what SDA called “100%,” preserved as a single-segment endurance run and tied to a clearly stated completion standard on the SDA page
John De Sousa – New Game + (SDA listing) – 0:06:42 – August 6, 2010 – Platform/version: not specified on SDA listing – A classic example of how NG+ turns Chrono Trigger into a short optimization sprint, with SDA documenting both timing conventions and endpoint
Obdajr – 100% (marathon showcase) – 5:36:17 – January 11, 2014 – SNES – A watershed visibility moment: the run was scheduled at Awesome Games Done Quick 2014, with the VOD title preserving the showcased category and time while the GDQ tracker confirms the event placement and start time
puwexil – 100% (SNES Glitchless, no RNG manipulation) – 5:25:12 – May 26, 2019 – SNES (North American console; no turbo per VOD notes) – A representative “glitchless endurance” performance explicitly framed as no-RNG-manip in the run listing and dated in the linked VOD notes
PtownRocks – 100% Glitchless (WR-labeled VOD) – 4:19:47 – March 14, 2023 – Platform/version: not specified in the snippet – Captures a major improvement moment (the VOD is explicitly framed as a multi-minute WR improvement with the run date stated in the listing)
SquareSoft. Chrono Trigger (USA) Instruction Booklet. 1995. PDF. Internet Archive. Accessed February 10, 2026. https://ia600702.us.archive.org/27/items/SNESManuals/Chrono%20Trigger%20%28USA%29.pdf
Nintendo of America. Nintendo Player’s Guide: Chrono Trigger. 1995. Internet Archive. Accessed February 10, 2026. https://archive.org/details/Nintendo_Players_Guide_SNES_Chrono_Trigger_1995
Square Enix. “CHRONO TRIGGER – Patch #5 Update.” Steam News (CHRONO TRIGGER). Accessed February 10, 2026. https://store.steampowered.com/news/app/613830/view/4036870438631320264
Square Enix. “CHRONO TRIGGER – Patch #3 Update.” Steam Community Announcements (CHRONO TRIGGER). Accessed February 10, 2026. https://steamcommunity.com/games/613830/announcements/detail/1649887617599184974
SteamDB. “CHRONO TRIGGER 29/8/2023 Update Content.” SteamDB Patch Notes. Accessed February 10, 2026. https://steamdb.info/patchnotes/11890051/
Speedrun.com. “Chrono Trigger.” Accessed February 10, 2026. https://www.speedrun.com/ct
Speedrun.com. “Chrono Trigger: SNES Any% No LSS Leaderboard.” Accessed February 10, 2026. https://www.speedrun.com/ct?h=SNES_Any_No_LSS&x=7kld3qnd
Speedrun.com. “SNES Glitchless in 05:25:12 by puwexil.” Chrono Trigger run page. Accessed February 10, 2026. https://www.speedrun.com/ct/runs/y95owwvz
Speedrun.com. “SNES Any% No LSS in 02:38:40 by Ashewyn_L.” Chrono Trigger run page. Accessed February 10, 2026. https://www.speedrun.com/ct/runs/yw5j6voy
Speedrun.com. “SNES in 03:51:25 by inichi.” Chrono Trigger run page. Accessed February 10, 2026. https://www.speedrun.com/ct/runs/1zxon25z
Speedrun.com. “CT – Master document for all speedrun categories.” Guide by andyw3321. Accessed February 10, 2026. https://www.speedrun.com/ct/guides/ys8qm
Google Sheets. “CT – Master document for all speedrun categories (resource hub).” Accessed February 10, 2026. https://docs.google.com/spreadsheets/d/1xTYaT1Wh6ddjxr5cKqPYIaKjRf7P_bkt_93tJmmAZvI
Speedrun.com. “CT Speedrunning Wiki.” Guide by elgranjerry. Accessed February 10, 2026. https://www.speedrun.com/ct/guides/w9sri
Speedrun.com. “Any% No LSS new tutorial by elgranjerry.” Guide. Accessed February 10, 2026. https://www.speedrun.com/ct/guides/n2bpe
Speedrun.com. “100% Glitchless Notes + PC/Steam + Master CT Notes.” Forum thread. Accessed February 10, 2026. https://www.speedrun.com/ct/forums/dwfb7
Speed Demos Archive. “Chrono Trigger.” Accessed February 10, 2026. https://speeddemosarchive.com/ChronoTrigger.html
TASVideos. “Submission #2240: inichi’s SNES Chrono Trigger ‘glitched any%’ in 21:23.98.” Published submission page. Accessed February 10, 2026. https://tasvideos.org/2240S
Games Done Quick. “Run Detail: Chrono Trigger.” Summer Games Done Quick 2019 tracker page. Accessed February 10, 2026. https://tracker.gamesdonequick.com/tracker/run/3860
GDQ VODs. “Chrono Trigger.” Accessed February 10, 2026. https://gdqvods.com/game/chrono-trigger
RPG Limit Break. “Chrono Trigger (Glitchless 100%) by puwexil (RPG Limit Break 2018 Part 47).” YouTube video. Accessed February 10, 2026. https://www.youtube.com/watch?v=2RyyyKuwJMg