# Pinterest pins for every blog post: 2:3 images from a template > Generate a 1000×1500 Pinterest pin for every post from a template, and publish it automatically through Pinterest's RSS auto-publish or its API. Published 2026-11-06 · https://shareglint.com/en/use-cases/pinterest-pins A blog post shared on Pinterest needs a tall image, and the post's 1200×630 `og:image` is the wrong shape: Pinterest recommends 2:3. With Shareglint the same template that makes your link preview renders the pin too — `"sizes": ["og", "pinterest"]` in one request — so every post gets a pin without anyone opening a design tool. This page covers the size, generating pins for a whole blog, and the two ways to publish them automatically. ## The size From Pinterest's specifications ([Pinterest Help](https://help.pinterest.com/en/business/article/pinterest-product-specs), read 2026-11-06): - **2:3 aspect ratio, or 1000×1500 pixels** recommended; "Pins with an aspect ratio greater than 2:3 might get cut off in people's feeds". - **PNG or JPEG**, up to 20 MB on desktop and 32 MB in the app. - All uploads are converted to 8-bit RGB JPEG; Pinterest suggests PNG in sRGB to avoid losing quality. - A pin's title takes up to 100 characters, of which the first 40 may show in feeds; the description up to 800. The `pinterest` preset is 1000×1500 and files come out at twice that by default (2000×3000), still 2:3. PNG is the better choice for text-heavy pins, as Pinterest recommends. ## A pin for every post The pin is the same post with a different layout: big title, the cover photo, your site. One request gives both images: ```bash curl -X POST "https://shareglint.com/v1/images?wait=true" \ -H "Authorization: Bearer sk_live_..." \ -H "Content-Type: application/json" \ -d '{ "template": "blog-og", "sizes": ["og", "pinterest"], "modifications": { "title": "12 make-ahead lunches that survive a commute", "eyebrow": "Meal prep", "site": "northwind.kitchen", "photo": "https://cdn.example.com/lunches.jpg" } }' ``` The `og` file goes into the post's `og:image`, the `pinterest` file into the feed or the pin. Both are cached: the same values again are free. Templates built for pins' common subjects — `recipe`, `listicle` ("10 ways to…"), `product-og` — render in the same size. **The back catalogue.** Export your posts (title, category, cover image URL, slug) as CSV and send it as a batch with `"sizes": ["pinterest"]`: every post gets a pin, all in one ZIP, each URL returned with your `id`. Rows per batch by plan: Free 50, Starter 500, Pro 1,000, Scale 2,000, Business 5,000. The [CSV and Google Sheets guide](https://shareglint.com/en/guides/bulk-og-images-from-csv-google-sheets) walks through the columns. **On every new post.** A static site can call the API at build time; WordPress, Ghost or any CMS can call it from a publish webhook, or with an n8n or Make workflow ([n8n](https://shareglint.com/en/integrations/n8n), [Make](https://shareglint.com/en/integrations/make)). A signed URL works without a server call: `…/blog-og.png?title=…&size=pinterest&s=…` renders the first time it is fetched. ## Publishing automatically: RSS auto-publish The route with no API review is Pinterest's own **auto-publish from RSS** ([Pinterest Help](https://help.pinterest.com/en/business/article/auto-publish-pins-from-your-rss-feed), read 2026-11-06): - It needs a **business account** and a **claimed website**; every feed item must link to the claimed domain. RSS 2 and RSS 1 (RDF) are supported, Atom is not. - Pins are taken from the ``, `` and `` tags of each item; the pin's title and description come from the item's `` and `<description>`. - Each feed publishes to a board you choose; new items become pins within 24 hours, oldest first, up to 200 pins a day. So the integration is one tag: put the rendered pin's URL in each item's `<enclosure>` or `<media:content>` instead of the post's landscape cover. ```xml <item> <title>12 make-ahead lunches that survive a commute https://northwind.kitchen/make-ahead-lunches Lunches that hold up for five hours in a bag. ``` ## Publishing automatically: the API Pinterest's API v5 creates a pin with `POST /v5/pins`, taking the image as `media_source` with `source_type: "image_url"` and the rendered file's URL, plus `board_id`, `link`, `title` (up to 100 characters), `description` (up to 800) and `alt_text` (up to 500), with the `pins:write` and `boards:read` scopes ([Pinterest Developers](https://developers.pinterest.com/docs/api/v5/pins-create/)). Two things to know before building on it: - **Trial access.** A new app gets Trial access, and "all Pins and Boards created with Trial access are only visible to their creator as Sandbox entities". Publishing real pins needs **Standard access**, which Pinterest grants after reviewing a video of your app's flow ([access tiers](https://developers.pinterest.com/docs/key-concepts/access-tiers/)). - **Your own content.** Pinterest says the call "is intended solely for publishing new content created by the user" — pins of your own posts are exactly that. For a blog, RSS auto-publish is usually enough; the API is for apps that publish pins on behalf of many users. ## Rich Pins Article Rich Pins add the headline, description and author from your page to the pin. They read `og:title`, `og:description` and `og:type` set to `article` (or schema.org Article markup); Pinterest does not list `og:image` among the required tags, and pages with the tags turn into Rich Pins automatically, within up to 24 hours ([Pinterest Help](https://help.pinterest.com/en/business/article/rich-pins)). The pin's picture is still the one you publish — the 2:3 image from the template. ## Text on pins Pinterest's specifications set no limit on text in organic pin images; the "no more than 10 words" text overlay rule is for Showcase and Quiz ads only. Pins are seen small in a grid, so a short title in large type reads best, and long titles shrink to fit their box in the built-in templates. ## Cost One render per pin; with the `og` image it is two renders per post, and repeats are free. A 300-post back catalogue is 300 renders once. The Free plan's 100 renders a month carry a watermark. Starter is $9 a month for 2,000 renders ([pricing](https://shareglint.com/en/pricing)). ## What it does not do - It does not post to Pinterest or claim your website; Pinterest's RSS auto-publish or API does the posting. - It does not write pin titles, descriptions or keywords. - It does not generate photos: the image fields show the photos you give them. ## FAQ ### What size should a Pinterest pin be? Pinterest recommends a 2:3 aspect ratio, or 1000×1500 pixels, as PNG or JPEG; pins taller than 2:3 might get cut off in feeds. The pinterest size preset here is exactly that ratio. ### Can I publish pins automatically? Two ways. Pinterest's RSS auto-publish creates pins from the images in your feed for a business account with a claimed website, up to 200 a day, with no API review. Or the API's Create Pin call takes an image URL — but apps with Trial access create sandbox pins only their creator sees until Pinterest approves Standard access. ### Do I need og:image for Rich Pins? Article Rich Pins read og:title, og:description and og:type set to article from your page; Pinterest does not list og:image among the required tags. The pin image is the one you pin or the one in your RSS feed. ### Is there a limit on text on a pin image? Not for organic pins in Pinterest's specifications. The 10-word text overlay limit applies to Showcase and Quiz ads only. Short, large text still reads best in a feed.