Saltar al contenido
Volver a todas las herramientas№ 085

Optimizar para la web

Lineariza un PDF para una vista web rápida y streaming progresivo.

0 B subidos a un servidor

Añade primero un archivo.

In an ordinary PDF the information a reader needs to draw page one is scattered through the file, with the index at the end — so a browser has to fetch the whole thing before it can show anything. Linearizing reorganises the file so the first page and its resources come first, which is why a linearized 40 MB document starts displaying almost immediately while an ordinary one shows a blank frame until the download finishes.

It reorganises rather than removes, and the tool says so plainly: linearization does not necessarily make the file smaller. If the goal is a smaller download rather than a faster first page, that is Compress. The two combine well — compress first, then linearize what remains.

How it works

  1. Drop in a PDF.
  2. Optimize it for the web.
  3. Download the linearized file and put it where it is served from.

What people use it for

  • Publishing a long catalogue or report on a website so the first page appears at once.
  • Serving a large PDF to readers on slow connections without a blank wait.
  • Preparing documents for a document portal where perceived speed matters.

Frequently asked questions

Is my file uploaded to a server?
No. The file is opened by JavaScript and WebAssembly running inside your own browser tab. It is never uploaded, there is no server-side processing and nothing is stored — closing the tab discards everything.
Why is the file not smaller?
Because linearizing is a reordering, not a reduction: the same content, arranged so the first page can be drawn from the beginning of the download. For a smaller file use Compress.
Will readers notice?
On a big file over a slow connection, very much so — the difference is between a first page in a second and a blank frame for thirty. On a small file served locally, not at all.
Does the server need to support anything?
It has to serve byte ranges, which effectively every web server does by default. Nothing needs configuring; the benefit only appears when the file is fetched over HTTP, not when it is opened from disk.
Should I compress as well?
If the file is heavy, yes, and in that order: compress first to reduce what has to travel, then linearize the result so what does travel starts rendering immediately.

Herramientas relacionadas