How-To Guide

How do you post to YouTube with Claude?

Claude has no native YouTube posting. Use a YouTube MCP connector holding the channel token, or call the Data API yourself, with quota and Shorts limits.

10 min read

By the Superdirector editorial team. Google's YouTube Data API reference, Quota Calculator and YouTube Help pages, and Anthropic's Claude connector documentation read November 15, 2026; six competitor guides on posting to YouTube with Claude read the same day.

At a glance

How do you post to YouTube with Claude?

Claude cannot publish to YouTube by itself. It writes the title and description, and something else has to hold the channel's Google authorization and run the upload. You have two routes. Connect a hosted YouTube MCP connector, where the provider keeps the token and its own API quota, or build a Google Cloud project that calls videos.insert yourself. A hosted connector takes minutes and a direct build takes a day or more, but YouTube's rules do not move: a 256 GB or 12 hour file ceiling, a 15 minute default length until the account is verified, and a default allowance of 100 upload calls per project per day.

  • Claude has no native YouTube integration; it drafts metadata and stops there.
  • Route one: add a YouTube MCP connector, connect the channel through Google sign-in, then ask Claude to list the channel before posting.
  • Route two: create a Google Cloud project, request the youtube.upload scope, and call videos.insert with a resumable upload.
  • YouTube's limits are its own: 256 GB or 12 hours per file, 15 minutes by default, and 100 upload calls a day.
  • Shorts is a shape decision, not a toggle: vertical or square, three minutes or less.
Numbered sequence of five steps: pick an uploading connector, connect the channel, add the server to Claude, confirm the channel appears, then ask in plain language.

The connector route is five plain steps, and the first one is the gate: most YouTube servers only read, so a connector must upload before anything else matters. Original diagram, drawn from the connector and directory guidance in this article, read November 15, 2026.

Superdirector

Make it work for your brand

Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.

The short answer: Claude drafts, a connector or your own app uploads

Claude cannot publish to YouTube by itself. Out of the box it writes a title and a description for you to copy, and that is the whole of its YouTube ability. To get a video onto a channel, something else has to hold the channel's Google authorization and run the upload. You have two ways to put that something between Claude and YouTube.

The first way is a hosted MCP connector. The Model Context Protocol is "an open standard, created by Anthropic, for AI applications to connect to tools and data" (Claude Help Center). You add a server that already knows how to upload to YouTube, connect the channel in the provider's dashboard, and from then on you can ask Claude in plain language to publish. The second way is a Google Cloud project of your own, calling the YouTube Data API directly. You own the token and the quota, and you do the setup yourself.

Blotato, one of the vendors selling the first route, frames the choice the same way. "YouTube is the heaviest lift of any platform in this series, because an upload is not a string of text, it is a file plus a set of required metadata plus a quota YouTube grants you" (Blotato). Claude can help with the metadata. It cannot spend a quota or hold a Google token.

RouteSetupWho holds the Google tokenWhat it costs you
Hosted MCP connectorPaste a connector address in Claude and connect the channel in the providerThe providerThe provider's subscription, plus its own upload allowance
Your own Google Cloud projectGoogle Cloud project, Data API enabled, OAuth consent screen, upload scopeYouGoogle's API is free within quota; the cost is your setup and upkeep

Everything below applies to both routes. The file ceiling, the length rule, the metadata fields, the daily upload allowance and the Shorts shape test belong to YouTube. Setup gets shorter with a connector. A single YouTube rule does not.

Route one: connect a YouTube MCP connector to Claude

This is the route most people want, because it turns a Google Cloud chore into a few clicks. The shape is the same for every provider that uploads: connect a channel on the provider's side, add the server to Claude, then talk to it. The steps below are the ones the stored guides agree on.

  1. Pick a connector that uploads. Many YouTube MCP servers only read transcripts, comments and channel statistics. PostOnce draws the line plainly: "Most read YouTube. This one uploads." (PostOnce). Check the provider's own tool list before you connect.
  2. Connect your channel in the provider. You sign into Google on Google's own screen and grant the upload permission. The provider keeps the resulting token, so Claude never sees your password and you never create a Google Cloud project (Blotato).
  3. Add the server to Claude. In Claude, open Settings and then Connectors and add a custom connector by pasting the address the provider gives you. A directory listing and a custom URL end at the same place: "Both run on the same MCP infrastructure: the runtime, transport, authentication, and tool-calling code paths are identical" (directory vs custom).
  4. Confirm the channel is visible. Ask Claude to show the connected accounts. If YouTube is missing, reauthorize it in the provider. This is the most common reason a first upload never arrives.
  5. Ask in plain language. Name the file or public URL, the title, the description and the visibility. The provider translates that into its own upload call, which runs Google's API underneath.

One network detail surprises people. Claude reaches a connector from Anthropic's cloud, not from your laptop: "Claude connects to your remote MCP server from Anthropic's cloud infrastructure, rather than from your local device" (Claude Help Center). The server has to be reachable over the public internet. That also explains why a video sitting on your desktop does not travel with the prompt; the provider needs a public URL or its own upload link.

Plan limits still apply. Custom connectors work across the Free through Enterprise plans, and "Free users are limited to one custom connector" (Claude Help Center). One YouTube account fits inside that limit. On a Team or Enterprise plan, an Owner adds the connector to the organization first.

The trade is control for speed. You skip the Google Cloud project, the consent screen and the API audit, because the provider already did those on its side. In exchange the provider holds the token, and its upload allowance, not yours, is the one that runs out.

Route two: upload with the YouTube Data API yourself

Building it yourself means you own the token and the upload call. Choose this when YouTube is the product, when a client requires the credentials to stay in their cloud, or when a connector's limits block the job.

Google's reference describes the endpoint in one line: "Uploads a video to YouTube and optionally sets the video's metadata" (videos.insert). The request is a POST to the upload host, and it needs authorization: "This request requires authorization with at least one of the following scopes" (videos.insert). Request the youtube.upload scope, which allows an upload and nothing else, when that is all the job needs.

  1. Create a Google Cloud project and enable the YouTube Data API. The upload method is part of that service, and its quota belongs to the project you enable it in.
  2. Configure the OAuth consent screen and request the upload scope. The user consents on Google's screen and the token is issued to your app.
  3. Call videos.insert with a resumable upload. The method "supports media upload" and accepts "video/*, application/octet-stream" (videos.insert). Set the part parameter to the metadata parts you want to write, usually snippet and status.
  4. Send the metadata, then read the response. A successful call returns a video resource with an ID. Keep that ID; it is how you confirm the upload later.

File size is a Google ceiling, not a connector preference: "Maximum file size: 256GB" (videos.insert). YouTube Help adds the length side: "The maximum file size you can upload is 256 GB or 12 hours, whichever is less" (YouTube Help). A two hour export can fit in the bytes and still fail the clock.

Privacy has a default worth knowing. If you send no privacy value, "the uploaded video's privacy status defaults to public" (videos.insert). Send unlisted or private when you want a review step. One older rule has also changed: "Videos uploaded from unverified API projects are not restricted to private viewing mode" (videos.insert). The audit still matters for quota, but it no longer decides whether a first upload can be public.

The metadata YouTube requires, and the fields that trip people

An upload is a file plus metadata, and the metadata is where most connector differences show up. These are the fields Google's reference lets you set, with the limit that matters beside each one.

FieldWhat to sendWhy it matters
TitleUp to 100 characters (YouTube Help); an empty title is rejected (videos.insert)A blank title fails the whole call with invalidTitle
DescriptionUp to 5,000 characters (1Social)Links and calls to action live here, not in a separate field
Privacyprivate, unlisted or public (PostOnce); public if you send nothing (videos.insert)Omitting it can publish before you have reviewed the file
Notify subscriberstrue or false (videos.insert)A back catalogue upload can notify a whole channel
Scheduled publishstatus.publishAt in the request body (videos.insert)The API schedules the publish itself, no separate queue needed
Declarationsstatus.selfDeclaredMadeForKids and status.containsSyntheticMedia (videos.insert)Realistic altered content needs the synthetic-media declaration (Blotato)

Connectors cover these fields unevenly. PostOnce accepts a 100 character title that defaults to the first line of your text, sends up to eight description hashtags as the video's tags, and takes one video of up to 768 MB (PostOnce). Blotato's connector takes the title, description, privacy and subscriber choice, but says plainly that "Tags are not supported at all" (Blotato). Neither is wrong. You just have to know which fields your tool passes through before you blame YouTube.

Two more fields split by tool. A custom thumbnail only works on a channel YouTube has verified, so Blotato's thumbnail field is no help before verification (Blotato). And a connector may not expose playlists or made-for-kids marking at all; PostOnce lists community posts, image-only posts and playlists as unsupported (PostOnce). Upload through the API when those fields matter.

The limits: file size, length, quota and Shorts shape

YouTube enforces several ceilings at once, and they live in different documents. The file ceiling is on the API reference and the Help Center. The length rule is on the Help Center. The daily upload allowance is on the quota calculator. The shape rule is on the Shorts help page.

LimitValueWhere it bites
File size256 GB, or 12 hours, whichever is less (YouTube Help)A long export can fail on bytes or on clock
Default length15 minutes per video until the account is verified (YouTube Help)Verified accounts can upload longer videos
Daily uploads100 videos.insert calls per project per day (Quota Calculator)A back catalogue batch stops at the bucket
Upload quota cost1 unit per call from the Video Uploads bucket (videos.insert)Uploads do not eat the 10,000 unit general quota
Other API calls10,000 units per day across all other endpoints (Quota Calculator)List and update calls share a separate pool

Two quota details explain most surprises. The upload method has its own bucket: "The search.list and videos.insert methods have their own quota buckets" (Quota Calculator). And the reset is fixed: "Daily quotas reset at midnight Pacific Time (PT)" (Quota Calculator). A failed upload still costs its call, so a retry loop can spend the allowance without posting anything.

Shorts is not a switch you set. YouTube decides the format from the file, and a Short has to be vertical or square and no longer than three minutes (1Social). The help page puts the creation tool at three minutes and caps an uploaded Short at 1080p (YouTube Help), and its view count now starts as soon as a Short plays or replays (YouTube Help).

The failure is quiet. "YouTube does not refuse a video that is the wrong shape for Shorts" (1Social). A horizontal clip uploads as an ordinary video, and "nothing in the response tells you it went to the wrong place" (1Social). Check the frame and the duration before the upload, not after it lands on the channel page.

Four-row matrix pairing each YouTube ceiling with the failure it causes: 256 GB or 12 hours fails on bytes or clock, 15 minutes while the account is unverified, 100 uploads a day stops a batch, and 10,000 units a day is a shared pool.

Each ceiling lives in a different document and fails a different way; the 10,000-unit general quota is one pool shared with list and update calls, while uploads draw from their own bucket. Original diagram, from the YouTube Help and Quota Calculator pages read November 15, 2026.

Verify the upload and fix the common failures

A queued upload is not a published video. Treat the returned identifier as the start of verification, not the end of the job.

  1. Read the response. videos.insert returns a video resource with an ID on success. Some connectors return their own post ID instead, so ask for the YouTube URL.
  2. Open the URL on the channel. Confirm the title, the description, the visibility and the duration. A private or unlisted video is live but hidden, which is a success, not a failure.
  3. Ask the connector for status. Blotato, for example, says "you can have it call blotato_get_post_status to confirm the video published" (Blotato). A notification is not that confirmation: "Test each stage and do not treat a Cowork notification as proof of publication" (Genviral).
  4. Match the error to the fix. uploadLimitExceeded means the channel used its uploads (videos.insert); invalidTitle means an empty or invalid title; a failed upload that returns no error body usually means the daily bucket emptied.

Do not retry a quota failure in a tight loop. Each attempt is another call against the same bucket. A provider that shares one allowance across all its customers can also refuse a post while your own project would still have room, so a refusal is a statement about the tool, not about YouTube.

If the video is live but the wrong format, the fix is the file, not the caption. Re-export it vertical or square and under three minutes, then upload again; adding a hashtag to the description does not move an ordinary video onto the Shorts shelf. One vendor documents appending #shorts through its provider while still letting YouTube make the final call (1Social).

Which route to choose

For most people the hosted connector is the right first move. It takes minutes, it skips the Google Cloud project and the consent screen, and one connection often covers several networks. You give up control of the token and depend on the provider's allowance. That is a fair trade when you run one channel and post a few videos a week.

Build the direct route when YouTube is the product, when the credentials must stay under your control, or when you need metadata fields a connector does not expose. The API is free within its quota, and the quota is generous for a normal channel: 100 uploads a day is far more than most teams use. The cost is the setup and the upkeep of a Google Cloud project.

Superdirector sits on the hands-on side of that line. The $29 a month plan connects Superdirector's MCP to Claude for research, drafting and asset creation you direct. The $199 a month plan runs one AI-operated social account that publishes eligible Instagram carousels and single link-free X text posts on a schedule, with posting turned on once at the account level as a standing permission. Neither plan posts to YouTube. A YouTube token stays with a connector or with your own project, which is the same boundary every route here shares.

Whichever route you pick, the order of work is the same. Choose where the token lives, connect the channel, upload one video end to end, and verify it on the channel before you schedule a batch. Those limits will still be waiting on the second upload.

Frequently asked questions

How do you post to YouTube with Claude?

Claude cannot post to YouTube on its own; it writes the title and description and something else uploads the file. Connect a YouTube MCP connector that holds the channel token, or build a Google Cloud project that calls the YouTube Data API's videos.insert method. A hosted connector takes minutes; a direct build is a developer setup, and both obey YouTube's file, length, metadata and quota rules.

Does Claude have a native YouTube integration?

No. Claude has no built-in YouTube posting or upload button. Every working route reaches YouTube through a third-party MCP server or through code you write against Google's API. As of November 2026 there is no YouTube MCP server from Google.

Can Claude upload a video file from my computer?

Only through a tool that can read the file. A hosted connector usually wants a public URL or its own upload link, so a video pasted into chat does not reach YouTube. In Claude Code, a skill can read a local path and upload it for you. Check how your chosen connector takes the file before you rely on it.

What are YouTube's upload limits for an API upload?

Google's reference allows files up to 256GB and accepts any video MIME type. YouTube Help caps a video at 256 GB or 12 hours, whichever is less, and limits an unverified account to 15 minutes by default. The API's default allowance is 100 videos.insert calls per project per day, and one call costs one unit from the Video Uploads bucket.

Is a vertical clip automatically a YouTube Short?

No. YouTube decides from the file itself: a Short has to be vertical or square and no longer than three minutes. YouTube does not refuse a horizontal clip; it publishes it as an ordinary video and the response does not say the clip went to the wrong place. Upload Shorts at up to 1080p.

Why did my YouTube upload fail?

The usual causes are an exhausted daily upload allowance, an empty or invalid title, a privacy value the channel cannot set, or a video longer than the account is allowed to upload. An unverified account is limited to 15 minutes per video, and the API returns uploadLimitExceeded when the channel has used up its uploads. Read the error body before you retry.

Related practical guides

Pick where the Google token lives

Choose the hosted connector if you want to post this week, or the direct API if the token and quota must stay with you. Either way, upload one video end to end and open its URL before you schedule a batch.