Open-source project
putyy/res-downloader avatar
putyy/res-downloader

res-downloader: a certificate, a proxy on port 8899, and a 4.0.0 beta line

Downloads common web resources including WeChat Channels, Mini Programs, Douyin, Kuaishou, Xiaohongshu, live streams, m3u8, Kugou, and QQ Music.

21,304 stars2,610 forksGoApache-2.0

At a glance

What is it?
A Go and Wails desktop app that captures network resources through a local system proxy and filters what it finds, aimed at Chinese video and audio platforms. It is useful precisely because it is generic, which is also why it wants a root certificate and can leave your system proxy pointing at a port that no longer exists.
Who is it for?
Use it if you work on Windows, macOS, or Linux and you want a friendlier list than a raw packet capture, especially for m3u8 streams and WeChat Channels. Skip it if you need a phone build, a stable release, or a tool that fetches large files on its own, because the docs send that job to other download managers.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
Mainly Go, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • putyy/res-downloader21,304 ★ · +1,343
Star history
Repository2026-09-212026-11-15
putyy/res-downloader20k21.3k

1,343 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The mechanism is a man in the middle, and the certificate is required

The README is honest about how the tool works: it captures network packets through a proxy and filters the resources it finds, comparing itself to Fiddler, Charles, and browser DevTools, and claiming the difference is friendlier filtering, display, and processing rather than a different technique. That has one hard consequence for installation. The first instruction is that you must allow the certificate file to be installed and allow network access, and if your installer refuses either, the app cannot see the traffic you want it to see. The app takes over the system proxy, and the value to check when nothing is captured is given exactly:

text
127.0.0.1
8899

Because the mechanism is a proxy rather than a site specific parser, anything your browser sends through it is visible, which is the upside for an unlisted site and the reason the certificate deserves a decision rather than a reflex.

Closing the app can leave the system proxy pointing at a dead port

The most concrete failure in the documentation is not about downloads at all. One FAQ entry is titled that after closing the software you cannot get online, and the answer is a single instruction: turn off the system proxy setting manually. The app is documented as taking the system proxy over and, on the way out, it does not guarantee it puts your settings back. That matters more than a failed download, because the effect is not a missing file but a machine with no network and a setting the user has to find in the operating system panel. The mitigation is procedural rather than technical: note whether your proxy was already enabled before you start, and treat the app as something to close by reverting that setting.

A Wails webview app, with no daemon and no command line

The go.mod and the repository layout explain the shape of the software. The module is built on Go 1.22.0 with a go1.23.2 toolchain, and the main dependency is `github.com/wailsapp/wails/v2` at v2.12.0, which means a desktop application that renders a webview over a Go backend. The tree matches that: `main.go` at the root, a `core/` package, a `frontend/` directory, a `wails.json` configuration, and a `build/` directory. The README documents only the desktop app; it describes no headless mode, server deployment or command line interface. The proxy layer is `github.com/elazarl/goproxy` at v1.7.2. A Wails app needs a desktop session, so this is a tool for one machine, not for a fleet.

The app finds resources, other tools fetch the big ones

Read the FAQ and the division of labour is explicit. For a slow download or a large file that fails, the recommended answer is a different program: Neat Download Manager or Motrix, both linked from the README. For live streams, the recommendation is to record with OBS. For m3u8 resources, the README points at two separate web tools, one for preview and one for download. So the built in fetch path is not the strong part of the product; identifying and presenting the resource is. The practical consequence is a two tool workflow, and a second consequence for automation: since the heavy lifting is delegated to external download managers that this project does not configure or call, there is no documented way to chain a capture straight into a resumable download without doing that wiring yourself.

WeChat Channels files are not finished until you press decrypt

One compatibility item has an extra step that is easy to miss. The platform list covers WeChat Channels, mini programs, Douyin, Kuaishou, Xiaohongshu, Kugou Music, and QQ Music, and video, audio, image, m3u8, and live stream resources, across Windows, macOS, and Linux. For WeChat Channels specifically, the FAQ states that after the resource is downloaded you click the 视频解密(视频号) action in the operations column. That makes the capture step and the finished file two different things for that platform, and a user who stops at the download will hold an undecrypted file. Nothing in the documentation describes what happens if that action is skipped, or whether the decrypt step is local, so treat that platform as a two step case rather than assuming every download is a ready file.

Version 4 is a beta line, and the maintainer warns about pace

The release history is three beta tags in about five weeks: 4.0.0-beta.5 on 2026-09-14, 4.0.0-beta.6 on 2026-10-04, and 4.0.0-beta.7 on 2026-10-21, with the last push to the master branch dated 2026-11-01. No stable 4.0.0 appears in that list. The README also carries a project status note in which the maintainer says personal commitments mean the time available for maintenance is limited, so replies to issues, pull request review, and release speed may be slower than before, while still inviting issues and pull requests, with a contributing guide to read first. Set that against what the software does on your machine: a beta that installs a certificate and rewrites your system proxy is a different risk than a beta that only reformats text, and a slower response is what you will have if a new platform changes its encryption.

Seven named platforms, no phone build, and a usage disclaimer

Scope is narrower than the mechanism suggests. Compatibility is stated for WeChat Channels, mini programs, Douyin, Kuaishou, Xiaohongshu, Kugou Music, and QQ Music, and the download addresses are the GitHub releases page plus a 蓝奏云 mirror whose password is given as 9vs5. There is no Android package and no iOS build anywhere in the documentation, so anyone looking for a phone or APK version finds nothing here. Two sibling builds are named rather than documented: a Mini edition that shows its interface in the default browser, and an old Electron version kept on a separate branch for Windows 7, with Windows 7 users told to install 2.3.0. The disclaimer at the end of the README says the software is for learning and research only, forbids commercial or illegal use, and disclaims liability, and the tool has no mechanism that checks whether a captured resource is yours to keep, which for the two music services on that list is a question the software leaves entirely to you.

Editorial conclusion

Use it if you work on Windows, macOS, or Linux and you want a friendlier list than a raw packet capture, especially for m3u8 streams and WeChat Channels. Skip it if you need a phone build, a stable release, or a tool that fetches large files on its own, because the docs send that job to other download managers. Before you install, read the disclaimer, which limits the software to learning and research and forbids commercial or illegal use, and note that you are trusting a certificate and a system proxy change to a project whose maintainer says response times will be slower.

Frequently asked questions

Is the downloader app safe to use?

The README requires that you allow the certificate file to be installed and allow network access during installation, and the app takes over the system proxy at 127.0.0.1 with port 8899. It also warns that after you close the software you may be unable to get online, and that you have to turn off the system proxy setting manually.

Is a video downloader legal?

The project states that the software is for learning and research purposes only, that use for any commercial or illegal purpose is forbidden, and that the author is not responsible for any legal liability. Nothing in the software checks whether a captured resource is yours to keep.

how to use res downloader

Five steps are given: allow the certificate file and network access at install, click 启动代理 at the top left of the home screen, choose the resource type you want with all types selected by default, open the resource page in an external app such as WeChat Channels or a mini program, then return to the home screen to see the resource list.

Do you have to pay for the downloader app?

The README states no price and points to the GitHub releases page and a 蓝奏云 mirror whose password is 9vs5, and the repository code is under the Apache-2.0 license. It does, however, run a community group and accepts a WeChat contact for joining when the group is full.

What is the safest video downloader?

The safety question here is the certificate and the proxy, not the download. This app needs you to allow a certificate file and network access at install, and it sets the system proxy to 127.0.0.1 port 8899, which you may have to clear by hand after closing it, so judge the certificate and the source of the binary rather than the file format.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. putyy/res-downloader on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/putyy-res-downloader.svg)](https://hysenlabs.com/projects/putyy-res-downloader)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/putyy-res-downloader.svg)](https://hysenlabs.com/projects/putyy-res-downloader)

Was this useful?