Doing PDF work on a phone without installing anything

What the phone already does well

• Viewing and light annotation. Every phone opens a PDF, and both major platforms include a mark-up mode with drawing, text boxes, highlight and a saved signature you can drop onto a page.
• Scanning. The camera apps and note apps on current phones detect page edges, straighten and crop automatically, and export the result as a PDF. This is genuinely one of the best scanning tools most people own.
• Printing to PDF. The system print dialog usually includes an option to save the output as a PDF rather than sending it to a printer, which is a reliable way to produce a file from almost anything that can be printed.
• Sharing and storage. Files and Drive both accept a PDF, keep it available offline, and hand it to whatever app or website needs it next.

Where the built-in tools stop

The built-in tools are viewer-and-annotator shaped. They are consistently weaker at anything that changes the structure of a document rather than marking it up.

The pattern is consistent: built-in tools add marks to a document, while structural changes need something that can rewrite the file. That is the gap the browser route fills.

The app store route, and what it costs

Installed PDF apps are not inherently bad, but the economics explain a lot about them. Server-side processing costs the vendor money per document, so the free tiers are usually shaped to push you toward a subscription or to make the free output undesirable.

The recurring patterns are worth recognising: a watermark or a page limit on the free tier, a mandatory account before anything can be exported, a free trial that converts silently, and — most importantly — processing that happens on the vendor's servers rather than on your phone. That last one is invisible in use and matters a great deal for a contract, an invoice or an identity document.

It is also worth reading the permissions before installing. A PDF reader that requests access to contacts, location and the microphone is answering a question nobody asked.

What the browser route actually does

A modern mobile browser is a full application runtime. When you open a PDF tool page, the tool itself — the code that reads and rewrites PDFs, usually a few megabytes — is downloaded to the phone and runs there. The file picker reaches your Files, your Photos and your cloud storage, and the result is saved back to your downloads folder.

Two consequences follow, one good and one honest. The good one is that there is no install, no account and no server in the loop: the document is read by your own device and written by your own device. The honest one is that the limits of the phone become the limits of the tool. A few hundred pages of high-resolution scans is where a phone starts to run short of memory, and a large compression job will take minutes and drain the battery faster than a laptop would.

Practical advice follows from that: do a large job on a computer if you have one, and use the phone for the ordinary case — a dozen pages, a signature, splitting an attachment, adding page numbers before filing.

A phone-shaped workflow

Most real tasks are a small sequence rather than a single action. This is the order that avoids doing anything twice.

• Scan the paper with the phone's built-in scanner rather than a separate app. It already handles edge detection and straightening.
• Combine the shots into one PDF in the browser, in the order they should read.
• Rotate and crop the pages that came out crooked, before doing anything else to the file.
• Add page numbers if the document is going to be filed or referred to — it is much easier to add them now than to discuss "the page near the middle".
• Sign it if it needs signing, placing the mark on the page that actually carries the signature line.
• Open the finished file in the phone's own reader and page through it once before you send it.

Where a phone is genuinely the wrong tool

• Long documents. Memory and battery are real constraints. A 300-page file is a laptop job, whatever the phone claims.
• Anything you have to check carefully. Judging whether a scan is legible, or whether a redaction actually removed the text, needs a large screen and a zoom level a phone makes tedious.
• Precise cropping and placement. Positioning a signature or a crop box by finger is possible and imprecise. A trackpad or mouse is quicker and more accurate.
• Batch work. Twenty files that each need the same treatment is a script or a desktop batch, not twenty repetitions on a phone.

A useful compromise, if you have one: an iPad or a Chromebook in a desktop browser gives you the large screen and the pointer without needing a full computer.

Two checks before you send anything from a phone

• Confirm the file actually saved. Mobile browsers sometimes display a result in a temporary view rather than saving it. Open the downloads folder, or the Files app, and check that a file with the expected name and size is really there before you close the tab.
• Confirm you are sending the processed file. The single most common phone mistake is attaching the original from the photo roll because it is first in the list, or picking the version from before the last edit. Check the page count and the first page of the attachment itself, not the thumbnail the share sheet shows.