LinkedIn PDF Document Carousel Generator
On LinkedIn, attaching multiple PNG/JPG images creates an awkward static photo collage—not a swipeable carousel. True swipeable LinkedIn carousels are multi-page 4:5 portrait PDF documents. Always export and attach the rendered deck as a single PDF document.
The One Rule: Every Page Shows Concrete Visual Evidence
Never ship a page that is only words, bullets, or a colored bar on a plain background. Why: LinkedIn readers swipe past text-only document pages because they look like generic AI quote cards; a real dashboard, product UI, logo, or chart is the proof a B2B reader trusts.
Walk this tree for each slide:
What is this slide about?
├── A product, site, repo, pricing page, report, doc, or source article with a public URL
│ → screenshotUrl = that URL. visual: the live page framed in a browser or laptop window,
│ with 1–2 annotated callouts on the exact element that proves the claim.
├── A named company, tool, or platform (HubSpot, Salesforce, Stripe, Notion, Google...)
│ → visual names its logo/wordmark, app icon, and brand palette explicitly.
│ imageUrl = a public logo or press image URL when you have one.
├── A metric, benchmark, or before/after result
│ → chart with labeled axes, units, a source line, and a callout on the key number;
│ company logos on the series. Or a 2-column before/after with a screenshot on each side.
├── A process, framework, or architecture
│ → diagram whose nodes carry the real product icons and short labels.
├── A real person (founder, executive, public figure, historical portrait)
│ → imageUrl = their Wikimedia Commons or press-room portrait, on this slide only.
└── A people, team, or context beat
→ imageUrl of a real photo; unsplashQuery only for a real place or physical environment
(concrete noun phrase, ≤120 chars); otherwise a photorealistic studio-lit hero object.
Step 1. Structure the B2B Narrative Arc
What is the source material?
├── Case Study / Experiment / Post-Mortem → 8–12 slides (Hook → Baseline → What Changed → Proof Numbers → Playbook → Summary Card)
├── Tactical Playbook / Framework (N steps) → N + 2 slides (Cover + N steps + Summary Close), minimum 6, capped at 15
└── Quick Contrarian Point / Before-vs-After → 6–7 slides
- Aspect ratio: Always
4:5. Why: 4:5 fills the phone width at 1.25× height, whereas 16:9 renders at 0.56× height (2.22× shorter) with letterbox bars.
- Never ship fewer than 6 slides or more than 15 slides unless the user explicitly demands an exact count. Why: under 6 slides loses the swipe dwell-time signal that drives LinkedIn feed distribution; past 15 slides mobile completion drops sharply.
Step 2. Build the Slide-by-Slide Beats
- Slide 1 — Cover (Stop the Feed):
- Headline under 9 words naming a concrete metric, mistake, or outcome (
"We audited 420 SaaS trials. 81% of ad spend leaked here." — never "5 Tips for Better SaaS Marketing").
- A hero visual behind or beside it: the product screenshot, the key chart, or the brands involved.
- Right-edge directional cue (
"Swipe →" or "1 / 9") so mobile readers register it as a document carousel immediately.
- Slide 2 — Context / The Conventional Trap: why the standard playbook fails, backed by 1 concrete observation or stat and a screenshot or chart of it.
- Slides 3 to N−1 — One Mechanism or Proof Per Slide:
- Max 32 words per slide. LinkedIn readers swipe on phones at arm's length; body copy smaller than
24pt equivalent gets skipped.
- No two consecutive slides share a layout: framed screenshot with callouts → labeled chart → before/after split → icon architecture diagram → real example.
- Keep every real figure, company name, and benchmark from the user's source verbatim. Never invent statistics.
- Slide N — The Cheat-Sheet Summary: recap all takeaways on one card (5-row checklist or decision matrix) with the tool logos next to each row. Why: saves and shares on the final summary slide carry far more weight than a generic
"Follow me for more!" end card.
Step 3. Gather Visual Assets (Mandatory Before Rendering)
Why: the renderer can only show what you hand it; a deck planned without URLs comes back as text cards.
- List every entity and source in the deck: products, companies, reports, dashboards, articles.
- Find a public URL for each: homepage, pricing page, public report, docs page, GitHub repo, the primary article. Open it to confirm it loads without a login or cookie wall. Why: a screenshot of a sign-in page is worse than no screenshot.
- Assign assets:
websiteUrls (deck-level, max 6): the most important pages; GenPPT captures live browser screenshots of them.
slides[].screenshotUrl: the exact page that slide discusses.
slides[].imageUrl: a direct public image URL (logo, chart, photo) you have actually seen. Never guess or construct an image URL. Why: a dead URL renders as an empty frame. If you have no URL, name the logo in visual.
- Real people:
slides[].imageUrl only. For a founder, executive, public figure, or historical portrait, pass a real Wikimedia Commons (https://upload.wikimedia.org/...) or official press-room portrait URL on that one slide. Never ask for a real person's face from text alone. Why: given a real portrait, GenPPT renders a close photographic likeness with no safety refusals; the likeness comes from the image, not the name.
slides[].unsplashQuery: only for real places, architecture, landscapes, cityscapes, or generic physical environments ("kanazawa higashi chaya wooden street", "hyperscale server room aisle"). Omit it on historical scenes, object inventions or metaphors, 3D book or product renders, and data diagrams. Why: stock search returns literal modern mismatches (formal leather dress shoes for a 1971 waffle-sole track flat); with no stock photo, GenPPT illustrates the metaphor, 3D book, or chart natively.
referenceImageUrls (max 20): deck-wide brand logos and marks only. Never put a person's portrait or a slide-specific screenshot here. Why: deck-level references reach every slide, so one slide's face bleeds onto its neighbors.
- Asset ledger check: every slide has a
screenshotUrl, imageUrl, or unsplashQuery, or its visual names a specific logo, product, chart, or object. Rewrite any slide that has none.
Step 4. Write Concrete visual Prompts and artDirection
visual formula (every slide): [backdrop] + [hero asset and where it sits] + [logos/icons and placement] + [callout: what it points at] + [headline position].
"Warm bone paper: framed laptop screenshot of the live pricing page filling the lower 60%, cobalt circle callout on the 'Enterprise' column with label '3× in 12 months', HubSpot and Salesforce logos top-right, headline top-left."
Banned visual values: "stat card", "timeline bar", "3-bullet summary card", "icon grid", "clean layout", "text slide". Why: vague labels give the renderer nothing to draw except text on a box.
artDirection:
- Palette from the subject's brand first. When the post is about a company or product, use its official palette and logo. Otherwise: warm bone (
#F7F6F2) with deep ink (#111827) and one accent (#1D4ED8 cobalt, #0F766E teal, or #EA580C vermilion), or deep slate (#0F172A) with crisp white type when the subject is a dark-UI product.
- Safe margins: keep
56px clear on all four edges. Why: LinkedIn overlays a page-counter pill at top-right and pagination controls along the bottom.
Short, clean copy: a headline and at most one short sentence per slide. No em dashes, no AI-slop phrasing ("isn't X, it's Y", "Hits Harder", "The secret is..."), and no number repeated twice on one slide.
Step 5. Render via MCP
- Call
genppt_create_slideshow (https://genppt.com/mcp) with:
aspectRatio: "4:5", title, thesis
slides: { title, purpose, visual, screenshotUrl?, imageUrl?, unsplashQuery? } objects
websiteUrls, referenceImageUrls, attachmentUrls (supplied PDFs and reports) from Step 3
artDirection from Step 4, autoRender: true
- If the connected server's schema does not list
websiteUrls or the per-slide asset fields, put every URL except portraits in referenceImageUrls / attachmentUrls and name each one in the matching slide's visual.
- Call
genppt_get_deck with { deckId, waitSeconds: 45 } until phase === "ready".
Step 6. Visual QA Gate (Mandatory Before Export)
Open every slideImageUrls image and look at it. A slide fails if it:
- shows text on a plain background with no screenshot, logo, chart, photo, or object;
- is missing the screenshot or logo you planned, shows it illegibly, or has a cookie-consent or login modal covering the capture;
- shows a stock object from
unsplashQuery that contradicts the subject (a modern object on a historical or metaphor slide);
- shows a person's face on a slide other than their own;
- has a cut-off headline, text within
56px of an edge, crop bleed at a border, or any figure that differs from the source.
Fix every failing slide with genppt_revise_slides: { deckId, revisions: [{ slideNumber, instructions, screenshotUrl?, imageUrl?, placeImages? }] }.
- Missing visual → add
screenshotUrl or imageUrl plus instructions describing the composition.
- Screenshot or logo redrawn wrong →
placeImages: [{ screenshotUrl or url, x, y, width, height }] with 0..1 coordinates (e.g. { x: 0.07, y: 0.35, width: 0.86, height: 0.5 }). Why: placeImages pastes the real capture untouched instead of letting the model redraw UI text.
- Cookie-consent or login modal over a capture → swap
screenshotUrl for a cleaner page with the same fact (docs, blog post, status page), or placeImages a clean capture.
- Mismatched stock object → revise with
instructions naming the exact object to illustrate and no stock photo. Why: GenPPT draws historical objects and metaphors correctly once stock search is out of the way.
- A face on the wrong slide → revise that slide with instructions to remove the person; keep the portrait on its own slide's
imageUrl.
- Crop bleed at a border → revise with instructions to keep every element inside the slide edges.
Re-check after genppt_get_deck. Max 2 revision rounds; if a slide still fails, cut it or tell the user which slide failed and why.
Then the mandatory PDF step: genppt_export_deck with { deckId, format: "pdf" } for the single multi-page PDF (downloadUrl). Never attach loose PNG URLs to a LinkedIn post when the user asked for a carousel.
Step 7. Write the Companion Commentary & Stage/Publish
LinkedIn truncates post commentary around 210 characters ("...see more").
- Lines 1–2 (under 190 chars): the sharpest finding or number from the deck—never
"I put together a quick carousel on...".
- Body (3–6 short lines): 3 scannable takeaways in plain operator prose. Zero AI clichés (
"delve", "game-changer", "unlock", "thrilled to share"). Put any external link in the post body on personal profiles whose API scopes lack comment permissions, or in the first comment on company pages that support it.
- Document title: max 58 characters. Why: LinkedIn shows the PDF title bar above Slide 1 and truncates longer titles on mobile.
Then walk the publishing tree:
Is a social publishing MCP or LinkedIn integration connected?
├── Yes → Attach the exported PDF `downloadUrl` as a LinkedIn document attachment with your <=58-char title:
│ ├── Connector flags the account as review-required, or it is a personal executive profile (default)
│ │ → Save as a draft only, display the exact commentary + Slide 1..N previews + PDF link, and wait for explicit approval before publishing.
│ └── Company page with autonomous publishing explicitly enabled
│ → Publish live and return the post URL.
└── No → Display the slide previews inline, provide `downloadUrl` for the multi-page PDF + `studioUrl`, and output the ready-to-paste LinkedIn post copy.
1---2name: linkedin-carousel-generator3description: Generate native LinkedIn swipeable PDF document carousels via MCP, with live product screenshots, brand logos, labeled charts, and real photos on every page, and stage or publish them with high-retention B2B post copy. Use when the user asks for a LinkedIn carousel, LinkedIn PDF slideshow, B2B slide deck for LinkedIn, or turning a case study, report, or article into a LinkedIn document post.4metadata:5 source: https://skillmd.com/skills/illyism/linkedin-carousel-generator6---78# LinkedIn PDF Document Carousel Generator910On LinkedIn, attaching multiple PNG/JPG images creates an awkward static photo collage—**not** a swipeable carousel. True swipeable LinkedIn carousels are **multi-page `4:5` portrait PDF documents**. Always export and attach the rendered deck as a single **PDF document**.1112## The One Rule: Every Page Shows Concrete Visual Evidence1314**Never ship a page that is only words, bullets, or a colored bar on a plain background.** *Why*: LinkedIn readers swipe past text-only document pages because they look like generic AI quote cards; a real dashboard, product UI, logo, or chart is the proof a B2B reader trusts.1516Walk this tree for each slide:1718```19What is this slide about?20├── A product, site, repo, pricing page, report, doc, or source article with a public URL21│ → screenshotUrl = that URL. visual: the live page framed in a browser or laptop window,22│ with 1–2 annotated callouts on the exact element that proves the claim.23├── A named company, tool, or platform (HubSpot, Salesforce, Stripe, Notion, Google...)24│ → visual names its logo/wordmark, app icon, and brand palette explicitly.25│ imageUrl = a public logo or press image URL when you have one.26├── A metric, benchmark, or before/after result27│ → chart with labeled axes, units, a source line, and a callout on the key number;28│ company logos on the series. Or a 2-column before/after with a screenshot on each side.29├── A process, framework, or architecture30│ → diagram whose nodes carry the real product icons and short labels.31├── A real person (founder, executive, public figure, historical portrait)32│ → imageUrl = their Wikimedia Commons or press-room portrait, on this slide only.33└── A people, team, or context beat34 → imageUrl of a real photo; unsplashQuery only for a real place or physical environment35 (concrete noun phrase, ≤120 chars); otherwise a photorealistic studio-lit hero object.36```3738## Step 1. Structure the B2B Narrative Arc3940```41What is the source material?42├── Case Study / Experiment / Post-Mortem → 8–12 slides (Hook → Baseline → What Changed → Proof Numbers → Playbook → Summary Card)43├── Tactical Playbook / Framework (N steps) → N + 2 slides (Cover + N steps + Summary Close), minimum 6, capped at 1544└── Quick Contrarian Point / Before-vs-After → 6–7 slides45```4647- **Aspect ratio: Always `4:5`.** *Why*: `4:5` fills the phone width at `1.25×` height, whereas `16:9` renders at `0.56×` height (`2.22×` shorter) with letterbox bars.48- **Never ship fewer than 6 slides or more than 15 slides** unless the user explicitly demands an exact count. *Why*: under 6 slides loses the swipe dwell-time signal that drives LinkedIn feed distribution; past 15 slides mobile completion drops sharply.4950## Step 2. Build the Slide-by-Slide Beats51521. **Slide 1 — Cover (Stop the Feed):**53 - Headline under **9 words** naming a concrete metric, mistake, or outcome (`"We audited 420 SaaS trials. 81% of ad spend leaked here."` — never `"5 Tips for Better SaaS Marketing"`).54 - A hero visual behind or beside it: the product screenshot, the key chart, or the brands involved.55 - Right-edge directional cue (`"Swipe →"` or `"1 / 9"`) so mobile readers register it as a document carousel immediately.562. **Slide 2 — Context / The Conventional Trap:** why the standard playbook fails, backed by 1 concrete observation or stat and a screenshot or chart of it.573. **Slides 3 to N−1 — One Mechanism or Proof Per Slide:**58 - **Max 32 words per slide.** LinkedIn readers swipe on phones at arm's length; body copy smaller than `24pt` equivalent gets skipped.59 - No two consecutive slides share a layout: framed screenshot with callouts → labeled chart → before/after split → icon architecture diagram → real example.60 - Keep every real figure, company name, and benchmark from the user's source verbatim. Never invent statistics.614. **Slide N — The Cheat-Sheet Summary:** recap all takeaways on **one card** (5-row checklist or decision matrix) with the tool logos next to each row. *Why*: saves and shares on the final summary slide carry far more weight than a generic `"Follow me for more!"` end card.6263## Step 3. Gather Visual Assets (Mandatory Before Rendering)6465*Why*: the renderer can only show what you hand it; a deck planned without URLs comes back as text cards.66671. **List every entity and source** in the deck: products, companies, reports, dashboards, articles.682. **Find a public URL for each**: homepage, pricing page, public report, docs page, GitHub repo, the primary article. Open it to confirm it loads without a login or cookie wall. *Why*: a screenshot of a sign-in page is worse than no screenshot.693. **Assign assets:**70 - `websiteUrls` (deck-level, max 6): the most important pages; GenPPT captures live browser screenshots of them.71 - `slides[].screenshotUrl`: the exact page that slide discusses.72 - `slides[].imageUrl`: a direct public image URL (logo, chart, photo) you have actually seen. **Never guess or construct an image URL.** *Why*: a dead URL renders as an empty frame. If you have no URL, name the logo in `visual`.73 - **Real people: `slides[].imageUrl` only.** For a founder, executive, public figure, or historical portrait, pass a real Wikimedia Commons (`https://upload.wikimedia.org/...`) or official press-room portrait URL on that one slide. Never ask for a real person's face from text alone. *Why*: given a real portrait, GenPPT renders a close photographic likeness with no safety refusals; the likeness comes from the image, not the name.74 - `slides[].unsplashQuery`: **only** for real places, architecture, landscapes, cityscapes, or generic physical environments (`"kanazawa higashi chaya wooden street"`, `"hyperscale server room aisle"`). Omit it on historical scenes, object inventions or metaphors, 3D book or product renders, and data diagrams. *Why*: stock search returns literal modern mismatches (formal leather dress shoes for a 1971 waffle-sole track flat); with no stock photo, GenPPT illustrates the metaphor, 3D book, or chart natively.75 - `referenceImageUrls` (max 20): deck-wide brand logos and marks only. Never put a person's portrait or a slide-specific screenshot here. *Why*: deck-level references reach every slide, so one slide's face bleeds onto its neighbors.764. **Asset ledger check:** every slide has a `screenshotUrl`, `imageUrl`, or `unsplashQuery`, or its `visual` names a specific logo, product, chart, or object. Rewrite any slide that has none.7778## Step 4. Write Concrete `visual` Prompts and `artDirection`7980**`visual` formula** (every slide): `[backdrop] + [hero asset and where it sits] + [logos/icons and placement] + [callout: what it points at] + [headline position]`.8182> *"Warm bone paper: framed laptop screenshot of the live pricing page filling the lower 60%, cobalt circle callout on the 'Enterprise' column with label '3× in 12 months', HubSpot and Salesforce logos top-right, headline top-left."*8384**Banned `visual` values**: `"stat card"`, `"timeline bar"`, `"3-bullet summary card"`, `"icon grid"`, `"clean layout"`, `"text slide"`. *Why*: vague labels give the renderer nothing to draw except text on a box.8586**`artDirection`:**87- **Palette from the subject's brand first.** When the post is about a company or product, use its official palette and logo. Otherwise: warm bone (`#F7F6F2`) with deep ink (`#111827`) and one accent (`#1D4ED8` cobalt, `#0F766E` teal, or `#EA580C` vermilion), or deep slate (`#0F172A`) with crisp white type when the subject is a dark-UI product.88- **Safe margins:** keep `56px` clear on all four edges. *Why*: LinkedIn overlays a page-counter pill at top-right and pagination controls along the bottom.8990**Short, clean copy:** a headline and at most one short sentence per slide. No em dashes, no AI-slop phrasing (`"isn't X, it's Y"`, `"Hits Harder"`, `"The secret is..."`), and no number repeated twice on one slide.9192## Step 5. Render via MCP93941. Call `genppt_create_slideshow` (`https://genppt.com/mcp`) with:95 - `aspectRatio: "4:5"`, `title`, `thesis`96 - `slides`: `{ title, purpose, visual, screenshotUrl?, imageUrl?, unsplashQuery? }` objects97 - `websiteUrls`, `referenceImageUrls`, `attachmentUrls` (supplied PDFs and reports) from Step 398 - `artDirection` from Step 4, `autoRender: true`99 - If the connected server's schema does not list `websiteUrls` or the per-slide asset fields, put every URL except portraits in `referenceImageUrls` / `attachmentUrls` and name each one in the matching slide's `visual`.1002. Call `genppt_get_deck` with `{ deckId, waitSeconds: 45 }` until `phase === "ready"`.101102## Step 6. Visual QA Gate (Mandatory Before Export)103104Open every `slideImageUrls` image and look at it. A slide fails if it:105- shows text on a plain background with no screenshot, logo, chart, photo, or object;106- is missing the screenshot or logo you planned, shows it illegibly, or has a cookie-consent or login modal covering the capture;107- shows a stock object from `unsplashQuery` that contradicts the subject (a modern object on a historical or metaphor slide);108- shows a person's face on a slide other than their own;109- has a cut-off headline, text within `56px` of an edge, crop bleed at a border, or any figure that differs from the source.110111Fix every failing slide with `genppt_revise_slides`: `{ deckId, revisions: [{ slideNumber, instructions, screenshotUrl?, imageUrl?, placeImages? }] }`.112- Missing visual → add `screenshotUrl` or `imageUrl` plus instructions describing the composition.113- Screenshot or logo redrawn wrong → `placeImages: [{ screenshotUrl or url, x, y, width, height }]` with `0..1` coordinates (e.g. `{ x: 0.07, y: 0.35, width: 0.86, height: 0.5 }`). *Why*: `placeImages` pastes the real capture untouched instead of letting the model redraw UI text.114- Cookie-consent or login modal over a capture → swap `screenshotUrl` for a cleaner page with the same fact (docs, blog post, status page), or `placeImages` a clean capture.115- Mismatched stock object → revise with `instructions` naming the exact object to illustrate and no stock photo. *Why*: GenPPT draws historical objects and metaphors correctly once stock search is out of the way.116- A face on the wrong slide → revise that slide with instructions to remove the person; keep the portrait on its own slide's `imageUrl`.117- Crop bleed at a border → revise with instructions to keep every element inside the slide edges.118119Re-check after `genppt_get_deck`. Max 2 revision rounds; if a slide still fails, cut it or tell the user which slide failed and why.120121**Then the mandatory PDF step:** `genppt_export_deck` with `{ deckId, format: "pdf" }` for the single multi-page PDF (`downloadUrl`). **Never** attach loose PNG URLs to a LinkedIn post when the user asked for a carousel.122123## Step 7. Write the Companion Commentary & Stage/Publish124125LinkedIn truncates post commentary around **210 characters** (`"...see more"`).126- **Lines 1–2 (under 190 chars):** the sharpest finding or number from the deck—never `"I put together a quick carousel on..."`.127- **Body (3–6 short lines):** 3 scannable takeaways in plain operator prose. Zero AI clichés (`"delve"`, `"game-changer"`, `"unlock"`, `"thrilled to share"`). Put any external link in the post body on personal profiles whose API scopes lack comment permissions, or in the first comment on company pages that support it.128- **Document title:** max **58 characters**. *Why*: LinkedIn shows the PDF title bar above Slide 1 and truncates longer titles on mobile.129130Then walk the publishing tree:131132```133Is a social publishing MCP or LinkedIn integration connected?134├── Yes → Attach the exported PDF `downloadUrl` as a LinkedIn document attachment with your <=58-char title:135│ ├── Connector flags the account as review-required, or it is a personal executive profile (default)136│ │ → Save as a draft only, display the exact commentary + Slide 1..N previews + PDF link, and wait for explicit approval before publishing.137│ └── Company page with autonomous publishing explicitly enabled138│ → Publish live and return the post URL.139└── No → Display the slide previews inline, provide `downloadUrl` for the multi-page PDF + `studioUrl`, and output the ready-to-paste LinkedIn post copy.140```