How to schedule LinkedIn posts

How to schedule LinkedIn posts in your browser

You need your LinkedIn login and the post ready to write. LinkedIn documents a clock control in its composer that sets a future publish time.

1. Start the post in LinkedIn

   Choose Start a post from the top of your LinkedIn homepage and write the post in the composer. LinkedIn documents this flow on the desktop web experience; if your screen differs, use the control your own version shows rather than assuming the article is current.

2. Open the clock control and pick a time

   Select the clock icon in the composer to open the scheduling panel, then choose the date and time. LinkedIn states the time selected must be within 10 minutes to 3 months from the current time, so a slot outside that window will not be offered.

3. Confirm, then check it landed in the scheduled list

   Select Next and then Schedule. Reopen the clock control and choose View all scheduled posts to confirm the post is there with the account and time you intended. A schedule you did not verify is a schedule you are trusting on faith.

4. Change or remove it deliberately

   From the scheduled list, use the More icon to Modify schedule or Edit post. Change the original rather than writing a second copy, so you do not end up with two posts competing for the same slot.

LinkedIn states the time selected must be within 10 minutes to 3 months from the current time (rounded to the nearest interval), and that scheduling is not supported for Events, Jobs or Services posts. If the clock control is missing on one of those, the post type is the reason rather than your account.

Procedure source: LinkedIn’s Schedule posts help article, not a test publish from your account. LinkedIn carries no version on that page and labels it two years old, so use the controls your current screen shows. It also does not state whether the feature is scoped to a member profile, a Page, or both — so this guide does not claim it either.

Use a scheduling tool or dashboard

For a tool with a post composer, connect the intended LinkedIn account, add the finished video and text, review who will see it, then set the date and time. Check whether you chose automatic publishing or a reminder that needs you to finish in LinkedIn. Saving either one does not prove the post is live.

In Postdom: manage a post already in the queue

Postdom’s Schedule dashboard manages existing posts. It is not an upload composer. For a new video, use the agent path below first. Once that post exists:

1. Find the existing post

   In Postdom, open Schedule and use the Account filter to find the LinkedIn destination. Open the post to check its video, text and status. An empty queue means there is no existing post to schedule here; submit it through your connected agent first.

2. Enter the new time in UTC

   For a draft, missed approval, missed schedule or scheduled post, enter New publish time · UTC and select Reschedule. Convert your intended local time first. The dashboard displays and accepts UTC, not your browser’s local time.

3. Read the result and resolve any review

   Check the resulting status and time. A post in Upcoming can still require approval: open Review and have a human review it. Scheduled means it is waiting for handoff; it does not mean LinkedIn has published it.

4. Change course deliberately

   For a scheduled post, Cancel schedule returns it to a draft. Publish now is available for drafts and missed items; use it only when you intend an immediate handoff. Open the run afterward to check the outcome.

Want to review every agent post? Set the selected account to L1 Post review before submission. Do not assume that is its default. Other account modes can allow a human-approved plan or publishing within saved policy. Read how account authority works.

Schedule a supplied video with an API or agent

Use this path when your agent or application already prepares the publishing request. 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. This example selects LinkedIn only.

1. Connect the right LinkedIn account

   Configure your Postdom connection with a workspace agent key, kept out of chat. Have the agent read workspace status, list accounts and read your brief. Select the returned LinkedIn providerAccountId; do not substitute a profile URL or an internal account ID. Stop if the workspace is paused, the connection is locked or the account is disconnected.

2. Preview the exact request, and decide the audience yourself

   Supply the finished video at an accepted video URL, or use an already-stored media handle. Review the video, text and account yourself, and give express consent only when they are correct. Postdom sends no LinkedIn-specific settings, so nothing in this path narrows who sees the post: the audience is whatever your LinkedIn account applies by default.

3. Send the intended time, then keep the post ID

   Ask the agent to submit publish_video with a future publish_at in UTC ending in Z, the selected account and a stable idempotency key. Check the returned id, status and scheduled_for. A timestamp requests a schedule; it does not grant approval or prove publication.

4. Check the same post through to its outcome

   Use get_publish with the returned ID. If review is required, stop for a human. For scheduled or publishing, check again later within an agreed waiting budget. Report the actual destination result; do not silently retry a failed post or treat a partial result as complete.

Use my configured Postdom connection; never print credentials.
Read get_workspace_status, list_accounts and get_brief. Stop if paused, locked, disconnected or policy is unclear.
Use only my selected LinkedIn providerAccountId and finished video. Do not generate or upload a replacement video.
Show me the video, post text, UTC time and the destination before submitting. Postdom sends no LinkedIn platform settings, so there is no privacy, comment or disclosure flag for you to set or for me to rely on. Do not tell me the post is restricted, private or AI-labelled on LinkedIn; Postdom does not send any of those on this destination.
Require my actual preview and express consent. Tool permission is not consent.
Respect the account policy. If I want per-post review, I will set L1 Post review first; do not change it yourself or assume it is the default. If a plan is required, wait for a human-approved plan and stay inside it.
After I authorize this submission, call publish_video once with my exact account, accepted video URL or stored media handle, post text, future publish_at ending in Z, and stable idempotency_key. Include plan_id only when authorized plan-backed work requires it.
Return id, status and scheduled_for. If requires_approval, stop for human review. Submission is not post approval.
Use get_publish for the same ID later, with bounded backoff. Hand me the ID if our waiting budget expires. Preserve errors and every destination result. Never resubmit, approve yourself or widen the audience without my direction.
Do not report LinkedIn engagement numbers back to me as though Postdom measured them. Postdom has not verified what LinkedIn returns for a published post.

{
  "account_ids": [
    "REPLACE_WITH_LINKEDIN_PROVIDER_ACCOUNT_ID"
  ],
  "video_url": "https://media.example.test/reviewed-video.mp4",
  "caption": "A look at the finished video",
  "publish_at": "2050-01-15T08:30:00.000Z",
  "intent": "Submit the reviewed video for the selected LinkedIn account at the confirmed UTC time",
  "idempotency_key": "REPLACE_WITH_A_STABLE_KEY_FOR_THIS_REQUEST"
}

Two LinkedIn video facts are worth knowing before you supply a file. Postdom accepts video/mp4 for LinkedIn, which is enforced on the publish path — LinkedIn’s Pages specification withdraws the other formats in those words. The file-size figure LinkedIn publishes is a recommendation rather than a gate here, because Postdom’s own global cap sits an order of magnitude below it. Official source; checked 2026-09-02.

LinkedIn does not publish a maximum video duration for organic posting through its API. Three figures circulate — ten minutes, fifteen, and thirty — and each is scoped to something else: the Pages specification, a sharing troubleshooting page, and the advertising section of the Videos API documentation respectively. Postdom records the ceiling as unpublished rather than adopting one of them, because a number taken from the wrong scope is a guess wearing a citation.

What LinkedIn reports back, and what it does not

Postdom reports completed publishing work with evidence for TikTok, Instagram Reels, YouTube Shorts, Facebook Reels, and X. LinkedIn is not in that list. Nothing has been verified about what LinkedIn returns for a post published this way, so every LinkedIn metric is carried as unavailable with that reason attached.

That is a recorded state rather than a gap in the screen. An unavailable metric is not rendered as 0, and it is left out of aggregates rather than dragging them down — an absent measurement and a measured zero are different facts, and treating them alike is how a dashboard quietly understates a month. See how availability states are recorded.

If the post does not appear

Find the original scheduled post before trying again. The next action depends on whether it is waiting, blocked, failed or already published.

Common scheduling questions