What a LinkedIn Document Post Is and How LinkedIn Processes the File

What is a LinkedIn document post?

A LinkedIn document post is a feed post whose content is an uploaded PDF, PowerPoint or Word file, which the feed displays as a set of pages the reader moves through inside the post. LinkedIn's developer documentation treats it as its own content type. The Posts API reference states: "Creating a post with a document requires uploading a document asset to obtain a Document URN (urn:li:document:{id}) for use in the post." The file comes first, the post second.

LinkedIn sets the file limits on the Documents API page: "The file size can't exceed 100MB and 300 pages. The following file types are supported: PPT, PPTX, DOC, DOCX, and PDF." Those two sentences are the full spec LinkedIn publishes for the file.

Property	Value	Source
File types	PPT, PPTX, DOC, DOCX, PDF	Documents API
Maximum file size	100MB	Documents API
Maximum pages	300	Documents API
Asset identifier	urn:li:document:{id}	Posts API
Organic posting	Supported	Posts API
Sponsored posting	Supported	Posts API
Page size or ratio	Not documented	Neither page

The last row matters for design. LinkedIn's developer pages give no page dimensions and no aspect ratio for documents. Any pixel size you read for document pages comes from someone's testing, not from LinkedIn's spec.

Is a LinkedIn document post the same as a LinkedIn carousel?

A LinkedIn document post is what most people mean by a "LinkedIn carousel", but LinkedIn's API uses the word carousel for a different format that organic posts cannot use. The Posts API reference has a table of content types with one column for organic posts and one for sponsored posts, and the rows disagree on exactly this point.

Content type	Organic (non-sponsored)	Sponsored
Documents	Yes	Yes
Carousels	No	Yes
MultiImage	Yes	No
Images	Yes	Yes
Videos	Yes	Yes

Read the Carousels row carefully. In LinkedIn's vocabulary, a carousel is a sponsored ad unit. An organic post that swipes sideways is a document post, and an organic post with several photos is a MultiImage post. Those are two separate formats with two separate upload flows.

A scheduler that says it supports organic "LinkedIn carousels" means document posts or MultiImage posts, because LinkedIn does not allow the Carousel type outside ads. Our general guide to carousel posts covers how the swipe format works across the other networks, where "carousel" means a set of images.

Which file should you upload for a LinkedIn document post?

Upload a PDF for a LinkedIn document post, because a PDF fixes your fonts and layout before LinkedIn touches the file. LinkedIn accepts PPT, PPTX, DOC and DOCX as well, but it has to process every upload before the file can appear in a post. The Documents API describes the PROCESSING status as "Asset is processing to generate missing artifacts." The sample response on that page returns a downloadUrl whose path contains ads-document-pdf-analyzed, a path name that suggests LinkedIn keeps a PDF version of whatever you sent.

Upload a PowerPoint file and any conversion happens on LinkedIn's side, with whatever fonts LinkedIn has. Upload a PDF and it already happened on your machine, where you saw the result. LinkedIn does not document how it renders fonts missing from a DOCX or PPTX.

Of the two limits, 100MB is the one image-heavy slides hit first, because a PDF exported at print quality keeps every image at full resolution. The 300 page cap sits far above anything a reader will page through in a feed.

PDF or PowerPoint and Word

PDF

• Fonts and layout are fixed before you upload
• What you see in the file is what LinkedIn gets to work with
• Matches the downloadUrl path name ads-document-pdf-analyzed

PPT, PPTX, DOC, DOCX

• LinkedIn converts the file on its own side
• Font rendering for missing fonts is undocumented
• Still capped at 100MB and 300 pages

How does a document post get published through the LinkedIn API?

A document post gets published in two stages: you upload the file to the Documents API and get back a document URN, then you create a post that references that URN. The Documents API page walks through each call.

1. Call POST /rest/documents?action=initializeUpload with an initializeUploadRequest that names the owner, either a person URN or an organization URN.
2. Read the response. It returns an uploadUrl, an uploadUrlExpiresAt timestamp and the document URN in the form urn:li:document:{id}.
3. Upload the file to the uploadUrl. LinkedIn's sample uses curl --upload-file with a bearer token and gets back HTTP/2 201.
4. Call GET /rest/documents/{document URN} and read status until it says AVAILABLE.
5. Call POST /rest/posts with content.media.id set to the document URN and content.media.title set to the title you want on the document, plus the post's commentary, visibility, distribution and lifecycleState.

The page adds one restriction: "SYNCHRONOUS_UPLOAD is not supported in Documents API." The flow mirrors the one for images, and our walkthrough of how LinkedIn initializeUpload turns a file into an image URN shows the same pattern with its error tables.

LinkedIn's page does not say whether a post can reference a document that is still processing. Waiting for AVAILABLE in step 4 is the order that never depends on that answer.

What do the LinkedIn document status values mean?

A LinkedIn document asset moves through four status values that tell you whether the file can go into a post yet. The Documents API defines each one in its schema table.

Status	LinkedIn's definition
WAITING_UPLOAD	"Waiting for client to upload source file or uploading process to be completed."
PROCESSING	"Asset is processing to generate missing artifacts."
AVAILABLE	"All of the recipe's required artifacts are ready. The asset is available to be served."
PROCESSING_FAILED	"Processing failed due to client error such as file size too large, unsupported file format, internal error (e.g., performance issue, database error, network failure), or other issue."

PROCESSING_FAILED is the one to plan around. Its definition lumps your mistakes, such as a 120MB file or an unsupported format, together with LinkedIn's own outages under one value. The status alone does not tell you which side failed. Check the file against the limits first. If the file is within them, upload it again. When a scheduled document post does not go out, that split between file problems and platform problems is the first thing to check, and our guide to LinkedIn scheduled posts not working covers the other causes.

Who can publish a LinkedIn document post?

A LinkedIn member can publish a document post on their own profile, and a company page admin can publish one on the page. The Documents API checks permissions against the owner you named at upload. "For documents with company URN owners, the caller must have ADMIN or DSC permissions for the company page." For person owners, "the caller must match the document owner."

The scopes follow the same split. w_member_social posts on behalf of the authenticated member, and w_organization_social posts on behalf of an organization, which LinkedIn restricts to "the company admin, DSC poster, or content admin." A caller without the right permission gets a 403 with the message "Accessing this document resource is forbidden. Please check your permissions for this resource."

Decide the owner before you upload. The permission check runs against the owner named in initializeUpload, so a file meant for a company page post goes up with the organization URN as its owner, not the URN of the member doing the upload.

How do you prepare a file for a LinkedIn document post?

Prepare a file for a LinkedIn document post by exporting it to PDF, checking it against LinkedIn's two limits, and deciding on the document title before you schedule.

1. Export the deck or document to PDF from the app you designed it in.
2. Check the file size is under 100MB. Compress images inside the PDF if it is not.
3. Check the page count is under 300.
4. Open the PDF and page through it once. What you see is what LinkedIn gets to work with.
5. Write the document title separately from the post text. The API stores it in content.media.title, apart from commentary.
6. Put the reason to open the document on the first page, since the first page is what shows before anyone moves through it.

Step 6 connects to how LinkedIn measures attention. LinkedIn's feed dwell time starts counting when "at least half of a feed update is visible as a member scrolls through their feed," according to LinkedIn's engineering team, and a document post is a feed update like any other. The first page is the part of the document that is on screen when that clock starts.

Can you schedule a LinkedIn document post with AdaptlyPost?

AdaptlyPost schedules LinkedIn document posts to connected LinkedIn profiles and company pages. In the composer, Document is one of the content types alongside text, image, video and carousel posts, and the upload accepts "PDF, PPT, PPTX, DOC or DOCX, up to 100MB", which matches LinkedIn's own file types and size cap. The LinkedIn options include a document title field, described in the composer as "Shown above the carousel in the LinkedIn feed". AdaptlyPost's copy does not state a separate page limit, so LinkedIn's 300 page cap is the one that applies. The LinkedIn post scheduler page covers connecting a profile or page over OAuth and queuing posts, and our guide on how to schedule LinkedIn posts compares the scheduling options.

Frequently asked questions

What file types can a LinkedIn document post use?

LinkedIn accepts PPT, PPTX, DOC, DOCX and PDF files for document posts. The Documents API lists those five formats and no others. PDF is the safest choice, because it fixes fonts and layout before LinkedIn processes the file.

How large can a LinkedIn document be?

LinkedIn caps a document at 100MB and 300 pages. Both limits come from the Documents API reference. The definition of the PROCESSING_FAILED status names "file size too large" as one of its causes.

Is a LinkedIn carousel the same thing as a document post?

For organic posts, the swipeable carousel people talk about is a document post. LinkedIn's API reserves the Carousel content type for sponsored ads and marks it as unavailable for organic posts. An organic post with several photos is a separate MultiImage post.

Can a LinkedIn document post be published through the API?

Yes. You upload the file through the Documents API's initializeUpload action, which returns a document URN, then create the post with POST /rest/posts and set that URN as content.media.id. The Documents API does not support SYNCHRONOUS_UPLOAD, so the file always goes up through the upload URL before the post is created.

What is the title on a LinkedIn document post?

The title is a separate field, content.media.title, that belongs to the document rather than the post text. LinkedIn's sample request sets it to "Example.pdf". AdaptlyPost's composer describes its document title field as "Shown above the carousel in the LinkedIn feed".

Can a company page publish a LinkedIn document post?

Yes. A company page document post requires the caller to hold ADMIN or DSC permissions on the page, and the document must be uploaded with the organization URN as its owner. A member without those permissions receives a 403 from the Documents API.

What should you check before re-uploading a failed LinkedIn document?

Check the file against LinkedIn's two limits, the 100MB size cap and the 300 page cap, since PROCESSING_FAILED lumps file mistakes and LinkedIn's own errors under one status. If the file passes that check, upload it again.

What LinkedIn API scopes cover document posts?

w_member_social posts a document on behalf of the authenticated member, and w_organization_social posts on behalf of a company page, restricted to the company admin, DSC poster or content admin. Which scope you need depends on the owner URN you set at upload.

Does dwell time apply to LinkedIn document posts?

A document post is a feed update like any other, so LinkedIn's dwell time clock starts once at least half of it is visible as a member scrolls. The first page of the document is what's on screen when that clock starts, which is why the post text says to put the reason to open the document there.

Does AdaptlyPost enforce LinkedIn's 300 page limit for document posts?

AdaptlyPost's composer states no separate page limit for document uploads, so LinkedIn's own 300 page cap is the one that applies. The composer does match LinkedIn's file types and 100MB size cap.