Built for a media library, not a downloads folder
Bilibili Video Downloader does much more than save one stream. It searches normal videos, multi-part collections, series, films, courses, creator spaces, favorites, history, watch-later lists, and followed shows. Users can select AVC, HEVC, or AV1 video at qualities reaching the account's available 8K, Dolby Vision, HDR, 4K, and enhanced variants, plus lossless, Dolby Atmos, and standard audio tiers.
The differentiator is everything around the media. Naming templates can use identifiers, titles, parts, publication time, and uploader information. The app downloads original covers, converts CC subtitles to SRT, preserves raw danmaku as XML or JSON, and can render danmaku into styled ASS subtitles. NFO, poster, and fanart generation target Emby-style libraries. Chapters can be embedded, and sponsor segments can become markers that compatible players skip.
A Tauri 2 GUI manages queues, pause, resume, restart, removal, batching, bandwidth limits, and segmented downloads. For someone maintaining a personal Chinese media archive, this is a much friendlier workflow than remembering a long command line and separately writing metadata scripts.
Language and account assumptions are substantial
The README, release notes, issue templates, and interface examples are in Simplified Chinese. There is no linked English documentation. Machine translation can explain a feature table, but login cookies, antivirus warnings, naming placeholders, task recovery, and third-party plugin risks deserve precise understanding. English-only users should choose a tool with documentation they can audit.
Bilibili account state controls accessible media. Cookie or QR login unlocks account areas and qualities the account is permitted to view. That does not grant ownership or redistribution rights. The repository says the program is for learning, research, and communication and places legal responsibility on the user. Download only material you are authorized to keep, follow applicable law and service terms, and do not use the application to bypass payment or access controls.
Credentials also need respect. A Bilibili session cookie can expose account activity and paid access. Store it only in the official application, avoid screenshots and logs containing it, and revoke the session if the machine or configuration is shared. A public issue includes the shape of SESSDATA values but correctly uses a generic example rather than publishing a usable credential.
Installation is easy, verification is manual
Release v0.2.1 provides precompiled packages. The release text distinguishes a portable archive that can run without installation, but the README warns that antivirus products may flag unsigned personal-project binaries. The maintainer recommends downloading only from the GitHub Releases page or building from source. A promise of safety is not cryptographic verification, so cautious users should inspect the repository, reproduce the build where practical, and scan artifacts independently.
The “portable” package is not fully self-contained in user-data behavior. Issue 20 says configuration and logs still live under AppData rather than beside the executable, making it installation-free but not truly portable between machines. Windows 7 is unsupported. macOS users may need to handle normal unsigned-app opening restrictions described in project discussions.
Current failures cluster around optional processing
Issue 85 reports a useful edge case: Bilibili sometimes returns view_points: null, while the application expects an array. With chapter marking enabled, parsing fails after video and audio downloads complete, chapter metadata creation fails, and the entire task is marked failed. Null should reasonably mean no chapters, but v0.2.1 reportedly does not handle that response.
Issue 76 shows another chapter-path dependency. Fetching sponsor segments from bsbsb.top timed out after one retry, causing automatic merge and chapter embedding to fail for three series episodes. An optional external enrichment service should not prevent the base video and audio from merging. Users prioritizing reliable archives should disable ad and chapter marking until failure is downgraded to a warning. Issue 72 similarly says turning off chapter and subtitle options was necessary to complete downloads in v0.2.0.
Platform coupling will always require maintenance
Issue 87 says v0.2.1 accepts a valid annual-member SESSDATA and reports login success, yet premium series return only preview quality. The reporter traced this to commas in the cookie value not being URL-encoded for particular playback endpoints. Replacing commas with %2c reportedly restores the full stream list. This is a concrete interoperability bug, not evidence that the account lacks access.
Issue 86 reports intermittent HTTP 412 responses when repeatedly searching a creator space. The returned Bilibili error page resembles anti-automation handling. Retries may succeed, but aggressive retrying can worsen rate limiting. A desktop downloader that uses unofficial platform endpoints must adapt continuously to signing rules, cookies, response schemas, regional policy, and bot defenses. No maintainer can guarantee permanent operation.
Large queues have a separate local cost. Issue 61 reproduces UI lag with about 5,000 stored tasks even when only one remains active. Each progress event walks and assigns into every Vue-tracked progress object, creating reactive work proportional to the full history. Archive or clear completed tasks before the queue reaches that scale.
Health is good for a young specialist tool
Version 0.2.1 shipped August 1, 2026, fixing QR login, and the repository was pushed again on August 11. Its 12 open issues and pull requests include detailed request traces, source locations, reproducible settings, and suggested fixes. At 1,840 stars, the community is modest but engaged. The recent release and issue activity together show active maintenance.
The experimental plugin system should be avoided by most users. It loads in-process dynamic libraries with no security restrictions. The README explicitly recommends source review and self-compilation and says never to trust third-party DLL, SO, or dylib files. A plugin has the same access as the application, including account state and the filesystem.
For a Chinese-speaking Emby user, this application offers a rare amount of purpose-built polish. Start with plain video, audio, cover, and subtitle downloads, verify output, then enable chapter and sponsor enrichment one feature at a time. For automated cross-site downloads or long-term scripting, yt-dlp has the broader maintenance base. This project's GUI and Bilibili metadata depth are why to choose it, while platform fragility is the cost.