A finished video. A time you choose.

How to schedule YouTube Shorts: Studio, tools & API

Here’s how to schedule YouTube Shorts: upload your finished video in YouTube Studio, choose Schedule, then set a date, time and time zone. Studio keeps it private until release. Use the tool and agent paths below if you also need a shared queue or an automated publishing workflow.

How to schedule YouTube Shorts in YouTube Studio

For a public release on YouTube, start here. Have the finished video, title and description ready, and check that you are in the intended channel.

  1. Select your finished video

    Sign in to YouTube Studio. Choose Create → Upload videos, then select the file.

  2. Complete the video details

    Add your title and description. Review the audience and altered-content questions truthfully, and complete the remaining upload checks.

  3. Choose the release time

    Open the Schedule card. Select the date, time and time zone you want, then choose Schedule.

Follow YouTube’s scheduling instructions, Shorts upload guide and video-details guidance. These are documented steps, not an authenticated upload performed for this guide.

Schedule with a tool or manage a dashboard queue

If you want to upload, write and schedule from one calendar, choose a tool with a YouTube Shorts composer. Check its current YouTube workflow before connecting: does it publish automatically, require a reminder, or only upload privately?

For example, Buffer’s own YouTube guide explains its composer and scheduling options. Use the tool’s instructions for channel connection, video upload and scheduling; check the final channel, visibility and time before saving.

Using Postdom’s Schedule dashboard

Postdom’s Schedule page manages requests already created by an agent or API. It is not a new-video upload form. If the queue is empty, start with the agent example below.

  1. Find the request

    Open Schedule, select the account filter and find the post. Read its status and UTC time. A request in Upcoming may still say requires_approval; appearing in the queue is not approval.

  2. Review before the requested time

    Use Review or Open review when approval is required. Check the exact video, account, caption, audience and disclosure settings. Approve only the request you intend to send. A scheduled request has not yet published.

  3. Change or cancel the schedule

    For a scheduled post, enter a future time in New publish time · UTC and select Reschedule. Cancel schedule returns it to a draft. Draft or missed requests offer Reschedule and Publish now; either needs a deliberate human decision.

  4. Check the outcome

    Open the run after the requested time and read its destination result. Keep the post ID if it failed or missed its time; do not create a duplicate to make the queue look complete.

Check your UTC time before you submit

Enter the UTC time you plan to use in Postdom. Preview it in your audience’s time zone, including that date’s daylight-saving offset. This does not schedule anything or check account eligibility.

Schedule through an API or AI agent

Postdom publishes finished videos you supply to TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads and Bluesky. It does not generate the video. The example here uses its released MCP tool with YouTube only.

  1. Connect and select the channel

    Follow the MCP connection guide. Read get_workspace_status, list_accounts and get_brief. Select the YouTube account’s providerAccountId, not its internal ID. Stop on disconnected accounts, paused publishing or unclear authority.

    For this reviewed example, a human must explicitly select L1 Post review and confirm the returned policy. Do not assume L1 is the default.

  2. Prepare the video and time

    Use an existing accepted video URL, or an already-stored media handle instead. The released upload_media tool does not send all metadata required by the current upload API, so this example does not use it. Arrange an accepted media source first.

    Choose a future UTC time. The caption’s first line becomes the YouTube title and is truncated by the tool; review the resulting title before submitting.

  3. Submit once, then wait for review

    After the human confirms the settings and authorizes submission, call publish_video with the reviewed inputs. Keep a stable idempotency_key for that exact request. Return a requires_approval response to the human; the agent must not approve it or change policy.

  4. Follow the same post ID

    Use get_publish after approval and again after the requested time, within an agreed waiting budget. Report the returned status and destination result. A request receipt, approved plan or scheduled status is not proof of publication. Even a successful private upload is not a public Short.

See the worked agent request and response

Illustrative inputs, exercised against a local fixture service using the released MCP package. No real account connection, provider upload or authenticated publication was performed. Replace the example channel, URL, caption, key and date with reviewed values; the distant example date is not a supported scheduling-window claim.

publish_video arguments
{
  "account_ids": [
    "youtube-channel-example"
  ],
  "video_url": "https://media.example.com/finished-short.mp4",
  "caption": "A quick look at our new workspace\nA finished demo supplied for review.",
  "publish_at": "2099-06-15T09:00:00.000Z",
  "intent": "Schedule the human-reviewed video as a private YouTube upload after explicit post approval.",
  "idempotency_key": "youtube-short-schedule-example"
}
Illustrative response excerpt: still awaiting approval
{
  "id": "post-example",
  "version": 1,
  "status": "requires_approval",
  "scheduled_for": "2099-06-15T09:00:00.000Z"
}

get_publish({ "post_id": "post-example" }) checks this same request. REST integrations use POST /v1/posts with publish_at and read GET /v1/posts/:id. MCP’s video_url maps to REST’s media_url; do not paste the tool arguments unchanged into a REST call.

See publish_video reference and the released tool implementation. These Postdom endpoints are not YouTube Data API endpoints.

If the Short does not appear when expected

Studio: still private after the time
Check channel restrictions. YouTube says a Community Guidelines strike can prevent a scheduled release; reschedule after the restriction ends. Check the video’s visibility rather than assuming the upload failed.
Postdom: missed_approval or missed_schedule
Open the request and ask the human to choose a new time or Publish now. Do not silently backfill a missed slot. For a failed request, preserve its error and fix the cause before deciding whether to retry.
Postdom: published, but nobody can see it
A successful MCP YouTube upload is private. Check the actual visibility in YouTube; the tool did not request a public release.
The displayed day differs
Compare the full timestamp and time zone. Postdom displays and accepts schedule edits in UTC; Studio lets you choose a time zone. Convert for the specific date, since daylight-saving offsets can change.

Common scheduling questions

Can you schedule YouTube Shorts?

Yes. YouTube Studio supports scheduling a Short for a future public release. A third-party tool may schedule differently: confirm whether it queues an upload or actually schedules public visibility.

Can I change a scheduled Short’s time?

In Studio, open Content, select the video and edit Visibility. Keep it private, choose Edit draft, change the Schedule time and save. In Postdom, open the existing request in Schedule and use Reschedule; its entry field uses UTC.

Does the Postdom agent example make my Short public?

No. The released MCP tool sets visibility to private, madeForKids to false and containsSyntheticMedia to true, without overrides. Its publish_at schedules a provider handoff, not a public YouTube release. Confirm that these settings truthfully fit the video before submitting; stop if they do not. Use Studio for the public-release workflow.

How far ahead can I schedule?

This guide does not state a universal maximum scheduling window. Check the date picker and current guidance for the method you use. An accepted time or approved request is not proof that the video has published.

What if approval arrives after the requested time?

For a Postdom request marked missed_approval, a human must explicitly choose Publish now or Reschedule. Do not silently publish late, create a duplicate request, or assume that approving a plan means a post has published.