Start a project ↗
TREN
← LMC NOTES / CONTENT & DIGITAL MARKETING

How to build a LinkedIn PDF post people can follow

A presentation needs a speaker. A document post needs to make sense on its own. Plan the reading experience before you start laying out pages.

Five folded ivory paper panels with different blue geometric forms arranged in a deliberate sequence.

The short answer: Pick one question your audience needs answered, build a page sequence around it, and design for a phone before exporting a PDF. Review the actual file and the upload preview, then hand over the document title, post copy and approved version together. Here, a “PDF carousel” means an organic LinkedIn document post.

Give the post one job

Starting with “we need a carousel” settles the container and leaves the brief unwritten. Start with the reader instead. What decision will they be better equipped to make after the final page: comparing a service, preparing a brief or understanding a process?

An exhibition supplier, for example, could explain what a client needs before requesting a stand quotation. That is a more focused reading task than browsing a complete company presentation. This is an illustrative content idea, not a client case or a claim about results.

Write a one-sentence promise and choose the next step that belongs with it. If the promise is a useful checklist, deliver the checklist before asking for a call. Our note on better briefs can help the team agree on that scope.

Outline the sequence before designing the cover

A sequence should move the explanation forward. Repeating the opening statement across several attractive layouts adds pages without adding value. The six-page structure below is LMC’s example for a short B2B explainer, not a LinkedIn requirement or an optimum proven by performance data.

Illustrative topic: information to prepare before requesting a trade-show stand quote.
PageReader’s taskEditorial choice
1 — PromiseRecognise the questionA specific benefit instead of a vague slogan
2 — ContextDefine the projectSpace, use and event information
3 — DistinctionSeparate the needsMeeting, demonstration and storage requirements
4 — ExampleSee what good input looks likeA short brief the reader could complete
5 — CheckSpot missing decisionsApproval owner, delivery and installation dates
6 — Next stepKnow what to do nextPrepare the brief or discuss the scope

If four pages answer the question, stop at four. If the explanation keeps growing, narrow the question or move the detail into a linked article. The cover should identify the subject even when someone sees it without the accompanying post copy.

Judge the layout on a phone

For an initial design test, we suggest comparing a square page with a 4:5 portrait page on a real phone. A 1080 × 1350 design canvas is one possible starting point. It is an editorial choice, not an official organic-post size or a pixel requirement for a PDF.

Make room for a short heading, one main point and a useful visual on each page. When the content does not fit, edit it before reducing the type. A readable cover cannot compensate for explanation pages that need constant zooming.

  • Keep margins, page numbering and the small brand signature consistent.
  • Give references enough space to be read; put longer source notes on an accessible web page.
  • Choose a layout for the task: comparison, worked example and checklist need different structures.
  • Use labels and shapes as well as colour to communicate distinctions.

Recognition comes from repeatable design decisions, not a logo in every available corner. Our brand consistency note explores how that works across different formats.

Treat the PDF as a deliverable that needs checking

LinkedIn’s document FAQ sets upload ceilings of 100 MB and 300 pages, with one document per organic post. Those limits are not editorial targets.

Its preparation guide recommends PDF, consistent page sizes and merging or flattening multiple PDF layers. Animation appears as static imagery.

Reopen the exported file. Inspect line breaks, special characters, image crops and page order. Avoid embedding needlessly large photographs, but check fine detail again after compression. A file that opens successfully has passed only the first check.

Do not equate merging PDF layers with turning every page into a screenshot. Keep the editable source and deliver the publication PDF as a separate, clearly named version.

Plan for the downloaded reading experience too

Adobe recommends planning accessibility in the source document. Keep real text and consider heading structure and alternative descriptions for meaningful images while authoring.

Use Acrobat’s accessibility checks and reading-order tools to evaluate the exported PDF. Selectable text alone does not establish accessibility.

We also recommend putting a concise version of the answer in the post copy and offering a readable web page for further detail. Do not assume the LinkedIn preview preserves every accessibility feature of the original. Check the PDF as a separate deliverable.

Approve the file, the title and the post copy together

LinkedIn’s upload workflow adds a document through the post composer, then asks for a document title and post description. Interface labels can vary. Check the publishing identity before proceeding.

The document title should make sense to a reader, not just to the production team. Replace an archive name such as “final_v7_approved” with a useful topic title. The post copy can introduce the problem and the value of reading, rather than repeating the cover word for word.

LinkedIn does not let you replace the document inside an existing post. Make sure the editorial, design and publishing owners review the same final PDF. Updating the source file while uploading an older export is an avoidable version error.

  • Can someone comfortably read the first, middle and final pages on a phone?
  • Have names, dates, claims and permitted visual assets been checked?
  • Does the exported PDF match the approved artwork?
  • Does the upload preview show every page in the intended order?
  • Is the next step clear, with a usable destination?

An agency handover should include the editable source, publishing PDF, document title, post copy and approval record. The publishing team should not have to reconstruct the missing parts after design sign-off.

Frequently asked questions

How many pages should a LinkedIn PDF post have?

Use the length needed to answer one question without repetition. Our six-page outline is an example for a short B2B explainer, not a platform rule or a performance guarantee.

Can we upload our existing company presentation?

Review its audience and context first. A dense deck that needs a presenter may not work as a self-contained feed post. Choose one topic and rework its headings, copy and next step for that reading experience.

What should we send to the agency?

Provide the reader’s question, key message, approved sources, brand assets and intended next step. Name the content approver and publishing owner in the brief as well.

Sources and review date

Sources checked on 23 October 2026. Platform behaviour is based on LinkedIn documentation; PDF accessibility guidance comes from Adobe. Page sequencing, canvas choice, handover and review steps are LMC editorial recommendations, with no promise of reach or engagement.

  1. LinkedIn — Upload and share documents
  2. LinkedIn — Document uploads FAQ
  3. LinkedIn — Document ads specifications
  4. Adobe Acrobat — Creating accessible PDFs
  5. Adobe Acrobat — Create and verify PDF accessibility