LinkedIn Carousel Post Design Specs for Mobile Readers

A LinkedIn carousel built for mobile readers needs more than the right dimensions. Its canvas, PDF export, padding, type and slide count must work together so readers can see the point and keep swiping. The central rule is simple. Design for the phone-sized version people actually read.

Why LinkedIn carousels are now a PDF format, and what that means for design

Since December 2023, organic LinkedIn carousels have been created by uploading a multi-page document, usually a PDF, which LinkedIn turns into swipeable slides. LinkedIn no longer has the native carousel post format for organic content. What looks like a sequence of social images is therefore a document post underneath.

That distinction changes the production work. PDF-specific decisions, including font embedding, link preservation and compression, affect what readers receive. A correctly sized page can still arrive with substituted type or blurry text if the export is wrong.

How LinkedIn renders carousels differently on mobile versus desktop

The same PDF has to serve two different reading settings. Desktop viewers tend to read more carefully and spend longer on data-heavy slides. Mobile readers are swiping through a feed and need quicker visual cues to understand what a slide offers. A layout that works when someone takes time to read it on a monitor can be too much work to read on a phone.

LinkedIn places a semi-transparent overlay at the bottom of mobile slides showing the page count and sometimes a next arrow. That strip occupies space a designer might otherwise give to a closing line or call to action. It belongs in the layout calculation before any text is placed there.

Desktop has its own controls, so it still needs a preview check. The priority, however, is to design for mobile first and then verify that the desktop view does not break. Reversing that order makes the smallest reading surface carry decisions made for the largest one. The phone is not a tiny conference-room screen, and its reader has not agreed to sit through the presentation.

Choosing between square and portrait — and why landscape is not a real option

The useful choice is between a square and a portrait slide. Square is safer across screens, while portrait is more aggressive about claiming mobile space. The decision depends on the audience and on whether the content needs predictable framing or a taller storytelling canvas.

The square 1:1 format renders predictably across screen sizes without cropping or letterboxing. That makes it the safer default when the split between desktop and mobile readers is unknown. For an audience that moves between devices, that predictability is a practical advantage.

The 4:5 portrait format occupies roughly 25% more vertical space than a square post. On mobile, that extra height fills the majority of the viewport and pushes competing feed content further down. Portrait is therefore the stronger choice when the audience is primarily mobile and the content is storytelling-led. It gives the current slide more room to hold attention, but the extra room is not permission to add another paragraph.

Landscape 16:9 may be technically accepted, but on mobile it leaves significant white space above and below the slide, turning the content into a thin strip in the feed. Between the two defensible options, choose square for safer cross-screen rendering or portrait for a more prominent mobile story.

File format, file size, and what happens when you get either wrong

Once the canvas is settled, the next question is whether the file will preserve it and load cleanly. PDF is the recommended format because it preserves embedded fonts and maintains the intended layout. LinkedIn also accepts PowerPoint and Word files, but converts them server-side into a rendered PDF carousel. That conversion can introduce font substitutions or layout shifts, so the original document and the published result may not match.

The official upload limit allows much larger files than the practical target of under 3 MB for a lightweight carousel. Passing the upload limit is not the same as being optimized for a reader waiting to swipe.

The simplest compression work happens before export. Use vector shapes and text rather than raster images wherever possible, compress background images before importing them, and limit heavy gradients that inflate the file. These choices keep the document lighter without turning the text itself into an image. Exporting slides as JPG or PNG and then placing those images into a PDF creates the opposite problem. LinkedIn recompresses an already-compressed image, which can leave text blurry and visuals muddy.

PDF supports clickable links, and those links need to be embedded in the PDF editor before export. LinkedIn does not retain clickable PDF hyperlinks in the feed, so support inside the document should not be mistaken for a tappable feed slide. File fidelity and feed behavior are related, but they are not interchangeable.

Safe zones, padding, and the overlay that will crop your CTA

The bottom overlay can obscure the very line meant to turn reading into action. On a phone, it appears as a partially transparent strip over the lower part of the slide, where a closing sentence or CTA can easily land. Transparency does not make that area safe for text. A reader should not have to decipher a call to action through the page counter.

Treat the page counter, navigation arrow and edge clipping as space unavailable to anything that must be read. Keep the content that must be read inside the 80 px padding boundary, away from the edges. The same 80 px rule applies to 1080×1350 portrait slides. A taller canvas changes the available space, but it does not remove the need for a protected area.

The dimensions give the size of the page, while safe zones show where the important content belongs inside it. Text can therefore be cut off or covered even when the file measures exactly what it should. Changing the canvas dimensions will not fix a CTA under an interface element, just as a larger envelope will not improve handwriting.

Before publishing, review the exported PDF in a desktop preview and on a mobile device screen. The export matters because the design-tool view is not the finished document. The phone check matters because looking at the full canvas can hide flaws that are visible at feed size. What looks comfortably spaced in Figma can still clip or become obscured in LinkedIn.

Typography minimums that keep text legible on a phone screen

Typography needs to work on both the full-size design canvas and the smaller slide shown on a phone. A font size on that canvas is not a promise about its size on the reader’s screen. Text that seems generous while designing can become functionally unreadable once the whole slide is reduced. The useful minimum is therefore the size that remains legible in the mobile view.

Use one idea per slide and no more than a short block of body text. Those limits leave room for heading-size type, readable supporting text and the required padding. When too much copy is squeezed onto a page, shrinking the type may make it fit while destroying the reading experience. The words are technically present, much like the terms and conditions nobody invited to the party.

Contrast must support that legibility. Use a contrast ratio of at least 4.5:1 between text and background so that the words do not disappear into the design. Low-contrast slides are hard for readers in general and also cause accessibility problems. Even a larger font can be hard to read when its edges blend into the background.

Use embedded fonts only, because LinkedIn may substitute a system font when the original is not embedded in the PDF. That substitution can disrupt the layout as well as the relationship between headline and body text. The cover carries the highest stakes, since its headline must read in under two seconds at phone size to stop the scroll. If it needs close inspection, it has already asked too much.

Slide count and how the algorithm measures carousel engagement

Slide count affects both the reader’s willingness to begin and the post’s ability to earn distribution. LinkedIn rewards dwell time and swipe-through signals, so the sequence is not simply a matter of visual taste. Each swipe registers as engagement and adds time spent with the carousel. A reader who completes it sends a stronger distribution signal than one who leaves at slide three.

The suggested ranges of 3–10, 6–10 and 8–12 slides converge around a middle range. Aim for the mid-single-digits to low-double-digits, with completion rate as the true measure. Shorter carousels of 3 to 4 slides can underperform, while longer ones can exhaust the reader before the finish. More pages create more chances to swipe, but also more chances to stop.

The visible page count makes that trade-off apparent before the first swipe. Readers can see the commitment being requested, and a high count can discourage them from starting. A deck is therefore asking for time as well as attention.

The steepest drop-off is between slide one and slide two. That makes the second slide responsible for delivering immediate value or giving the reader a clear reason to continue. A strong cover gets readers to start, but weak slides after it can still lose them. If readers stop at slide two, the care taken to choose the total slide count makes no difference because they never reach the rest.

The practical aim is a focused sequence that people finish. Each slide needs to give readers enough to make them want to swipe again without packing too much onto the page. That links length back to typography and padding rather than leaving it as a separate editorial decision.

How these specs work together as a mobile-first system, not a checklist

These specifications work because they constrain one another. Portrait adds mobile space, but its taller canvas makes protection from the bottom overlay more important. Keeping the file under 3 MB limits heavy raster imagery and favors simpler slides. One idea per slide then helps preserve both readable type and a focused overall length.

Forcing dense material into a target slide count pushes font sizes down and padding inward. Taking advantage of portrait height without respecting the safe zone leaves important text exposed. For founders and executives publishing through their own profiles, those failures have a concrete cost in presentation. Cropped text and tiny fonts signal poor communication before the reader has processed the argument.

The cover slide is the clearest test of the whole system. It must work in square or portrait, keep its message inside the safe zone, use heading-size type and load from a small file. It must also earn the first swipe in under two seconds. Test all of these needs together at phone size, because meeting one will not make up for falling short on another. A mobile-first carousel is ready when the reader can get to the point without fighting the format.