Twitch recently announced a 100-hour storage limit for Highlights and will be deleting anything outside the limit on April 19th, 2025.  This is, of course, alarming as many speedrun submissions make use of Twitch highlights.

# Downloading Runs At Risk

Before I dive into the rest of the article, I would like to spotlight a community effort to mitigate the damage caused by Twitch’s actions here. A sincere thank you to @Matse007 and the team behind the Speedrun Rescue Script which detects runs submitted (either from a specific individual or for a whole game) with Twitch Highlights and downloads them for you. With your footage safely preserved, you can re-upload your runs to another platform and update your submissions as needed. At the very least, this script ensures that the valuable content you’ve worked hard to capture remains accessible to you.

[You can get it from the Github page here, alongside the installation instructions.](https://github.com/Matse007/SpeedrunRescueScript)

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXf7VPdIDDg0u-BzbdpG9VcE_xenHcsOBwisYIn85awtk48SvMZAHQwOs9kcv8kmRXeVtt0UGdblLG1eGIC6t0TfAQ5soJtcU1nmZMSTUIV_2Wty1qTASnvLxZEbE2-NB51eh5bq?key=uq53moH6c6uD_CQPJZjukOHE)

The Speedrun Rescue Script requires installing Python and some other dependencies, so it might not be the most beginner-friendly - but if you’re comfortable with a more technical setup, it’s the best option for backing up all of your runs that are potentially at risk.

If you’re not comfortable with the more technical approach, [Clipr.xyz](https://clipr.xyz/) offers a web-based option for downloading individual VODs. This tool works in a pinch if you only need to save a handful of VODs.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXeD8I35HWNZaxXjneeptn7oDVP2ZBwyvtB6pJJ-DuxAxgpcEA_hSr86KBZl1GiIxt_N4MT7Eau4TmKN2uin1MNjmim5U0GhhxACWm74kzCsB04euDuK_AttSoxFeFh4AT_R8W2E?key=uq53moH6c6uD_CQPJZjukOHE)

You can also export VODs directly to YouTube right from within the Twitch Video Producer, although it’s worth noting it’s only one at a time and quite slow.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXfL1ycfd-_mBPJ_aybnbGqdBB59S7lFf6jNQ_ASz1Jqhgrsz-3PkzTEqC_72E-ClF9XmTkRDrsuf-UQnBHHEiHhDhmn6k0uFeO_cfhfK113GfAKNtcPUHiseY-uN4eRwqu2fuTFrg?key=uq53moH6c6uD_CQPJZjukOHE)

If you have any other suggestions or know of alternative tools, please share them in the comments - I’ll review them all and potentially add them to the article.

# Highlight Lock

Adding to the urgency, Twitch is preventing users from creating new Highlights until their stored content is below the 100-hour limit - meaning many runners with **hundreds or even thousands of hours of archived footage** are currently unable to save their runs. **For many, sorting through that amount of content is completely unreasonable.**

# A Troubling Pattern - Long-Term Solutions

With the short-term stuff out of the way - let’s talk long-term. Those of you who have been around for a few years may remember similar previous events with YouTube’s unlisted videos and with older Imgur content (frequently used for guides). This is a disturbing pattern that is repeatedly threatening the history of our community.

While we don’t have immediate answers, I wanted to let you know that we are *very* well aware of the situation at hand and are **actively discussing long-term solutions to protect speedrunning history** from similar issues in the future. If you have ideas you would like us to consider, by all means, feel free to drop them in the comments for me to review.

# A message to Runners and Moderators 

We understand that many runners will be re-submitting potentially dozens of runs in the near future. Please be patient with your moderators, as they will be handling a significant influx of submissions while also balancing the rest of their responsibilities outside of speedrunning.

Moderators, once things have settled, we kindly ask that you refrain from deleting any run submissions that were previously verified with video proof, even if the footage was later removed by Twitch.

# Conclusion

This situation is frustrating as hell - but it’s also a reminder of how resilient and resourceful the speedrunning community is. While Twitch’s changes put years of history at risk, efforts like the Speedrun Rescue Script show that we’re not powerless. In the short term, take action to back up your runs, and in the long term, let’s work together to find solutions that protect our community’s archives.

Please be sure to thank the team behind Speedrun Rescue Script personally or in the comments.

We’ll keep you updated as we explore better ways to safeguard speedrun history. In the meantime, **if you have any other tools, insights, or ideas, drop them in the comments** - we're all in this together :)

### *Cam // Meta - Speedrun.com Community Manager*

Let's talk about Twitch and their 100 Hour Limit.

Twitch Highlight Limit & Speedruns At Risk

In my last article, we covered **Twitch’s new 100-hour storage limit for Highlights**, which threatens thousands of existing speedruns. Since **all runs submitted with Twitch links are at risk**, we knew a solution was needed - not just for this situation, but to **build a system that allows us to respond faster to similar issues in the future**.

Today, we’re rolling out **new tools** to help runners and moderators **identify and manage runs at risk** more efficiently.

## ![](/static/blob/7n63q24n.png)

# **Identifying Runs at Risk**

To make it easier to track affected runs, runners can now see all of their at-risk submissions in the Pending Tab on their profile

![](/static/blob/1n7j9m7n.png)

..and moderators have access to the same information within the Mod Hub alongside all the other previously available filters. 

**For most cases, the view you will want is "Verified" runs that are also "At risk" as seen in the image below.**

![](/static/blob/1n5364qz.png)

Additionally, **at-risk runs will now be marked with a yellow identifier on their Video Proof Icons** for quick visibility.

# **Managing Runs at Risk: The Video State Variable**

![](/static/blob/rnq2352n.png)

To give users control over their runs, we’ve introduced a **“Video State” global variable**. This variable will only be visible on runs considered at-risk. If a run is flagged as at-risk, its Video State will default to **“⚠️ Video at Risk”**, and runners or moderators can update its status based on the situation:

✅ **Mark as Safe** - Use this if the video proof within the run submission has been updated to a link that won’t be removed in the upcoming Twitch deletion on April 19th, 2025 (e.g., reuploaded to YouTube) or if the Twitch VOD is included in the 100-hour storage limit on the runner’s channel.

🔴 **Mark as Abandoned** - Use this if the video proof **cannot be updated** and the existing video link has been or will be removed. **This does not impact the run itself** - it simply acknowledges that the run once had valid proof and remains a viable leaderboard submission.

# **Who Can Update Video States?**

- **Runners** can update video states on runs they were a player in (this includes co-op runs)
- **Submitters** can update video states on runs they submitted (whether they are the player or not)
- **Moderators** can update video states on games they moderate

# **A Note to Moderators**

While SRC has no control over where videos are re-uploaded or by who, we ask that moderators allow **runners some time to update the video proof on their own submissions first**. This helps prevent run content from being reuploaded to channels not owned by the runner.

However, **we support moderators downloading and backing up** run video proof as long as they **wait to update submissions**, giving runners time to handle updating their own submissions first.

# **Related Changes & Improvements**

As part of this update, we’ve made a few other related improvements

- **Added Embed Support** - Runs with video links from **TikTok, RUTUBE, and YouTube Live** will now have the video proof embedded properly
- **“View Run” → “Triage Run”** - The terminology has been updated to better reflect the new workflow, and is now distinct from Edit Run

![](/static/blob/7z38544n.png)

- **The “Pending” Tab** - The Pending tab on runner profiles now counts runs at risk, making them easier to track

![](/static/blob/qnygmk4n.png)

# **Backing Up Your Runs: How to Download At-Risk Videos**

Let’s quickly recap how to backup your runs if you aren’t already familiar. If you haven't backed up your runs yet, now is the time to do so.

Here are the best ways to download your runs:

### **Speedrun Rescue Script - Advanced Setup**

![](/static/blob/dz4wx9me.png)

Developed by @Matse007 and some other amazing contributors from within the speedrunning community, this script automatically detects and downloads your runs that were submitted with Twitch Highlights.

- Detects at-risk runs either per runner or per leaderboard/game
- Best for runners and moderators who need to bulk download all at-risk runs per runner or per leaderboard/game
- Lots of new customization options (see Github page)
- Requirements: Python + dependencies (installation instructions on the page)
- Get it here: [https://github.com/Matse007/SpeedrunRescueScript](https://github.com/Matse007/SpeedrunRescueScript)

Matse has also gone ahead and created a handy YouTube tutorial for S.R.S.!

https://www.youtube.com/watch?v=tkgnHt2aVmQ

### **TwitchDownloader - Easy Setup (Still Somewhat Technical)**

TwitchDownloader allows you to bulk download your VODs and Highlights from a Twitch channel.

![](/static/blob/1n83vr9z.png)

**How to Use:**

Best for bulk downloading VODs and Highlights from a single Twitch channel.

    1. Install TwitchDownloader (GUI is recommended over CLI)
    2. Open the Task Queue tab and hit Search VODs
    3. Enter your Twitch channel name to generate a list of all VODs/Highlights
    4. Select all relevant runs (or select all) and add them to the queue for downloading

- Get it here: [https://github.com/lay295/TwitchDownloader/releases](https://github.com/lay295/TwitchDownloader/releases)
- Installation Instructions: [https://github.com/lay295/TwitchDownloader/ReadMe](https://github.com/lay295/TwitchDownloader?tab=readme-ov-file#readme) (Go down to any of Windows/MacOS/Linux “Getting Started” sections)

This is probably the easiest “set it and forget it” solution, but will still require some basic Github knowledge to download/install.

## **What’s Next?**

While these changes currently apply only to existing at-risk runs, these features lay the groundwork for responding more effectively to similar issues in the future.

We're actively monitoring the impact of these changes and are prepared to make additional adjustments as necessary. If you have any feedback, suggestions, or run into issues using the new tools, let us know! This is a community-wide effort, and we’re committed to making the process as smooth as possible.

**- Cam // Meta, Speedrun.com Community Manager**

Twitch Runs At Risk are now visible and easier to manage!