How to Edit a PDF on a Chromebook

Chromebooks were designed around the browser, which makes them surprisingly capable for PDF work. There is no Adobe Acrobat for ChromeOS, and that is a feature, not a problem — once you know which browser-based and Linux-container tools to reach for, a $300 Chromebook handles 95% of the PDF tasks people use a $2,000 laptop for.

What ChromeOS gives you out of the box

Open any PDF on a Chromebook and you get the built-in viewer, which has quietly become quite capable:

• Highlight, underline, strikethrough.
• Sticky notes and free-text annotations.
• Drawing with finger, stylus, or trackpad.
• Form filling for interactive PDFs.
• Save, print, and "save as PDF" of any web page.

For sign-and-return tasks, this is enough. The viewer doesn't edit existing text, swap images, or rebuild forms — for those you need a real tool.

Method 1: Browser-based editor

The native option for Chromebooks is a browser tool. No install, no Linux container, no Android app. Docento.app edits PDFs in the browser tab itself, with the file staying on the device — useful for school reports and HR documents alike.

Works equally well on:

• A traditional clamshell Chromebook with trackpad.
• A 2-in-1 with stylus, where margin annotation feels natural.
• A larger Chromebook Plus device with extra performance for big PDFs.

Method 2: Android apps from the Play Store

Most Chromebooks support Android apps via the Play Store. The PDF apps that work best in this mode:

• Xodo — annotation, form filling, signature.
• WPS Office — fuller editing, with ads in the free tier.
• Adobe Acrobat Reader — most familiar, most paywalled.

These work, but Android apps on a 13-inch Chromebook screen sometimes feel cramped, and stylus integration varies. Browser tools usually feel more native.

Method 3: Linux apps via the Linux container

Newer Chromebooks support a Linux (Crostini) container, which unlocks desktop PDF tools:

• LibreOffice — opens, edits, and exports PDFs.
• Inkscape — for editing the visual content of a PDF page (great for diagrams).
• qpdf, pdftk, pdfcrop — command-line tools for splitting, merging, cropping, encrypting.
• Ghostscript — for compression and format conversion.

Setup: enable Linux in Settings → Advanced → Developers → Linux development environment, then install via apt. Worth doing if you process PDFs regularly. See our batch processing guide for examples.

Method 4: Web apps for specific tasks

Some PDF tasks have dedicated Chromebook-friendly web apps:

• Google Drive — preview, basic annotation, OCR via "Open with Google Docs" (which extracts text from a PDF into a Doc).
• Smallpdf, ILovePDF, etc. — feature-rich but they upload your file. Only use these for non-sensitive documents.
• In-browser, no-upload tools like Docento.app — keep the file on your device.

Filling and signing

Chromebooks are excellent for filling and signing PDFs:

• The native viewer handles real fillable forms.
• For non-interactive forms, browser tools let you type into the boxes and save.
• Signatures: a stylus on a 2-in-1 produces clean signatures; a trackpad signature is workable but jagged. For best results, sign on paper, photograph, and drop the image into the PDF.

For a deeper walkthrough, see how to sign a PDF online.

OCR on a Chromebook

ChromeOS has limited native OCR, but several options work:

• Google Drive: open a scanned PDF "with Google Docs" and the document opens with extracted text. Quality is decent for clean scans, weaker for handwritten or low-DPI images.
• Linux container with tesseract for batch OCR.
• Browser OCR tools that run via WebAssembly — slower than desktop, but private and surprisingly capable for occasional use.

See our OCR explainer for more.

Compression and combining

Both work entirely in the browser. Compression usually means resampling images to a lower DPI; combining is drag-and-drop in a thumbnail grid. For larger jobs, the Linux container plus qpdf or Ghostscript runs faster than browser tools.

See reducing PDF file size and how to combine PDF files.

Performance notes

Chromebooks vary widely in power. Tips:

• For PDFs over 100 pages, prefer a desktop-class browser tool with WebAssembly — it uses your CPU more efficiently than a hybrid Android app.
• Close other tabs before big edits. Memory pressure is the most common cause of "it crashed."
• For school-issued Chromebooks with limited specs, scanning with a phone and editing in a browser is often better than scanning directly on the Chromebook's webcam.

Privacy considerations on shared Chromebooks

If the Chromebook is school-issued or work-issued:

• PDFs in Downloads/ may sync to the school's Drive automatically.
• Browser history may be reviewed.
• Don't open personal financial documents on a managed Chromebook.

For sensitive documents, prefer a personal device or a guest browser session, and use tools like Docento.app that don't upload anywhere.

Conclusion

Chromebooks have quietly become great PDF machines. Browser tools handle editing, signing, filling, and combining. Android apps fill the gaps. The Linux container unlocks command-line power for batch work. Docento.app covers the everyday cases, with the file never leaving the Chromebook. For comparisons across devices, see our iPhone and Android editing guides.