Axortex

The culture of tech, food & beauty

← Tech
✦Tech

LoL Replay Download Limit: Riot's Lockdown U-Turn to 10 per Hour. Full Timeline

Riot's Patch 26.20 tried to lock LoL replays to your own games. After coach and creator backlash it shipped a 10-downloads-per-hour cap in 26.21. Dated timeline, both sides, who it hits.

A Axortex ·

TL;DR: On 6 October 2026 Riot's Patch 26.20 notes said League of Legends players would only be able to download replays of games they played in, and that third-party apps and sites would lose replay downloads entirely. Coaches, analysts, pros and creators pushed back within hours. A day later Riot delayed the change to Patch 26.21. On 20 October it dropped the lockdown: everyone can still download anyone's replays, but only 10 per hour. The cap takes effect "during" Patch 26.21, which went live on 21 October. Within a day, at least one replay service, Replayit, said it was "degraded" and offered subscribers refunds.

Last updated: 22 October 2026, 08:00 KST.

What happened

League's replay system has worked the same way for years. Open anyone's match history in the client, download the .rofl file, and watch the game from any camera angle. Coaches used it to review students, analysts used it to scout solo queue, and whole YouTube channels were built on Challenger and pro solo queue replays.

Patch 26.20, the Worlds 2026 patch, was set to end that. The notes, published 6 October (US time), said:

"Starting with this patch, you will only be able to access replays from matches you played in. Other players will no longer be able to download your replays, and third-party apps & sites will lose access to replay downloads entirely."

Riot framed it as security. It said vulnerabilities around League game data had been exploited by cheat developers and other bad actors. The same day it began blocking unknown third-party apps from reading game memory across League, TFT and VALORANT, and gave approved tools until April 2027 to move to official APIs. (We covered the memory block in our AI decompilation timeline.)

The replay change is what drew the backlash. By 7 October Riot had delayed it. On 20 October it replaced it with a rate limit.

Timeline

Date (UTC / KST) Event Source
6 Oct 18:00 UTC / 7 Oct 03:00 KST Patch 26.20 notes published: replays limited to games you played in, third-party replay downloads cut "entirely" Riot patch notes (as quoted by Strafe, esportnow.gg)
6 Oct, evening UTC Jankos: "What...? No reason to remove that feature." Creator NEACE tags Riot Phroxzon and Drew Levin, calling it "a ridiculous change." Vandiril shares a LoL Dobby YouTube post on it X, via Dot Esports / esportnow.gg
6 Oct 22:15 UTC / 7 Oct 07:15 KST Challenger coach Strompest (ex-FlyQuest) posts a workaround (rename a student's .rofl file to match one of your own) and calls the change "a huge blow to the content creation ecosystem" X
7 Oct (US) Patch 26.20 goes live LoL Wiki, Strafe
7 Oct 09:25 UTC / 18:25 KST Necrit: the issue seems to be people "vibecoding scripts that scrape the data off of 1000s of public replays" to train bots X
7 Oct 16:48 UTC / 8 Oct 01:48 KST @LeagueOfLegends: the change is "being delayed to patch 26.21" while Riot works on a solution so creators and coaches "are not meaningfully impacted" X (about 12,000 likes)
20 Oct 18:00 UTC / 21 Oct 03:00 KST Patch 26.21 notes: "replay downloads will be limited to 10 per hour," including your own, friends' and other players' replays Riot patch notes
20 Oct 18:34 UTC / 21 Oct 03:34 KST @LoLDev posts "An update on replays"; Drew Levin reposts it X
21 Oct (US) Patch 26.21 goes live Riot, LoL Wiki
21 Oct 15:56 UTC / 22 Oct 00:56 KST Replayit: "Riot's replay limit is now live, and Replayit is currently degraded." New subscriptions paused, refunds offered X (@ReplayitGG)
Timeline graphic of the League of Legends replay controversy: 6 Oct Patch 26.20 notes restrict replays to own games and creators push back; 7 Oct Necrit points to scraping bots and Riot delays the change to 26.21; 20 Oct the 26.21 notes and LoLDev announce a 10-per-hour download cap; 21 Oct patch goes live and Replayit reports degraded service

Riot's stated reasons vs. critics' claims

What Riot said, in order:

  • 6 Oct (26.20 notes): a security move. Vulnerabilities around League data had been exploited by cheat developers and other bad actors to build unauthorized tools. The separate Riot Support article on the memory block said AI-assisted reverse engineering had made such tools easier to build.
  • 7 Oct (delay): "We are working on a solution to ensure the creators and coaches out there that rely on replays are not meaningfully impacted by this change and want to have that in place before this goes live."
  • 20 Oct (26.21 notes): "This change is necessary to prevent large-scale abuse of downloaded replays by bad actors using vibecoded apps to scrape thousands upon thousands of replays. We opted for a time-based limit to still allow creators to make content, while preventing mass exploitative downloads. We'll continue to monitor how many replays are downloaded to ensure players have access to this important feature while preventing clear misuse."

The reason narrowed over two weeks. On 6 October Riot cited general security and cheat tooling. By 20 October the target it named was specifically mass scraping.

What critics said:

  • The original plan hit the wrong people. Jankos listed three uses that would die: learning from top-ranked players' replays, analysts scouting jungle pathing and timers, and coaches improving students' play. A Reddit comment quoted by Strafe called it "a huge blow to educational League content."
  • It was buried. Strafe noted criticism that a change this big showed up inside the patch notes with no separate announcement. esportnow.gg also pointed out that it landed on the Worlds patch, which Riot usually keeps quiet outside balance changes.
  • Fix the bots, not the feature. Even after the reversal, some players weren't satisfied. One widely seen quote-post (about 50,000 views) of @LoLDev's update said bots add players after matches, then download their whole match history, and asked why Riot didn't use "bot detection" instead of "a hard rate limit."
  • Sarcasm about the cap. Another post thanked Riot for "generously" granting "the right to watch 10 per hour." Riot's notes describe a download limit, not a viewing limit. Replays you have already downloaded aren't capped.

On the other side, coaching community Coludi called the cap "a much more reasonable way to prevent abuse without hurting coaching." Sheep Esports wrote that the reception was "the complete opposite" of the first announcement.

Who is affected

Matrix chart comparing impact by group under the original Patch 26.20 plan versus the final 26.21 cap: regular players go from none to low; players watching friends or high-elo games, coaches, analysts, creators and third-party tools go from blocked or high impact under the original plan to low, medium or high under the cap; bulk scrapers go from blocked to high
  • Regular players. You could always download your own games, and that hasn't changed. The cap only matters if you download more than 10 replays in an hour, which few people do.
  • Players studying friends or high-elo games. Under the original plan this was gone. Now it's back, at up to 10 downloads an hour.
  • Coaches. A 1-on-1 coach reviewing a student's last few games is under the cap. Strompest's file-rename workaround is no longer needed for that.
  • Analysts and scouts. This group may notice the cap. Scouting a prospect or an opposing team's solo queue habits can mean pulling dozens of games in one sitting. At 10 an hour, 40 games takes four hourly batches, so more than three hours of waiting, or several staff accounts working in parallel. Riot hasn't said whether the cap is per account.
  • Creators. Riot says the time-based design is meant to "still allow creators to make content." A channel making one deep-dive video is fine. Channels that upload Challenger and pro solo queue games in bulk, which Reddit users named in the 26.20 backlash, now run into a ceiling.
  • Third-party replay sites and tools. These are hit hardest, apart from scrapers. The 26.20 plan cut them off completely. The cap leaves a narrow opening, but any service that fetched replays for many users through its own accounts is throttled. Replayit, a service that automatically saves LoL, TFT and CS2 highlights, said on 21 October it was "degraded" and paused new subscriptions. One of its users asked whether the service could use each user's own linked Riot account, and its own 10-per-hour allowance, instead.
  • Bulk scrapers. This is the stated target. "Thousands upon thousands" of replays at 10 an hour on one account is a long job.

What the 10/hour limit means in practice

Illustrative scenario Downloads needed At 10/hour (one account)
Review your own session 3–5 Under the cap
Coach reviews a student's week ~10–20 1–2 batches (up to ~1 hour wait)
Analyst scouts 4 opposing players, 10 games each 40 4 batches (3+ hours)
Hard ceiling, downloading nonstop 240/day 24 hours
Scraper targeting 20,000 replays 20,000 ~2,000 hours (~83 days)

The math is simple: 10 an hour is at most 240 a day per limit bucket. That's plenty for any human workflow and far too slow for a single-account scraper. The real questions are things Riot hasn't published:

  • Rolling or fixed window? Not specified.
  • Per account, per IP or per device? Not specified. If it's per account, a scraper with 50 accounts gets 500 an hour. That's the hole the critic of "a hard rate limit" was pointing at.
  • Do your own replays count? The notes say "replay downloads will be limited to 10 per hour" with no exception for your own games, so assume they count.
  • When exactly does it start? "During Patch 26.21." Replayit's post suggests it was enforced by 21 October, but Riot hasn't confirmed a time.

Replays also only play on the patch they were recorded on, so a creator can't build up a backlog across patches. The cap applies to each two-week patch cycle.

What to watch next

  1. Whether Riot changes the number. Riot says it will "continue to monitor how many replays are downloaded." That could mean raising the cap, lowering it, or adding exceptions.
  2. A creator or coach program. In early October, esports.gg suggested vetted access for League Partner Program creators and registered coaches. Riot hasn't announced anything like it. If analysts at pro teams start complaining during scouting season, watch for one.
  3. Third-party tools moving to official APIs. Replayit is the first public casualty. Watch whether replay sites rebuild around users' own accounts, and how the April 2027 memory-access deadline lands alongside this.
  4. Whether bots adapt. If scrapers just spread across more accounts, Riot may need the "bot detection" approach critics asked for, or a tighter cap that real users will feel.

One caution: the 26.20 replay wording has been removed from Riot's live 26.20 patch notes page, so the quote above relies on Strafe's and esportnow.gg's same-day copies.

Sources

#league-of-legends#riot-games#replays#patch-26-21#coaching#content-creators#esports-controversy
← Back to all posts