reCAPTCHA v3 (recap3 for short) is a type of bot protection provided by Google that is used by Yeezy Supply. Unlike the regular reCAPTCHA v2 that you might be familiar with, where you have to check a box and solve an image-based challenge, v3 requires no interaction. Instead, when you visit a site that implements recap3, you are given a score between 0.1 (worst) and 0.9 (best) representing how likely it is you are human. This is sometimes referred to as a trust score or humanity score. This score is tied to your Google account, well-established and active accounts will typically have a good score.

To pass the splash page on Yeezy Supply, you need a score of at least 0.7, as well as being randomly selected. Note that using score testers is not a reliable way to determine your score. Just because you have a particular score via the tester does not mean you will have that same score on Yeezy Supply. 

Splashforce uses a recap3 harvester to obtain recap3 cookies for your tasks so that they have good enough scores to pass the splash page. You can open the recap3 harvester by clicking the “Harvest recap3” button at the bottom of the dashboard tab.

Before the Drop

Ahead of drops, you should sign in to your Google accounts. You can do this by opening the recap3 harvester, clicking a session tab, clicking the Open YouTube button and then logging in to YouTube. Once you are logged in, you can close the YouTube window. Even with YouTube closed, you remain signed in to your Google account on that session, there is no need to keep YouTube open. You can add additional sessions and repeat this process to sign into all of the Google accounts you wish to use. Logins persist even after closing and re-opening the bot.

It is acceptable to use both DC and residential proxies in the harvester as long as they are unbanned by Google. Their banned status on Yeezy Supply does not matter. DC proxies are quicker and so will tend to obtain recap3 cookies faster than residential proxies would. As a result of this, DC proxies may get banned quicker than residential ones. Residential proxies are typically metered meaning that using them in the harvester will use up your data plan. Each recap3 cookie you obtain uses about ~90 KB in data. It is also possible to leave the proxy field empty if you wish to run a session on your local IP. 

Note that the harvesters do not actively do anything unless your tasks are running during a drop. Once you have logged in to all of your Google accounts you can close the recap3 harvester until drop time. 

If you want to close a session, click on a different tab so that you are not closing the selected session or otherwise Splashforce may crash. For example, if you want to close session 2, click on session 1 first, then close session 2.


The harvester sessions can be CPU intensive by default. You can enable browser hardware acceleration in the settings tab, which will use the GPU to render the harvester, resulting in better overall performance. You will need to restart the bot for the changes to take effect after checking the box.

Browser hardware acceleration is a little buggy on Mac. You should first sign in to your Google accounts before enabling it since the YouTube window will not be visible otherwise. Also, after enabling it, the first time you open the harvester, it will not display correctly. Simply click the X to close it, and open it again. This time it should display normally.

Harvester Won’t Load

See common problems here: Captcha Solvers

During the Drop

Yeezy Supply only uses the recap3 harvester, not the captcha solver, you should open it before you start your tasks. When you start your tasks, they will attempt to get a recap3 cookie from one of the sessions you have logged in. You can observe this when the reCAPTCHA icon briefly appears in the bottom right of one of your sessions. When your task has a cookie, it will proceed to wait in the splash. Recap3 cookies only have a lifetime of 2 minutes, after which they expire. 

Your tasks will have to get a new recap3 cookie approximately every 2 minutes. It is completely normal to see your tasks rotate between “waiting in splash” and “waiting for recap3 cookie”

If you have a lot of tasks, you will be requesting recap3 cookies quite often in order to continue to wait on the splash page until you are selected. During a typical drop, you will request a lot of recap3 cookies. Splashforce will balance requests for recap3 cookies by evenly distributing them over all your sessions so that no single session is hit too hard. However, you need to ensure that you have enough sessions to be able to support the number of tasks you are running.

Over the course of a drop, you may start with a passable score and end without one. Your recap3 score will eventually decay over time as you continue to request more and more recap3 cookies over a relatively short period. This is especially true if your task to session ratio is too high. This is why it is extremely important not to start tasks too early because otherwise, you are simply hurting your score for no reason if the sale has not yet started. Drops in your recap3 score are temporary and they will recover with time.

Furthermore, it is also possible that your IP or proxy is temporarily banned from the reCAPTCHA service if you make too many requests over a short period. This is why it is important to use distinct proxies for each session to avoid this. Ideally, you would use proxies familiar with those Google accounts. For example, if you farm a Google account with a specific proxy, use that same proxy in the harvester.

Overcoming a Ban

While your tasks are running, you should be observing your recap3 harvester sessions to ensure they are working. If all is well, you should see either the “waiting for captcha” spinner, or the reCAPTCHA icon in the bottom right, although it should only appear briefly. Anything else, like an empty white square, or text saying you could not connect to the reCAPTCHA service, indicates that your IP has been temporarily banned. 

If you have other sessions available that are not banned, Splashforce will continue to use them to get recap3 cookies for your tasks.

To fix a banned session, the first thing you should do is click the skip button, this will remove the stuck recap3 request from the session, and also clear the proxy. Your session should go back to the “waiting for captcha” spinner. Next, you should paste a new proxy into the proxy field and click the apply button. You can also click the “Random Proxy” button to automatically select and apply a random proxy from your proxy list. This should get you back on track.

When you click the “Random Proxy” button, the selected proxy will not be immediately visible in the proxy field. This is simply a visual quirk, clicking another session tab and then going back to your original session will show you the random proxy that was selected and applied. 

There is currently a bug where pressing the “Skip” button will actually remove the proxies from every single session, not just the selected session. Right now, if you use the skip button to fix a banned session, you would need to reapply proxies to all of your sessions. If there are still a good number of working sessions remaining to sufficiently support your tasks, you could simply ignore the banned session.

One potential issue arises if your local IP is banned by the reCAPTCHA service. As aforementioned, when you click the skip button to clear a stuck recap3 request, the proxy will be removed defaulting to your local IP. If you have tasks waiting for a recap3 cookie, a task may immediately attempt to get a recap3 cookie from the banned local session and then that session will become stuck again. If you wish to bring that session back into play, you would need to first stop any tasks that are waiting for a recap3 cookie, then click the skip button, apply the proxy, then start your tasks again.

Was this article helpful?
3 out of 3 found this helpful