Contact ytbench

ytbench is built and run by one person, not a support team. Every message to contact@ytbench.com is read by that person directly — there is no ticketing system, no first-line support script, and no outsourced inbox. The sections below cover the four things people usually write in about, so you can include the right details the first time.

Report a problem with a tool

If a page won't load, a download comes back empty, or a result looks obviously wrong, email the tool's exact URL (for example `/tools/youtube-thumbnail-downloader`), the input you entered, and what you expected to see instead of what actually happened. A screenshot of the result screen is more useful than a description of it, since it shows the exact error code or message the tool returned. If the problem only happens with one specific channel or video, include that link too — most tool bugs turn out to be about how one particular page is structured, and having the exact input makes it possible to reproduce the issue instead of guessing at it.

Correct a channel reading

The monetization checker and other tools read whatever a channel's public page shows at the moment of the request — they don't have access to anything YouTube doesn't already display to any visitor. If you run a channel and believe a result is wrong (a membership or Store signal that shouldn't be there, a stale subscriber count, or a banner/thumbnail that doesn't match what you currently have live), send the channel URL, the result you got, and what your channel actually shows right now. Results can also be cached for up to 24 hours after a channel changes, so if you just updated something, that alone can explain a mismatch — mention the timing and it's easy to rule that out first.

Copyright and takedown requests

ytbench doesn't host or store video, thumbnail, or banner files — tools that let you download an asset fetch it directly from YouTube's own CDN at request time and pass it through, they don't keep a copy on our infrastructure. If you believe a tool is being used to infringe on rights you hold, email the exact page URL, the channel or video in question, and a description of the request so it can be identified and reviewed.

Privacy and data requests

ytbench doesn't require an account, doesn't collect your name or email unless you write in, and doesn't log which visitor looked up which channel — see the Privacy Policy for the full detail on what is and isn't cached. If you still have a question about what a specific query stored, or you want something removed that you believe was recorded about you, email the request along with enough detail (roughly when you used the tool, and what you're asking to have checked or removed) to act on it.

What happens after you contact ytbench

Every message gets a reply from a real person, not an autoresponder. Bug reports with a reproducible input are usually the fastest to turn around, since there's a concrete case to test against; channel-reading corrections and copyright requests take a bit longer because they require pulling up the channel or asset in question and checking it against the current code before responding. If a fix changes how a tool behaves, it ships as a normal update to the site — there's no separate notification system, so if you'd like to know when something is fixed, say so in your message and that will be confirmed directly.