Repository navigation
YouTube channel
github-actions[bot] edited this page Nov 21, 2026
·
3 revisions
What we learned bringing up a new channel (October 2026): it is held back in ways the API reports badly, so do these before the first big upload run.
-
Sign in (YouTube sign-in):
clippa upload --sign-inonce, on the machine that uploads. The token lands insecrets/youtube_token.json. First set the Google Cloud project's OAuth app to In production (Google Auth Platform > Audience > Publish app; no verification needed, you click past the "unverified app" warning): while it is in Testing, Google expires the sign-in after 7 days and uploads stop withinvalid_grant. Signing in again keeps the analytics scope, andclippa doctor(online) tests the sign-in by refreshing it. -
Verify the channel at https://www.youtube.com/verify (phone). Without it custom
thumbnails are refused (403); videos still go up, and
clippa upload --thumbnailssets the covers afterwards. Verification can take more than one round: if Studio later refuses an upload, it may offer another verification link. Follow it. On our channel that second verification lifted the cap for Studio and the API: uploads went through again right away. -
Expect a small daily upload cap.
uploadLimitExceeded("The user has exceeded the number of videos they may upload") is YouTube's limit on the channel, not the API quota (that one isquotaExceeded). Private uploads count too. The window looks rolling (about 24 h from each upload), and the API hit it at 8 uploads in 24 h on the new channel. It grows with the channel's history and verification; YouTube doesn't publish the number. Keep[schedule] max_per_day,[youtube] max_per_runandmax_per_24hunder it (max_per_24hcounts every upload in the last 24 h, so hourly automatic runs stay under too). A refused upload leaves nothing behind on YouTube or in schedule.json, so it is safe to rerun later. -
Past the cap, upload in Studio (it may still accept uploads when the API is
refused):
clippa upload --next 5lists what goes out next with each file; drag the file into Studio, set it Private, skip the details, thenclippa upload --attach <item> <link>sets the title, description and tags, adds the thumbnail, captions, playlist and Kitsu link, and records the video as uploaded so Clippa never sends it twice. -
Publishing through the API (
videos.updateto public) worked on our Cloud project before any API audit, so[youtube] manual_publishcan be turned off once you trust the uploads. Before that, check the first private uploads for Content ID claims in Studio. The Data API can't see claims; it only shows region blocks. -
Playlists are created on first use and their ids cached in
secrets/youtube_playlists.json. If you delete one in Studio, the next add finds it gone, looks the name up again and makes a new one if needed. A playlist renamed in Studio keeps its id, so videos keep going into it. Playlist names come from each item's Kitsu "Playlist" column. -
Source links (
[youtube] source_links, on by default) add a line such as "Full segment: " to a clip's or segment's description once its longer video is public. They are not in Kitsu. Each upload run edits at mostlink_updates_per_run(20) descriptions of videos already up (about 51 quota units each).clippa upload --links --dry-runshows what it would change. Change the wording per show withclip_source/segment_sourcein[shows.<key>.youtube]. -
API quota. A Cloud project gets 10,000 Data API units a day, reset at midnight
Pacific; uploads themselves have their own bucket (100 a day), but each upload's
thumbnail (50), captions (400) and playlist adds (50 each) come out of the 10,000.
Every call is counted in
logs/youtube_quota.jsonand each upload run ends with the day's total. Source-link updates and caption retries (a captions upload that failed is tried again hourly, 3 times;clippa upload --captionsalone) only spend what's left afterupload_units(600) for each uploadmax_per_24hstill allows that day. If Google raises your project's quota, set[youtube] daily_quotato match.
Home · Getting started · clippa doctor · These pages are built from docs/wiki/ in the repo, so edits made here are overwritten: how to edit them
Run it
- Overview
- Getting started
- Roles and services
- Configuration
- Pipeline
- Review
- Reviewing
- War room
- Clippa messenger
- Scheduling and uploads
- Costs
- Checkup
- Audit
- Backups
Install
- Install
- Install checklist
- Kitsu
- Discord app
- YouTube sign-in
- Windows
- macOS
- Transcribe on Modal
- NAS recorder
- NAS hub
- Claude on the NAS
- Phone access
- Model providers
- Adding a show
- YouTube channel
Features
- Pre-shows
- Fetching VODs
- Speakers
- Faces
- Covers
- Cast library
- B-roll
- Clip art
- Weekly issue
- X posts
- TikTok
- News watcher
- Character pieces
- Documentaries
Research
Working on Clippa