How to Schedule Pinterest Posts: Formats and Cadence

Pinterest’s scheduler takes a Pin up to thirty days out, ten at a time, one Pin per schedule, and it will not let you swap the image once the Pin is queued (Pinterest Help). Past that line the job is yours: board id, media, a cover image when the media is video, link, timestamp. This guide covers both upload paths, the board taxonomy, the native horizon, what breaks, and the twenty-minute weekly routine I run for PostSider’s account.

Operations guide: two upload paths, one board decision, one weekly slot.

In short

• Pinterest’s own scheduler stops at 30 days ahead and 10 queued Pins, and it will not let you change the image after you schedule.
• Image Pins take 2:3 stills, video Pins take MP4 or M4V between 4 seconds and 5 minutes, and every video Pin needs a separate cover image.
• A Pin is created on one board. Pushing the same Pin to five boards every week is the pattern Pinterest treats as duplicate content.

A queue beats a burst on Pinterest

Pinterest’s help pages say there is no set engagement window for a Pin, and that a Pin can gain engagement hours, days, months, or even years after publication, with seasons and holidays among the factors that change performance (Pin performance and distribution). Pinterest’s marketing calendar guidance tells brands to have a seasonal campaign ready a couple of months ahead. A batch uploaded on the first of the month misses it; a queue does not.

A burst also collapses your feedback loop. Twenty Pins in one afternoon give you one day of data across twenty creatives. The same twenty across five weeks give you a weekly read on which board and which format work.

Evergreen recycling is the part people get wrong. Recycling returns a published Pin to a later slot, and the safe version varies the creative or the destination so the second appearance is not a copy of the first. Pinterest asks brands not to repeatedly save the same Pins or upload content that already exists on the platform, and warns that accounts doing it can be flagged as spam and temporarily blocked from creating Pins. Recycling a product shot onto a new board months later with new copy is normal. Re-posting the identical Pin to the same board every Tuesday is what gets an account restricted.

For per-network frequency, the how often to post guide has the published recommendations. Pinterest’s own floor is one original Pin a week.

The pin format decides the upload path

Pinterest has two organic formats, image and video, each with its own upload path and validation. A scheduler that stores one media blob and one caption breaks on the second.

Pinterest’s developer documentation states that organic Pin formats have been simplified to image or video Pins, so an Idea Pin goes through the video path in the API (creating boards and Pins).

	Image Pin	Video Pin
Accepted files	BMP, JPEG, PNG, TIFF, WEBP	MP4 or M4V on web
Size and length	20 MB on web	4 seconds to 5 minutes, 2 GB per the video sheet
Ratio	2:3, listed as 1000 x 1500	9:16 or 1080 x 1920 recommended

File types and the 20 MB image ceiling come from Pinterest’s Pin specs, which also sets titles at 100 characters and descriptions at 800. The 2:3 recommendation and the 1000 x 1500 dimensions match the image sizes cheat sheet. The 4-second floor, the 5-minute ceiling and the 2 GB limit are in the video specs sheet, which carries the 1080 x 1920 safe zones: 270 px top, 65 px left, 195 px right, 790 px bottom.

Pinterest says descriptions do not appear in the home feed or the search feed, and that the algorithm uses them for relevance. Treat the description as an indexing field: search phrase in the first sentence, product detail after it.

Each path stores different things. An image Pin needs the file, the board id, the title, the description, the link and alt text. A video Pin needs the media id from the upload handshake, a cover image URL that resolves publicly, and the same board id. That handshake is three calls: register the upload, push bytes to the returned URL, poll the media id until processing succeeds, then create the Pin with that id and the cover URL. Pinterest returns 400 when the cover is missing.

PostSider’s Pinterest connection takes up to five images on one Pin and rejects a set whose images do not share width and height. That rule catches the catalogue export where row one is 1000 x 1500 and row two is 1000 x 1333.

Boards are the taxonomy, so schedule to the right one

Every Pin is created onto one board, and the board id is required in the create call. Board choice decides who sees the Pin.

A board is a topic promise, and a Pin that breaks it gets scrolled past by its followers. The common failure is a board called Products that receives every image the company owns: no audience to serve, no search phrase to rank for.

A Pin can reach a second board without a second create call. Pinterest’s API has a Save Pin call that places an existing Pin on another board or a board section. Use it when the Pin fits both topics, and skip it when the second board is only a volume target.

Settle the board list once, in writing: product line, seasonal, archive. A client reviews it in a minute, and every queued Pin inherits the decision.

Native scheduling has a horizon; a queue does not

Pinterest’s scheduler is a UI feature with a ceiling, documented inconsistently. A stored job has no ceiling except the one you set for review.

The scheduling page describes a business account booking Pins up to 30 days ahead, one Pin at a time, 10 Pins queued at once, with the publish date, title, board, description and link editable afterward. If you rely on the native tool, 30 days and 10 queued Pins are the whole plan.

None of this exists in the API. POST /pins publishes when called, with no scheduling field in the request body, so any tool offering a future date stores that date and holds the create call until the minute arrives (create Pin reference). The UI schedule is Pinterest’s feature; the API schedule is the integrator’s, which a client notices when a Pin goes out at the wrong hour.

That is the case for a queue, and why PostSider’s Pinterest scheduler exists: the job sits in the posting queue with its board, media and link, Smart Slots finds the next free time, and the create call fires at the stored minute.

What breaks when a Pinterest post fails

Most failed Pins fail before Pinterest sees them: a file outside the accepted type or size, a video outside 4 seconds to 5 minutes, a cover URL that does not resolve.

Symptom	Check first
400 on create	Cover URL on video, then title and description length against 100 and 800
401 or 403	Token expiry, then boards:read, boards:write, pins:read, pins:write
Video publishes as a static Pin	media id finished processing; creative type reads REGULAR until it does
Multi-image Pin rejected	every image has the same width and height
Pin publishes, then no traffic	destination link resolves, domain allows Pinterest’s crawler
Account limited or Pin removed	same asset saved to several boards in a short window

Access errors are usually scope errors. An app that can read boards but not write to them fails at create time, and a token issued for a personal account fails on a business board the same way. Broken links are a distribution problem: Pinterest asks brands to avoid broken or blocked links and notes that its crawler needs access to the domain. A Pin that publishes and then 404s is worse than one that fails where you can see it.

A 20-minute weekly Pinterest queue

This is the routine I run for PostSider’s account: twenty minutes on a Monday, covering a week across several boards.

1. Pull the week’s images, or import a CSV when the catalogue has one row per Pin.
2. Write the title under 100 characters with the product name and the search phrase, then the description under 800, phrase in the first sentence.
3. Attach media per format: one file for an image Pin, five files at one canvas size for a set, an MP4 plus a cover for video.
4. Open the per-platform preview and check the crop. A 1:1 export shows up here with its headline in the bottom safe zone.
5. Slot the Pins. Smart Slots takes the next free slot, and I spread three to five Pins across the week instead of filling one afternoon.
6. Send the week for approval when the account belongs to a client. The approval sits on the queued Pin, so the reviewer sees the board, preview and link.
7. Publish, then check the live Pin for board, link and crop. A scheduled Pin is not proof that Pinterest accepted it.

Once a week, open analytics and read saves rather than impressions. A Pin that keeps getting saved a month after publication is the one to recycle into a later slot with new copy.

I build PostSider, a scheduler for 30+ networks, and I run its Pinterest account on the queue described here.