How LinkedIn Carousels and PDFs Are Related

This is the single most confusing thing about LinkedIn carousels, and it confuses people because LinkedIn never really named the format. There is no button in the post box that says “carousel”. What people call a carousel is almost always a document post, and the file behind it is almost always a PDF.

Once that clicks, a lot of other questions answer themselves: which design tool to use, why the slides look like pages, why the text sometimes goes blurry, and why your links inside the file behave oddly. So it is worth going through slowly.

Is a LinkedIn carousel the same thing as a PDF?

In everyday use, yes. When someone says “I made a LinkedIn carousel”, what they did was:

• Design a set of slides in some tool — Canva, Figma, Google Slides, PowerPoint, Keynote, even a word processor.
• Export the whole thing as a single PDF file (PDF = Portable Document Format, a file type that keeps a fixed layout on every device).
• Attach that one file to a LinkedIn post using the document option.

LinkedIn takes it from there. It processes the file, works out how many pages it has, and shows it in the feed as a small viewer with arrows or a swipe area. Page one becomes slide one. There is no separate carousel object; the carousel is the document.

PDF is not the only file type LinkedIn accepts for a document post — presentation and word-processing files such as PPT, PPTX, DOC and DOCX also work, and LinkedIn converts them behind the scenes. But PDF is what most people export, because it is the one format that shows exactly the layout you designed, with your fonts baked in, on every phone and laptop.

How does LinkedIn turn a PDF into swipeable pages?

Practically, LinkedIn converts each page of your file into an image and stacks those images inside a small viewer that sits in the feed. That has a few real consequences you can plan around:

Your slide shape is decided by the page size of the file, not by LinkedIn. A PDF exported from a widescreen presentation gives you wide, letterbox slides. A PDF exported at a square or tall page size gives you square or tall slides. Whatever page dimensions you set in the design tool are what the feed shows. A sibling article in this cluster covers sizing in detail.

The file is flattened. Anything that only works in a live document — slide transitions, animations, embedded video, comments — is gone. What survives is what a printed page would show.

Text becomes part of the picture. This is the one that catches people out. Because pages are rendered visually, the words on your slides are not selectable text in the feed. That matters for readability on a small screen and it matters for accessibility — screen readers cannot read text that has become an image. Other articles in this cluster go into phone readability and accessibility properly; the point here is that it is a direct result of the PDF-to-image step.

Links inside the file are unreliable. A clickable link you added in your design tool may not survive as a clickable link in the feed viewer. Creators widely report this, and the safe habit is to put any link you actually want people to follow in the post caption or the first comment instead of relying on it inside the slides.

What is a multi-image post, and how is it different?

A multi-image post is the other swipeable format, and it is genuinely different under the bonnet. Instead of one document, you attach several separate image files — JPEGs or PNGs — to one post, and the reader swipes between them.

Both formats give the reader a swipe. That is why they get muddled. But they behave differently:

• What you upload. One file versus several files. A document post is a single PDF; a multi-image post is a set of images you export one per slide.
• How many slides. A document can run to a lot of pages — more than anyone will actually swipe through. Multi-image posts hold a small handful. Kalovio supports 2 to 9 images in one post. Check LinkedIn’s own help centre for its current limits rather than trusting a number from a blog, including this one.
• How it looks in the feed. A document post shows a document-style viewer, usually with a page counter. A multi-image post shows the images more like a photo gallery, and with more than a few images LinkedIn may show some as a grid preview rather than one at a time.
• What it is good for. A document suits a designed, ordered sequence where slide three only makes sense after slide two. Multi-image suits a set of related pictures — event photos, product angles, before-and-after shots — where order matters less.

Carousel, multi-image, carousel ad: what is the difference?

The third column is the one to keep separate in your head. Carousel ads are a paid LinkedIn Ads format, bought and built inside Campaign Manager, LinkedIn’s advertising tool. They are made of cards, each of which can point at its own destination, and they are billed like any other ad. They are not what you get when you upload a PDF to your own feed, and advice written about carousel ads — card counts, headline lengths, bidding — does not transfer to organic document posts. If an article mixes the two, treat the rest of it carefully.

So which one should I use?

A short rule that holds up most of the time:

• Use a document post when you have made something — a designed explainer, a checklist, a framework, a walk-through where each slide builds on the last. This is the classic carousel.
• Use a multi-image post when you have several real pictures and no strict order — photos from a conference, three views of a product, a couple of screenshots.
• Use a single image when one picture says it. Another article in this cluster compares that choice directly.

One practical tie-breaker: a document post is a single file you can update, version and reuse elsewhere. If you are going to send the same slides to a client or attach them to an email later, building them as a PDF from the start saves you a step.

How do I actually make and publish one?

The making part is deliberately boring, and that is good news — you do not need a specialist tool.

1. Pick a page size and stick to it. Set it once in your design tool so every slide matches. Mixed page sizes in one PDF look broken in the viewer.
2. Design the slides. Big type, one idea per slide, plenty of empty space. Assume a thumb-sized screen.
3. Export as PDF. One file, pages in the right order. Open it once and swipe through before uploading — the export is where fonts go missing and page order surprises you.
4. Write the caption separately. The caption is ordinary post text and carries any link you want clicked.
5. Publish. Attach the document in LinkedIn’s post box, or publish it through a tool.

On that last step: if you already write your posts by chatting with an AI assistant, you can hand it the PDF instead of switching apps. Kalovio connects Claude or ChatGPT to your own LinkedIn account through LinkedIn’s official interface, so you can upload a PDF and publish it as a document post from the chat, caption and all. Two things to know honestly: document posts go through LinkedIn’s newer versioned interface, which is not switched on for every self-serve app, so try it on your own account and Kalovio will report clearly if LinkedIn refuses; and document posts publish immediately — they cannot be scheduled yet, unlike text and image posts.

What should I check before uploading?

• Page order. Open the exported PDF and swipe through it yourself first.
• Fonts. If your tool offers “embed fonts” on export, use it. Missing fonts get substituted and the layout shifts.
• File size and page count. LinkedIn has limits on both, and they change. Check LinkedIn’s help centre rather than a number you read somewhere. Kalovio’s own upload cap is 20 MB per file.
• The first page. It is the thumbnail people see before they swipe, so it has to earn the swipe on its own.
• Your link. Put it in the caption or a comment, not inside the PDF.

Get those five right and the format itself stops being the hard part. What is left is the writing, which is where a carousel is won or lost anyway.