A fully functional automated video processing system that supports downloading videos from platforms such as YouTube, automatically generating subtitles, translating content, creating metadata, and scheduling uploads to Bilibili.
1.6k
Stars
238
Forks
0
Open issues
2
Contributors
AI Analysis
ytb2bili is an end-to-end video workflow automation system that downloads YouTube videos, generates and translates subtitles via AI, creates metadata, and publishes to Bilibili with scheduling support. It serves content creators and translators who need to repurpose YouTube content for Chinese audiences, combining Go backend infrastructure with a Next.js management console. This is purpose-built for the YouTube-to-Bilibili publishing niche, not a general-purpose video tool.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Go-based YouTube-to-Bilibili automation with AI subtitle translation and web management console
ytb2bili is a content automation system designed to bridge YouTube and Bilibili, targeting creators and agencies who need to repurpose video content across platforms. It automates downloading, transcription, AI translation, metadata generation, and scheduled uploads. Built with Go backend and Next.js frontend, it appears positioned for the Chinese creator economy. Adoption is not verified beyond GitHub visibility; real-world usage signals are absent from public documentation.
Created November 2025, ytb2bili emerged during a period of increased interest in cross-platform video workflows. Competes in a space already occupied by established tools like biliup (Rust, 5,258 stars) and bililive-go (Go, 5,623 stars). The project appears to target content creators frustrated with manual Bilibili upload workflows.
Project gained 1,598 stars in roughly 7 months (as of June 2026), averaging ~228 stars per month. Recent velocity is modest (5 stars in last 7 days as of June 26, 2026), suggesting either plateau or stabilization after initial attention. Growth pattern resembles a niche tool that found its audience but has not achieved viral adoption. No evidence of accelerating momentum.
Adoption not verified. README mentions community channels (QQ group, WeChat) and GitHub contact, suggesting user base exists, but no deployment count, user testimonials, company names, or production case studies provided. Presence of Docker and deployment documentation implies intent for production use, but actual deployments are not documented.
Likely a task-pipeline architecture: Go backend with REST API, Next.js frontend for console, LLM integrations for subtitle generation/translation, audio processing pipeline, and Bilibili API integration. README documents internal packages (LLM, tools, models) and external composition (Docker support) but does not detail microservice boundaries, concurrency model, or state management — inferring only from documented module layout.
Not documented in README. No CI/CD pipeline, test harness, or coverage targets mentioned. Makefile includes `make test` command but test scope/results not described.
Last push June 26, 2026 (11 days ago relative to current date July 6, 2026) indicates active maintenance. However, this is a single recent commit; frequency and scope of updates not quantifiable from metadata alone. Repository includes Docker support, multi-language README (English, Chinese, Japanese, Korean), and documented configuration — suggesting sustained care. Absence of recent issue closure data or release notes limits confidence in maintenance velocity.
ADOPT IF: you are a Bilibili creator or agency automating YouTube repurposing at scale, have moderate Go/Docker comfort, and need AI-translated subtitles and scheduled uploads without manual intervention. AVOID IF: you require proven production stability, extensive documentation of real-world deployments, or commercial support contracts. MONITOR IF: you are evaluating this against biliup or bililive-go and adoption evidence emerges (case studies, usage metrics, enterprise endorsements).
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
1/10
- Adoption not verified; community size unknown — deployment success stories absent from public record. Risk: undiscovered bugs or scaling issues may exist in production but not be surfaced.
- Maintenance velocity unclear; single recent commit does not establish release cadence. Risk: updates may slow or cease; long-term viability not guaranteed.
- Dependency on third-party LLM APIs (inferred from README mention of 'LLM integrations') — cost and latency not documented. Risk: surprise billing or API degradation could break workflows.
- No test coverage documented and no CI/CD pipeline mentioned. Risk: regressions may not be caught; pull requests may lack quality gates.
- Bilibili and YouTube API terms of service compliance not addressed in README. Risk: automation workflows could violate platform ToS or be blocked without notice.
ytb2bli will likely remain a niche tool serving Chinese creators and agencies who need YouTube-to-Bilibili workflows. Mainstream adoption outside this segment is improbable unless adoption accelerates and documentation matures. Project may stabilize as a community tool or be archived if maintainer loses interest. Growth rate suggests plateau rather than decline.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Go
- Last updated
- 2w ago
- Created
- 8mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
No open issues — clean slate.
Open pull requests
No open pull requests.
Similar repos
JimmyLv/BibiGPT-v1
BibiGPT is an AI-powered summarization tool designed specifically for video and...
bililive-go/bililive-go
Bililive-go is a specialized live-stream recording tool supporting 18+ Chinese...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
difyz9/ytb2bili
this
|
1.6k | +2 | Go | 7/10 | 2w ago |
 fqscfqj/Y2A-Auto
|
1.5k | — | Python | 7/10 | 1d ago |
 biliup/biliup
|
5.3k | — | Rust | 7/10 | 5d ago |
|
JimmyLv/BibiGPT-v1
|
6.1k | — | TypeScript | 7/10 | 2mo ago |
|
bililive-go/bililive-go
|
5.6k | — | Go | 7/10 | 2d ago |
 btjawa/BiliTools
|
5.3k | — | Rust | 8/10 | 3d ago |
Longer-established, higher GitHub visibility. ytb2bili appears to add AI-driven subtitle translation and web console; biliup may focus more narrowly on upload automation. ytb2bili's extra features come with higher complexity.
Also Go-based, higher adoption. Likely focused on live-streaming rather than VOD translation workflows. ytb2bili targets asynchronous content reprocessing; different use case despite same language.
Higher-star alternative. Appears focused on AI-driven insights from Bilibili content; ytb2bili is output-oriented (creation automation). Different problem domain.
Rust-based competitor with similar or higher adoption. Exact scope unclear, but ytb2bili's differentiator appears to be end-to-end YouTube-source automation plus AI translation.
