Paperlane

Notes on documents, scans and print jobs

Paperlane is a small site about the boring half of paperwork: file sizes, reading order, form fields that refuse to cooperate, and print settings that behave differently on every machine. Nothing here is a product review. Every note comes from a document that had to be fixed before a deadline.

Recent notes

14 October 2026

Why a scanned page weighs three times more than it should

A 300 dpi colour scan of a text page is mostly noise that the eye never resolves, and that noise is what bloats the file. Converting the bitmaps to a 1-bit or greyscale image at 200 dpi, with JPEG quality around 75 for anything with a photograph, usually cuts size by two thirds with no visible difference on screen or on a desktop printer.

Two paragraphs, no before/after screenshots.

2 October 2026

A default zoom that survives the next print job

Setting "fit to page" as the opening view affects only the viewer window, not the printed sheet, which is why a document can look right on screen and clip badly on paper. If the page is A4 and the printer margins are 6 mm, the reliable fix is to leave the view at 100% and shrink the content box instead.

Written for the person who prints for other people.

21 September 2026

What "flatten" actually does to form fields

Flattening (the Adobe Acrobat command, not the printer setting) bakes the current field values into the page content and drops the interactive objects, so a form becomes a picture of a form. It is the right move before sending anything to a signature service, and the wrong move if the recipient still needs to tick boxes or type in a date.

Keep an unflattened copy. Always.

9 September 2026

Reading order and the tag tree in an old scan

A flat scan has no structure, so a screen reader reads whatever order the OCR pass produced, which is often column by column across the whole sheet. Rebuilding the tag tree by hand is slow, but correcting the reading order on the first five pages usually fixes the worst of it for anything under forty pages.

Tested with a 22-page council document.

28 August 2026

Print presets that don't fight the printer driver

Most print presets store the paper size and tray by index, so a preset made on one machine picks the wrong tray on another even when the paper is identical. Storing the preset by name and letting the driver resolve the tray, rather than by position, survives moving a job between two offices.

Applies to shared printers in the same building.

12 August 2026

When a second, archival copy is worth the disk space

If a document will be stored for years and must open the same way later, a constrained subset such as PDF/A is worth the extra megabytes because it embeds fonts and forbids the features that tend to change. For a file that is read twice and thrown away, it is not worth the conversion time.

Short version: archive the contracts, not the invoices.

How we test

Every note starts as a real document: a scanned form, a printed report, a signed contract, a badly exported spreadsheet. Changes are measured, not guessed — output file size in kilobytes, page count, whether the text layer still selects, and whether the file opens on a machine that has never seen the fonts used to make it. Notes are published only when the same fix works twice on two different documents.

We deliberately avoid screenshots. A screenshot is one person's window layout, and it ages badly. The descriptions here are meant to be followed from memory on a machine that looks nothing like ours.

About Paperlane

Paperlane has been running since 2019 as a one-person site. It began as a folder of internal notes written while repairing scans for a small records office, and stayed online because the same questions kept arriving from other people with the same problem. The tone is deliberately flat: no tutorials that begin with a story, no lists of ten tools.

The site is plain HTML with a stylesheet and about a hundred lines of layout. Pages are written to open in one request and to render with scripting switched off, which matters on old machines and on locked-down office browsers. There is no comment section, no account system, and no tracking beyond whatever the host records.

Everything is checked against a free reader and, where it matters, against Adobe's own viewer. Corrections are welcome and are usually published as a footnote on the note itself rather than a separate post. If something here is wrong on your setup, the note will say so rather than pretend the setup is unusual.

The address field does not submit anywhere yet. Pressing Enter just returns you to this section. Nothing is stored, nothing is sent.

Contact — corrections, dead links, and requests for a specific document problem: notes at paperlane, in the box below any note.

What gets a reply — anything with a file size, a page count and what you already tried. "It doesn't work" usually gets a guess.