Email is hidden behind a button and ReCaptcha
To see a business email, you need to open the channel, click the contact button and pass Google ReCaptcha. At list scale, this becomes repetitive manual work.
YouTube-ReCaptcha
Email Parser for ZennoPoster that collects YouTube channel emails from the button protected by Google ReCaptcha.
The template processes channel lists, solves ReCaptcha through CapMonsterCloud, authorizes with NetScape cookies, replaces accounts on the daily limit and saves found contacts with channel metadata into a readable XLSX spreadsheet.
- 5/day
- YouTube limit per accountafter the limit, the template reports the status and switches to the next working session
- 20
- threadsmulti-threaded processing for channel lists when the cookie and proxy pool is sufficient
- <3 sec
- cookie loginfast hot replacement through an active NetScape YouTube session
- 2-10 sec
- ReCaptchathe current branch solves Google ReCaptcha through CapMonsterCloud
011_Channels_Urls.txt
02Cookies\1_Ready
03CapMonsterCloud
04Results\[Channel emails].xlsx
5 emails / account / daythen the thread takes the next active session
Channel report10 columns
ChannelStatusEmailData
@creator-labemail foundbusiness@example.comcookies ok
@market-review5/day limitcookie swaphot swap
@media-stackno buttonnot foundmetadata saved
Statuses are separatedcookiesStatus, emailStatus, parseStatus
What it solves
YouTube limits both ReCaptcha and accounts
On YouTube, channel email is hidden behind the business contact button, ReCaptcha and a daily limit of around 5 reveals per account. YouTube-ReCaptcha turns this into a managed multi-threaded process.
Each account has a daily limit
YouTube opens only a limited number of emails from one account per day. After the limit, other channels no longer reveal emails until the account is replaced.
Account replacement must be fast
Manual login into every account slows collection down. The template uses ready cookies with active sessions and switches accounts without a long login flow.
The output must be a spreadsheet
Contacts, statuses and channel metadata are saved to XLSX so the list can be filtered, sorted and handed off for further work.
Features
Everything needed for bulk YouTube email collection
The capability set is based on the current ProjectMaker project, input_settings.xml, documentation and the product brief.
Button email parsing
- reveals business email on the channel page
- solves Google ReCaptcha through CapMonsterCloud
- saves email found in the channel description
Accounts and cookies
- NetScape cookie authorization
- validity and active YouTube session checks
- normalization of incomplete cookie sets from different sources
Hot replacement on limits
- tracks the daily email reveal limit
- switches to a new account after the limit
- reuses working cookies without manual login
Bulk processing
- multi-threaded runs up to 20 threads
- channel links by ID or @username
- temporary problem channels can return to the queue
Proxies and IP rotation
- IPv4 HTTP and SOCKS5 proxies
- URL-based IP rotation after a thread
- separate statuses for proxy errors and YouTube limits
Reports and channel data
- channel metadata in the final table
- local LiteDB before XLSX export
- separate cookie, email and parsing statuses
Speed
Throughput depends on cookies, ReCaptcha, proxies and limits
The landing page shows practical reference values instead of promising the same speed on every infrastructure.
cookie check
checks a cookie file for validity and an active YouTube session
channel check
checks the channel, contact button and base metadata before email reveal
ReCaptcha
expected speed for solving one Google ReCaptcha in the current template branch
threads
practical throughput depends on cookies, proxies, IPs and YouTube limits
Workflow
From channel list to XLSX report
The product value is in the repeatable flow: prepare channels and cookies, pass ReCaptcha, replace the account on limit and save the result.
01
Prepare input data
Add YouTube channel links to `1_Channels_Urls.txt`, place NetScape cookies into `Cookies\1_Ready` and enter the license key.
Channel queue and account pool are ready02
Connect ReCaptcha and proxies
Enter the CapMonsterCloud API key and, if needed, enable IPv4 proxies, proxy-check timeout and IP rotation URL.
Runtime is ready for bulk processing03
Run parsing
The template checks cookies, opens the channel, detects the business email button, solves ReCaptcha and stores found data in the local database.
Emails and metadata are collected04
Replace accounts automatically
When an account reaches the daily email reveal limit, the thread takes the next cookie file and continues processing the list.
One account limit does not stop the whole list05
Save XLSX
The `Save` task exports results into `Results` and splits the report into multiple files when there are more than 500,000 rows.
Spreadsheet is ready for analysisMore than a one-off script
A ready workflow built around YouTube limits
YouTube-ReCaptcha does not behave like one request to a page. It checks cookies, proxies and the channel, solves ReCaptcha, watches the account limit, switches the session and saves data into a database before final XLSX export.
View running and saving flowSolves one exact task
This is not a universal YouTube parser. It is a focused product for bulk collection of public channel emails behind the business contact button.
Handles YouTube account limits
The template tracks the email reveal limit on an account and continues through the next account from the prepared cookie pool.
No manual captcha solving
Google ReCaptcha is solved through CapMonsterCloud, so the operator does not have to pass the protection on every channel by hand.
Produces a readable result
Emails, statuses and channel metadata are exported into XLSX, while temporary and final errors stay separated from found contacts.
Audience
For teams that work with public channel contacts at scale
The product is not for checking a couple of channels by hand. It is for recurring email and metadata collection from large channel lists.
YouTube and outreach teams
For preparing spreadsheets with public business emails before manual review, filtering and further communication.
Marketers and media buyers
For checking large channel lists by niche, topic, country or an existing partner prospect database.
Data operators
For turning scattered channel links into a report with contacts, username, country, creation date and channel statistics.
Automation specialists
For clients who need a ready ZennoPoster or ZennoBox workflow instead of building a custom parser and ReCaptcha chain.
Requirements
Accounts, cookies, CapMonsterCloud and a stable network
Stable bulk runs depend not only on thread count, but also on cookie quality, proxies, network speed and ReCaptcha service balance.
ReCaptchaCapMonsterCloud account with a positive balance
CookiesNetScape cookies for channels with an active YouTube session and a working account channel
Proxiesfast, stable IPv4 proxies with low ping; IP rotation is supported through URL
Input listYouTube channel URLs with ID or @username
RuntimeWindows 10-11, ZennoPoster or ZennoBox, desktop PC or dedicated server
Hardware and networkIntel i7 2019+ class CPU or similar AMD, 16 GB RAM or more, internet from 100 Mbps
SpreadsheetsMicrosoft Excel or a compatible editor for viewing XLSX; export itself is generated without installed Excel
Technical base
Confirmed product parts and honest limitations
The page keeps product constraints explicit: the template automates collection, but it does not remove YouTube limits or account requirements.
Current v2.0.5 project
The open ProjectMaker project confirms the `Parsing` and `Save` tasks, input settings, cookies, proxies, LiteDB and XLSX export.
CapMonsterCloud as the main service
The current version uses CapMonsterCloud for Google ReCaptcha; RuCaptcha support was removed in the v2.0.0 branch.
XLSX through EPPlus
Since v2.0.5, the report is generated through the built-in EPPlus library and is not blocked by missing Microsoft Excel.
Honest limitations
Results depend on cookie validity, YouTube limits, proxies, CapMonsterCloud balance and whether the channel owner published an email.
FAQ
Common questions before launch
Short answers about limits, cookies, speed, results, runtime and YouTube-ReCaptcha restrictions.
What is YouTube-ReCaptcha?
It is a ZennoPoster template for bulk parsing of public YouTube channel emails opened through the business contact button and protected by Google ReCaptcha.
How does it work around the 5-emails-per-account limit?
It uses a pool of cookies with active YouTube sessions. When one account reaches the daily email reveal limit, the thread takes the next account and continues processing the list.
Why are NetScape cookies required?
Cookies allow fast authorization in YouTube without a manual login. A working cookie login takes less time than full account authorization and fits hot replacement.
Which data is saved to the report?
The XLSX report includes button email, description email, channel title, URL, username, country, creation date, subscribers, views and video count.
How fast is it?
Expected references: cookie check up to 5 seconds, channel check up to 5 seconds, ReCaptcha solving from 2 to 10 seconds. Real speed depends on accounts, proxies, IPs and current YouTube limits.
What happens when a channel has no email?
The template does not invent a result. Missing email buttons, temporary failures, limits and permanently problematic links are handled with separate statuses.
Is Microsoft Excel required?
Excel or a compatible editor is useful for viewing spreadsheets. Since version 2.0.5, XLSX export itself is generated through EPPlus and does not require installed Excel.
Can ZennoBox be used instead of ZennoPoster?
Yes. ZennoPoster and ProjectMaker are used for editing and development, while ZennoBox is suitable for running the finished product.
Are there limitations?
Yes. YouTube-ReCaptcha is not an official YouTube tool and does not remove platform limits. Test a small sample before a large run.
Ready to automate YouTube channel email collection?
Read the documentation, review pricing or contact us directly to choose a YouTube-ReCaptcha workflow for your channel volume and account pool.