The short answer
Start a LinkedIn post, open the additional options, choose a document, upload your PDF, add its title and a useful caption, check the audience, then publish. Inspect the actual post afterward. An upload preview is not proof that the final document is readable or correct.
What you’ll take away
- Prepare a separate public copy of the file.
- Explain the main lesson in the caption as well as the document.
- A published attachment cannot simply be swapped for a corrected PDF.
Prepare the file you actually want people to keep
LinkedIn’s current document help lists a maximum of 100 MB and 300 pages, with PDF among the supported formats. Those are ceilings, not a target length. It also notes that document animation becomes static, and people allowed to view the post can download the document as a PDF.
Make a public copy rather than uploading the working master. Read every page for client names, private conversation fragments, internal links and numbers whose meaning changes outside your team. Removing a name from the caption does not remove it from the attachment.
For a recap, give the file a clear subject and period. Keep a private version note so you can identify exactly which file was published. A filename such as recap-public-v2.pdf is useful for your own records; the document title should explain the reader’s benefit.
A five-page example with a real reading path
Here is an invented structure for a creator explaining an onboarding lesson. It is a writing example, not an observed customer result. The reader should be able to follow the argument without a voice-over or animation.
Do not reduce a dense slide until it technically fits. Remove secondary claims, split the explanation or offer a readable companion page. If the meaningful detail disappears on a phone, a successful file upload has not solved the reader’s problem.
| Page | Reader’s job | Concrete content |
|---|---|---|
| 1 | Know the promise | One onboarding assumption I changed |
| 2 | Understand the starting point | The original instruction and its ambiguity |
| 3 | See the revision | A fictional before/after example, explicitly labeled |
| 4 | Apply the lesson | Three questions to check your own instruction |
| 5 | Know the limits | What was not tested, plus the next step |
Check more than the visual preview
Keep the source document structured, export meaningful text and check its reading order. W3C’s PDF technique explains why a visually clear multi-column page can still be read in the wrong sequence by assistive technology. Selecting text successfully is one useful check, not an accessibility certification.
Open the export on a narrow screen and try the actual sequence. Read links in context and check that important chart information is expressed in words. If a screen reader is part of your checking workflow, listen to the exported file rather than assuming the source editor’s order survived.
Offer the essential lesson in the post text or a suitably accessible companion format as well. W3C notes that fixed PDF layouts can remain difficult for people who need to adapt text appearance. A tagged PDF alone does not remove every access barrier.
Upload, then make the publishing decision
The desktop route in LinkedIn’s help is the post composer’s additional options, then the document control. Choose the file, add a document title, finish that step and write the post description. Mobile uses the document option under the additional post controls. Labels can vary by interface language.
Use the caption to state one takeaway and enough context to judge it. “A five-page fictional example for making onboarding instructions clearer” is more informative than “Swipe for value.” Verify the selected audience and intended file before using the publish control.
- Open the exported public file once more and verify the version and page sequence.
- Choose the document upload, confirm its title and review the loaded preview.
- Add a concise text summary, limitations and any accessible companion resource.
- Check audience and permissions. Publish only when the public copy is ready.
Verify the published post, not just the composer
Reopen the post from your activity and inspect its actual document. Check the first page, a middle page and the final page; then inspect any page carrying a key number or name. Where the viewer offers a download, check that the downloaded public copy is the intended file. Keep the post link in your version notes.
If the caption has a typo, edit the text. If the attachment contains a material error, LinkedIn says the document itself cannot be changed in the existing post. Decide whether to remove and republish a corrected version; explain a consequential correction where appropriate. Deletion is not a recall of copies people already downloaded.
Wrapped.li’s export choices help create a shareable asset. This guide covers the separate publishing and verification task. It does not promise that a document format will increase reach, nor claim that a draft or preview is already published.
Sources & product references
Product details reflect the publication date. External features and interfaces may change.
