A standard PDF file must be fully downloaded before any content can be displayed. For a 50-page PDF embedded on a webpage, this means the visitor sees nothing until all 50 pages have transferred from the server to their browser. A linearized PDF reorganises the file structure so the first page can be displayed as soon as that part of the file arrives, before the rest of the document has downloaded. For PDFs hosted on websites, this is the difference between a document that appears immediately and one that shows a blank loading screen for several seconds.
What linearization actually does to a PDF file
A standard PDF stores its cross-reference table, which is the index telling the reader where each page and object is located in the file, at the end of the file. This means a reader must download the entire file before it knows where to find page one. The file itself is often stored in the order objects were created during editing, which may not correspond to the reading order at all.
A linearized PDF reorganises the file so that the first page's content appears near the beginning of the file, the cross-reference table is stored at the start, and the remaining pages are stored in reading order. A PDF reader that understands linearization can begin rendering page one as soon as the first portion of the file arrives, then load subsequent pages progressively as they download.
This progressive loading requires the server to support HTTP range requests, which allow a PDF reader or browser plugin to request specific byte ranges of the file rather than the entire thing. Most modern web servers support range requests by default.
When linearization makes a practical difference
Linearization makes the largest practical difference for PDFs that are hosted on websites and viewed in browser-based PDF viewers, particularly when the PDFs are long and the connection is slow. A 10MB annual report hosted on a company website benefits significantly from linearization: readers can start reading the executive summary on page one while the remaining 49 pages continue loading in the background.
For PDFs shared as email attachments, linearization provides no benefit because the file must fully download before the email client opens it. For PDFs in document management systems that download files locally before opening them, linearization similarly provides no benefit.
For PDFs embedded in websites using a JavaScript PDF viewer library, linearization allows the viewer to display pages on demand rather than loading the entire document. A viewer that shows only the current page and loads adjacent pages on navigation is dramatically more responsive with a linearized PDF than with a standard one.
Checking whether a PDF is linearized
In Adobe Acrobat, the Document Properties dialog (File, Properties) shows whether the PDF is linearized in the Description tab. Look for "Fast Web View: Yes" in the properties. If it shows No, the PDF is not linearized.
In the terminal, the command-line tool pdfinfo (part of the poppler utilities on Linux and Mac) shows linearization status in its output. Running pdfinfo on any PDF file outputs a line indicating whether the file is linearized.
A quick visual check can be done by uploading the PDF to a web server and accessing it through a browser. If the first page appears almost immediately while the browser is still showing the loading indicator for the rest of the page, the PDF is likely linearized. If nothing appears until the full file loads, it is not.
Creating a linearized PDF
Adobe Acrobat creates linearized PDFs when you use File, Save As, which triggers a full rewrite of the file structure. The regular Save function in Acrobat uses incremental save, which adds changes to the end of the file and does not linearize. Always use Save As to create a fresh linearized PDF when you want fast web view.
Ghostscript, the open-source PDF toolkit available on all platforms, creates linearized output when run with the -dFastWebView=true flag. This is useful for batch processing collections of PDFs that need to be prepared for web hosting.
Most PDF creation tools that export from word processors or design applications do not create linearized PDFs by default. The PDF is created in whatever internal structure the tool uses, without linearization optimisation. If web performance is important for your PDF content, running the exported PDF through Adobe Acrobat or Ghostscript to linearize it is a post-processing step worth adding to the workflow.
Linearization and file size
Linearization itself does not change the total data in the PDF. The same content is present before and after linearization. The file size changes are minimal, typically less than 1 percent, because linearization only reorganises how the data is arranged in the file rather than changing the data itself.
The perception of a linearized PDF loading faster than a non-linearized one is not because the file is smaller. The file is the same size. It loads faster in the experiential sense because users see content sooner, even before the full file has arrived. The full download time is the same or nearly so.