---
name: linkedin-carousel-builder
description: Plans, writes and prepares a LinkedIn document post, the swipeable page-by-page file that the marketing world calls a carousel, starting from a topic, a draft or an existing article. It settles the format question first, because LinkedIn removed the native organic carousel post in December 2023 and the carousel ad is a separate paid object, then produces a page-by-page plan, the upload title, the accompanying post text brief, and a pre-publish verification pass built around the documented fact that an uploaded document cannot be edited after posting. This skill should be used when somebody asks for a LinkedIn carousel, when a post draft has outgrown a single idea and needs splitting into pages, or immediately before a document is exported or uploaded.
---

# LinkedIn carousel builder

## The claim this skill is built on

Two facts do most of the work here, and both are usually missing from carousel advice.

The first is that the object is misnamed. Three different things have carried the name carousel on LinkedIn, two of them are not what the reader means, and one of them no longer exists. Work on the wrong one and you either hunt for a button that was removed or follow a specification belonging to a paid advertising format.

The second is that a document post is a publishing operation, not a drafting one. LinkedIn documents that after posting you can edit the title and the description but not the document itself, and that changing the file means deleting the post and reposting, which discards every reaction, comment and share it had collected. Nothing else in the ordinary LinkedIn workflow behaves this way: a text post can be edited in place, a profile rewritten at will. Here, the moment you press post, one wrong digit is either permanent or expensive.

The obvious approach, writing ten pages of tips, exporting a PDF and uploading it, fails at both points. Everything below is arranged so the format question is settled before any pages exist, and so the last free moment to fix the file is used deliberately rather than passed through without noticing.

## Part one. Establish the object before anything else

Say the right word in your own notes and the rest falls into place. All three of the following were checked in August 2026.

**The native organic carousel post is gone.** This was a multi-image swipe format, distinct from the document post. LinkedIn began removing it on 14 December 2023, and existing carousel posts were deleted rather than merely closed to new creation. Profile videos and in-image links went in the same change. Never instruct anyone to create one. A template, guide or third-party tool promising a native LinkedIn carousel post is either describing something that no longer exists or describing a document post under the wrong name.

**The carousel ad still exists and is paid.** A Sponsored Content format, minimum 2 cards and maximum 10, with its own image specification and text limits. It is current and documented. It simply has nothing to do with an organic post, and its numbers do not transfer. Use the term only inside advertising work.

**The organic document post is what people mean.** You upload a file and LinkedIn renders it as a swipeable, page-by-page unit in the feed. This is what this skill builds, and LinkedIn does not call it a carousel anywhere in its documentation.

From here on the file says document post, and so should you, noting in passing that everyone calls it a carousel so nobody thinks you have misunderstood the request.

## Part two. The documented specification, and which parts change your work

Every item below comes from LinkedIn's own documentation, checked August 2026.

- **Accepted file types: PPT, PPTX, DOC, DOCX and PDF.** LinkedIn recommends converting to PDF for the highest quality upload, so the near-universal advice to export a PDF is not folklore, it is the platform's own recommendation.
- **Maximum file size 100 MB. Maximum 300 pages. A cap of one million words.** You will never approach these with a well-made document post. Their use is as a sanity check: a file anywhere near 100 MB has images embedded at print resolution.
- **One document per post.** You cannot attach several. A two-part idea is two posts or one longer document, not one post with two files.
- **The document must have a title, and the title is set at upload.**
- **After posting, the title and the description can be edited. The document cannot.** To change the file you delete the post and repost, losing all accumulated engagement. This is the most consequential line in the specification and Part eight exists because of it.
- **PDFs with multiple layers must be flattened or merged, and PDFs with differently sized pages must be fitted to a single page size.** Ignore either and the upload misbehaves.
- **Video and animation inside a document render as static images.** Anything that moves becomes one frame.
- **Viewers can download the document as a PDF, LinkedIn describes this as an accessibility requirement, and it cannot be switched off.** Everything you put in the file is downloadable by anyone who sees it.

**One thing the specification does not give you is a size.** LinkedIn publishes no pixel dimensions and no aspect ratio for organic document posts. The commonly published 1080 x 1350 and 1200 x 1500 figures are third-party convention. What LinkedIn does state officially, for the paid document ad, is that vertical, horizontal and square are all supported and that standard page sizes such as A4 and Letter are handled. So the safe instruction, and the only one this file will give, is: keep every page the same size, and prefer a vertical or square page because the feed column is narrow. Do not repeat a pixel figure as though the platform required it.

## Part three. Decision rule: document post or plain text post

Run this before a single page is designed.

**Branch A, build the document post,** when the content has a natural page-by-page order that a reader would lose in a paragraph. In practice that means one of: a sequence of steps where each depends on the one before, a comparison across more than two items, a before and after where seeing both matters, a set of examples that are only persuasive in aggregate, or numbers that need a shape rather than a sentence.

**Branch B, write a plain text post,** when the content is one idea, one argument or one story. A single opinion split across nine pages is a paragraph in costume, and the reader who swipes to page three to find the sentence they could have read in the feed is the reader who does not swipe again. This is also the branch when the value sits in the sentences themselves, because good prose survives being read and does not survive being chopped into headline fragments.

**Branch C, you cannot tell.** This is the common case and it has a mechanical answer, the flatten test. Write the whole thing as a plain text post first, inside LinkedIn's documented 3,000 character maximum, then try to cut it to roughly 1,300 characters without losing anything that matters. If it survives the cut, it was never a document post, so publish the text. If the cut forces you to delete a step, a threshold or a comparison the reader actually needs, the content has genuine page structure and you have just written the outline. Either way the test ends with a usable artifact, which is why it beats guessing.

One further consideration is not a branch but changes the plan. LinkedIn documents that a post can carry either a URL link or an image, but not both at once. A document occupies the media slot in the same way, so plan for any link to live in the first comment, and confirm the behaviour in the composer on the day, since LinkedIn's sentence names a URL and an image rather than naming documents explicitly. Text inside a rendered document is not clickable, so a URL on a page is something the reader has to retype.

## Part four. The page budget

Set the number of pages before writing them, because a budget forces the cutting that makes a document post readable.

Work to a spine of one cover page, a body of one idea per page, and one closing page. Below about four pages there is no swipe worth building and a single image or a text post does the job. Above about twelve, drop-off does the cutting for you and does it badly. LinkedIn's guidance for the paid document ad is to keep it under 10 pages, which is advertising guidance rather than organic guidance, but it is the only number the platform publishes near this question and it points the same way.

One idea per page is a hard rule, not a stylistic preference. The unit a reader consumes is the page, and two ideas on one page means the second is read while the thumb is already moving. If a page needs the word "and" in its headline to be true, it is two pages.

## Part five. Swipe economics

**Page one only has to sell page two.** It does not have to summarise the document, state the thesis or carry the best line. Its entire job is to make a swipe feel worth one second. The common misallocation is loading page one with the whole argument, which spoils the payoff and produces the most crowded page in the file.

**Number the spine.** Put a position marker on every page, such as 3 of 9. A reader who knows how much is left behaves differently from one who does not, and the marker also lets you check page order in the exported file at a glance, which Part eight uses.

**Land the payoff before the last page.** The final page is where the call to action lives, and a reader who has already received the value is a better prospect than one who feels it was withheld until they were asked for something. Put the substantive conclusion on the second to last page and let the last page ask.

## Part six. Legibility at the size the feed actually renders

A document post is read inside a narrow feed column, most often on a phone. It is designed on a laptop at close to full width. That gap is where most document posts fail, and it fails silently, because the version the author is looking at is perfectly readable.

The check works on any tool and either operating system: shrink the page on screen to about 8 cm, a little over 3 inches, roughly the width of a phone feed column, then read it at normal viewing distance. If you have to lean in, the type is too small. Do this before the pages are finished, because the fix is removing words rather than resizing them.

The following are working rules of this file rather than platform values, offered because they survive that check. Keep the smallest text on a page at no less than about one thirtieth of the page height. Keep a content page under roughly 40 words and a cover page under about 12. Prefer one image or chart per page over two. If a chart needs a legend to be understood, it needs a different chart or its own page.

## Part seven. Build and export

Any tool that exports a PDF works, and every option below runs on both Windows and macOS: PowerPoint, Google Slides, Canva, Figma, or LibreOffice Impress if the budget is zero. The tool matters far less than four export behaviours.

**Set one page size and use it for every page.** Mixed page sizes are a documented cause of upload misbehaviour and are easy to introduce by copying a slide in from another deck.

**Flatten.** LinkedIn requires layered PDFs to be flattened or merged. The reliable route in almost any application, on either operating system, is to print to PDF rather than use a save or export command that preserves structure. Vector artwork, transparency groups and comment layers are the usual culprits.

**Expand animations into pages.** Video and animation render as static images, and a slide built to reveal three bullets in sequence will either flatten to its final state or export as three near-identical pages, depending on the tool. Decide which you want and build it as separate pages.

**Embed the fonts, then open the exported file.** Font substitution happens at export, not in the design file, so the PDF is the only place to see it.

## Part eight. The pre-publish verification, which exists because the file is frozen

This is the step immutability forces, and the step people skip. Run it on the exported PDF, opened as a file, not on the design document. They are different objects, and the errors that matter live in the gap between them.

1. **Page count and order.** The intended number of pages, in the intended order. The position markers from Part five make this a five second check.
2. **Uniform page size.** Every page the same dimensions, no stray landscape page.
3. **Fonts.** Every page in the intended typeface, no substituted fallback, no missing glyphs.
4. **Numbers.** Read every figure aloud against the source. Transposed digits are the classic frozen error: invisible during proofreading, and they change the meaning completely.
5. **Text, read backwards.** Read the pages from last to first. It breaks the narrative flow that hides typos.
6. **Any URL, typed out and tested.** Readers may have to retype it, so it must be short and correct.
7. **The download question.** Assume a competitor, a client and a journalist all download this file, because they can and you cannot stop them. Remove anything confidential, any unlicensed image, any internal figure, then check the document properties and file name, which travel with the download.
8. **The title.** Set at upload and, unlike the pages, editable afterwards. Make it specific rather than clever, because it labels a file people may save.

Only after all eight does the file go near the upload dialogue.

## Part nine. The typo you find after publishing: the second decision rule

You will eventually find an error in a live document post. The rule is not "always repost", because deleting destroys the engagement the post has collected.

**If the error changes what a reader would do,** a wrong number, a wrong name, a step out of order, delete and repost, as early as possible while the engagement being discarded is still small.

**If the error is cosmetic,** a typo, a misaligned box, a stray placeholder in a footer, leave it. Post a correcting comment and use the one thing you are still allowed to change, the description, to carry the correction. Reposting for cosmetics trades real engagement for tidiness.

**If you cannot tell,** ask one question: would a reader who acts on that page do the wrong thing? If yes, it is material, so repost. If no, it is cosmetic. If the answer is genuinely unclear, treat it as material, because a wrong correction costs less than a wrong instruction sitting permanently in a file people download.

## Part ten. Worked example, compressed

**Brief.** An operations lead at a company selling warehouse stock-count software wants to publish the seven checks their team runs before a month-end count. Their request: "make it a carousel".

**Object.** Not a native carousel, which was removed in December 2023, and not a carousel ad, since this is organic. Build a document post.

**Format rule.** Branch C, cannot tell, so run the flatten test. Written as plain text it reaches about 2,400 characters, inside the documented 3,000 limit. Cutting towards 1,300 forces the removal of the numeric threshold on three of the seven checks, and those thresholds are the only part a reader could act on. The content has genuine page structure. Branch A confirmed, and the flatten draft is now the outline.

**Page budget.** Cover, seven checks at one per page, a summary page, and a closing page. Ten pages, inside the working ceiling and inside the documented 300.

**Swipe.** Page one carries a six-word cover line and nothing else, since its only job is the swipe to page two. Position markers on all ten. The full seven-check summary lands on page nine, and page ten asks.

**Legibility.** At an 8 cm width, check four is unreadable at 68 words. Cut to 21 and one supporting number. Two other pages lose a sub-heading each.

**Export.** Built in a slide tool, but two pages had been pasted in from an older landscape deck and are the wrong size. Refit all ten to one portrait size, then print to PDF to flatten the vector diagram on page six.

**Verification.** The eight-point pass on the exported file finds a substituted font on page three and, on page five, a threshold written as 30 days where the source says 3 days. Both fixed before upload. The file name still reads "deck-v4-FINAL-use-this-one", which would travel with every download, so it is renamed too.

**Verdict.** Publish as a ten-page portrait PDF, one page size, flattened, titled "Month-end stock count: the seven checks we run first", with the link to the full guide in the first comment rather than on a page, and the accompanying post text written separately so its first line survives the fold. The transposed 3 and 30 is the specific error that would otherwise have been permanent or cost the post.

## Failure modes

**The deleted format.** Someone follows a guide written before December 2023 and hunts for a native carousel option that is not in the composer. From outside it looks like confusion about the interface, or a third-party tool promising carousel posts that quietly produces a document post under a different name.

**The laptop-sized page.** Every page is comfortable at full width on a large monitor and illegible in the feed. Nobody reports it, because a reader who cannot read page two just scrolls on. The tell is normal impressions with almost no swipe-through.

**The ransom-note export.** Mixed page sizes or an unflattened layered PDF. Pages appear cropped, oddly scaled or in the wrong proportion after upload, and the author blames LinkedIn rather than the export.

**The frozen typo.** A wrong figure is found after publication, the post is deleted and reposted, and the second version starts from zero. The visible symptom is the same document appearing twice in one feed within a day.

**The withheld payoff.** Everything of value sits on the last page behind the call to action. Readers drop out around page four, and the comments are people asking for the thing the document was meant to give them.

**The leaked file.** Confidential figures, an unlicensed image or a client's internal data ships inside a file anyone can download and nobody can lock. It surfaces weeks later, out of context, with the original file name and document properties attached.

**The vanishing animation.** The deck was built with animated reveals or an embedded GIF. All of it renders static, so pages designed to appear in stages arrive as one crowded page or several near-identical ones, and the sequence stops making sense.

**The orphan link.** A URL is typed onto the final page in the expectation that people will click it. Text inside a rendered document is not clickable, so the reader has to retype a long address, and almost nobody does.

**The unnumbered stack.** No position markers anywhere. Readers cannot tell whether they are three pages from the end or thirteen, and drop-off rises for a reason no dashboard will ever name.

## What this skill does not do

- It does not design anything. It specifies what each page says and how much will fit; the layout, the typeface and the images are a design job, and a template in a tool like Canva or a designer with an hour beats it every time.
- It will not give you a pixel size. LinkedIn publishes no dimensions or aspect ratio for organic document posts, so the only honest instruction is one page size throughout, vertical or square. Treat every precise figure you have read elsewhere as convention, not specification.
- It does not write the accompanying post text, the comments underneath, the profile people land on, or any follow-up message. Those are separate jobs with separate constraints.
- It does not cover the paid formats. Carousel ads and document ads have their own specifications, limits and approval process, and this file stops at naming them so they are not confused with the organic object.
- It cannot inspect your file. Whether the PDF is flattened, whether fonts are embedded and whether page sizes match are checks you or a PDF tool must run; this file only tells you they are the checks that matter.
- It cannot confirm the specification is unchanged since August 2026. LinkedIn removed an entire organic format in December 2023, so verify the limits in the product before anything important depends on them.