Skip to main content
PlugMonkey
Updated June 2026 · Verified against PDF.js + ISO 32000-2

How to Annotate PDFs in Chrome: A Step-by-Step Workflow Guide (2026)

Chrome's built-in PDF viewer cannot annotate. This guide walks you through a complete annotation workflow on a real document — color conventions, highlights, comments, sticky notes, freehand sketches, navigation, and export — using the free Enhanced PDF Viewer extension built on Mozilla's PDF.js engine. Everything runs locally in your browser.

Beginner
10 minutes
8 steps

By PlugMonkey Team, Editorial

TL;DR

Chrome's bundled PDF viewer is read-only for annotation — no highlighter, no comment tool, no sticky notes, no freehand drawing. The fix is a Chrome extension that re-renders PDFs with a real annotation layer. Enhanced PDF Viewer is the free option: it replaces Chrome's default viewer automatically on install, exposes five highlight colors plus inline comments, sticky notes, and freehand sketching, and renders everything locally on Mozilla's PDF.js engine with zero outbound network calls. The recommended workflow is: open your PDF, decide your color convention (the single most underrated step — yellow for facts, blue for questions, green for todos), highlight as you read, add inline comments to passages that need elaboration, drop sticky notes for standalone thoughts that don't anchor to specific text, use freehand drawing for diagrams or signatures, navigate between annotations from the sidebar, and export or print the annotated copy at the end so the markup travels with the document. Annotations persist within the current session and bake into printed and downloaded copies; cross-session storage is on the roadmap.

  • Pick your color convention before you start — yellow = fact, blue = question, green = todo is a widely-used legal/academic system that travels across collaborators.
  • Highlight as you read, then layer comments on top — separating capture from synthesis is the single workflow change that prevents most annotation regret.
  • Use sticky notes for thoughts that don't anchor to specific text; use freehand drawing for diagrams and signatures the highlighter cannot express.
  • Export or print at the end so annotations bake into the file — annotations persist within the session and survive print/download, but cross-session storage is on the roadmap.
“PDF.js is a Portable Document Format (PDF) viewer that is built with HTML5. PDF.js is community-driven and supported by Mozilla. Our goal is to create a general-purpose, web standards-based platform for parsing and rendering PDFs.”
— Mozilla PDF.js project — official description on the project GitHub repository, the engine that Enhanced PDF Viewer uses for rendering and annotation. · github.com/mozilla/pdf.js

The Numbers, By the Source

Every figure below cites a primary source. Click through to verify.

0 annotation tools

Number of annotation tools (highlight, comment, sticky note, sketch) exposed by Chrome's built-in PDF viewer as of Chrome 124+. The viewer is read-only for markup purposes — it supports text selection and copy but no markup persistence.

Source: Google Chrome Help — Open PDFs in Chrome2026

5 highlight colors

Highlight colors Enhanced PDF Viewer ships with (yellow, green, blue, pink, orange). Multi-color highlighting is the foundation of every serious PDF workflow — single-color highlighters force every passage into the same conceptual bucket.

Source: Enhanced PDF Viewer Product Spec2026

ISO 32000-2:2020

The international standard that defines PDF annotation objects — highlights, text comments, freehand ink — used by every conformant PDF reader. Enhanced PDF Viewer's annotation layer maps onto these standard objects via PDF.js.

Source: ISO — Document management (PDF 2.0)2026

Before You Start

  • Enhanced PDF Viewer installed from the Chrome Web Store (free, no account)
  • A PDF file or web URL you want to annotate — a contract, paper, textbook chapter, or spec works equally well
  • Google Chrome (or a Chromium browser: Edge, Brave, Arc) on desktop
  • Optional: keyboard shortcuts memorized for the fastest workflow
  • Optional: a color convention chosen in advance (yellow = fact, blue = question, green = todo)
1

Step 1 — Open Your PDF in Enhanced PDF Viewer

Once Enhanced PDF Viewer is installed from the Chrome Web Store, it automatically takes over PDF rendering in Chrome. There is no toggle to flip and no per-site permission to grant. Open any PDF — drag a local file into a Chrome tab, double-click a PDF in your file manager (Chrome must be the default PDF handler), or paste a PDF URL into the address bar. The extension's toolbar appears at the top of the document with the annotation tools grouped on the right. If you don't see the extension toolbar, check that the extension is enabled at chrome://extensions and that you've reloaded the PDF tab once after install. For password-protected PDFs, Enhanced PDF Viewer prompts for the password locally — decryption happens in-browser via PDF.js, the file is never uploaded to any server.
Pro Tip

Pin Enhanced PDF Viewer to your Chrome toolbar (puzzle-piece icon → pin) so you can right-click it to switch back to Chrome's built-in viewer for any one-off document that needs the simpler renderer. This is faster than disabling the extension entirely.

2

Step 2 — Pick the Right Annotation Color Before You Start

This is the single most under-discussed step in PDF annotation workflows. A color-coding convention chosen before you start reading turns highlights from decoration into signal. The widely-used legal and academic convention is: yellow = key fact / definition (the things you'll need to find again), blue = question / unclear passage (something to ask or research later), green = action item / todo (something that requires follow-up outside this document), pink = critical issue / risk (the things that change the conclusion), and orange = quotation / citation (passages you'll quote in your own work). Enhanced PDF Viewer's five-color palette maps directly onto this system. The W3C's WCAG guidance on color-as-meaning warns that color alone is insufficient for accessibility — so pair each color with a comment when the meaning matters for collaborators using screen readers or with color-vision differences. The convention also travels across collaborators: a shared color key is the cheapest team coordination ritual you can adopt.
Pro Tip

Write your color key into a sticky note on page 1 of the document before you start annotating. When you share the file later, the key travels with it — no out-of-band explanation needed.

Important

Don't change conventions mid-document. The single biggest regret with multi-color highlighting is re-reading three weeks later and realizing 'green' meant different things on different pages. Pick one system and hold it.

3

Step 3 — Highlight Key Passages as You Read

Click the highlighter icon in the toolbar, pick your color from the dropdown, then click and drag across the text you want to mark. The highlight applies immediately to the selected text. To remove a highlight, click the eraser tool and click the highlight you want to remove. Power users can stay in highlight mode and use the keyboard: select text with the mouse, press H to apply the current highlight color. To switch colors quickly, type the first letter of the color name (Y for yellow, G for green, B for blue, P for pink, O for orange) while the highlight tool is active. Stay in capture mode — highlight everything that catches your attention as you read. The temptation is to stop and synthesize after each highlight, but that breaks reading flow. The synthesis step is Step 4 (inline comments), kept deliberately separate from capture.
Pro Tip

Aim for roughly 5-15% of the document highlighted in total. Less than 5% and you'll wish you'd captured more on the second read. More than 25% and the highlights cancel each other out — everything is important so nothing is.

4

Step 4 — Add Inline Comments to Highlights That Need Elaboration

After the first reading pass, switch to the comment tool (speech-bubble icon). Click any highlight and a comment popover appears anchored to that passage. Type your thought, question, or cross-reference. The comment stays anchored even when you scroll, zoom, or rotate the page. Use comments for: your own interpretation of the highlighted passage, cross-references to other parts of the document ("see also page 47"), questions for collaborators when the document will be shared, and follow-up actions the highlight implies. Keep comments short — one or two sentences. If you find yourself writing a paragraph, you're synthesizing in the wrong place; that belongs in a sticky note (Step 5) or in a separate notes document. The comment tool is for elaboration anchored to specific text, not for free-form analysis.
Pro Tip

Add comments only to highlights that need them — usually 20-30% of your highlights. Commenting on every highlight defeats the purpose; the act of leaving most highlights uncommented is itself a signal that they're self-explanatory.

5

Step 5 — Drop Sticky Notes for Standalone Thoughts

Some thoughts don't anchor to specific text — overall reactions, summaries of a section, notes about what's missing, or reminders about the document's broader context. For these, use the sticky note tool (note icon). Click anywhere on the page and a draggable yellow note appears. Type your thought and drag the note to a non-intrusive corner. Sticky notes are visible at any zoom level and persist across navigation. The mental model: highlights and comments are anchored to text; sticky notes float on the page. Use sticky notes for: page-level summaries ("this whole page is about X"), what's missing ("no mention of edge case Y"), cross-document references ("see contract clause 4.2"), and reading-pause markers ("continue from here") when you'll come back to a long document. Resist using sticky notes when an inline comment would be more precise — anchored elaboration is almost always more valuable than free-floating notes.
6

Step 6 — Sketch Diagrams With Freehand Drawing

When text annotation isn't enough — when you need to circle a passage, draw an arrow between two concepts, sketch a small diagram, or sign a contract — switch to the freehand drawing tool (pencil icon). Click and drag to draw. The default ink color matches your highlight color; switch ink color from the toolbar dropdown. Freehand drawing is rendered as standard PDF ink annotations (per ISO 32000-2), which means they travel correctly when you export or print the annotated copy. Common uses: circling a value in a table or chart, arrows between concepts on a single page, signatures on contracts (use a stylus or trackpad), quick math in the margin of an engineering spec, and diagrams that explain your reading of a complex passage. The eraser tool removes ink strokes individually — click any stroke to remove it.
Pro Tip

If your trackpad signature looks rough, switch to a stylus on a touchscreen Chromebook or iPad-as-second-display via Sidecar. Both produce signatures that look hand-written rather than mouse-drawn.

Important

Freehand sketches in a PDF are not legally equivalent to digital signatures under PAdES or eIDAS. For binding contracts that require cryptographic guarantees, use a dedicated signing tool like DocuSign, Adobe Sign, or a PAdES-conformant desktop editor. Enhanced PDF Viewer's freehand tool is for visual sketching, not legal signature workflows.

7

Step 7 — Navigate Between Annotations With the Sidebar

Long documents accumulate dozens of annotations. To jump between them without scrolling, open the annotation sidebar from the toolbar (the icon resembles a small list). The sidebar lists every annotation in document order with a preview snippet and the annotation type icon. Click any entry to jump to it. The sidebar is filterable by type (highlights only, comments only, sticky notes only, sketches only) and by color. This is the workflow surface that turns annotation from a markup exercise into a navigation system. Use the filter to switch between modes: when reviewing your highlights, filter to highlights-only; when answering your own questions, filter to blue (your question color); when checking off todos, filter to green. The combined product is a faceted index of your reading, generated as a side-effect of annotating.
Pro Tip

Use the sidebar filter as a final review pass: filter to your 'critical issue' color (pink in the convention above) and walk through every flagged passage in 60 seconds. This is the single most valuable post-reading ritual — it catches the items you marked as critical but didn't act on.

8

Step 8 — Export or Print With Annotations Preserved

At the end of your annotation session, save the annotated copy so the markup travels with the file. From the toolbar, click Download — Enhanced PDF Viewer bakes annotations into the downloaded PDF, so opening it in Acrobat, Preview, or any other reader shows your highlights, comments, sticky notes, and sketches. The same applies to printing: Ctrl+P (or Cmd+P on Mac) opens Enhanced PDF Viewer's print dialog with annotation rendering enabled by default. For collaboration, the downloaded annotated copy is the best handoff artifact — it preserves the annotation layer in a standard format that every PDF tool can read. Annotations within the current session also persist across page navigation, zoom, and theme changes, but cross-session storage (the annotations surviving you closing the tab without exporting) is on the Enhanced PDF Viewer roadmap. Until that ships, the rule is: download the annotated copy before closing the tab.
Pro Tip

If you annotate the same document across multiple sessions, name your downloads with a date stamp (e.g., <code>contract-2026-06-01-annotated.pdf</code>). Each session produces its own annotated copy; the date stamps let you reconstruct a session-by-session history when needed.

Important

Closing the Chrome tab without downloading the annotated copy will lose your annotations for that session. There is no auto-save and no recovery flow — annotations are session-scoped until the cross-session storage feature ships. Treat the Download step as part of the workflow, not as optional cleanup.

Summary

Annotating PDFs in Chrome requires an extension because Chrome's built-in viewer is read-only for markup — there is no highlighter, no comment tool, no sticky notes, and no freehand drawing. Enhanced PDF Viewer (free, built on Mozilla PDF.js, 100% local) replaces the built-in viewer automatically on install and exposes the full annotation surface: five highlight colors, anchored inline comments, draggable sticky notes, and freehand drawing. The workflow that holds up across legal review, academic reading, contract negotiation, and code documentation is the same: pick a color convention before you start, highlight as you read without stopping to synthesize, add inline comments to passages that need elaboration, drop sticky notes for standalone thoughts that don't anchor to text, use freehand drawing for diagrams and signatures, navigate between annotations via the sidebar, and export or print the annotated copy at the end so the markup travels with the document. Annotations persist within the current session and bake into downloaded and printed copies; cross-session storage is on the roadmap. The whole flow runs entirely inside your browser — no uploads, no telemetry, no account — which matters for confidential contracts, unpublished research, and medical or financial records that should never touch a third-party server.

Need More Help?

Get personalized AI assistance with additional tips and troubleshooting.

Ask ChatGPT(opens in new tab)Ask Perplexity(opens in new tab)Ask Claude(opens in new tab)

AI responses are generated independently and may vary

Related Guides

PDF Accessibility Checklist for Chrome: WCAG-Aligned Reader SetupHow to Highlight and Annotate Web ArticlesHow to Save and Organize Articles with ReadMonkey Pro

Frequently Asked Questions

Sources & Further Reading

  1. Mozilla PDF.js GitHub repository — open-source PDF rendering and annotation engine. Apache 2.0 license. — Mozilla Foundation / GitHub (accessed Jun 1, 2026)
  2. PDF.js project homepage — feature overview, demos, and annotation-editor capabilities — Mozilla Foundation (accessed Jun 1, 2026)
  3. ISO 32000-2:2020 — Document management — Portable document format (PDF 2.0). The PDF standard that defines annotation objects (highlights, text comments, freehand ink, sticky notes). — International Organization for Standardization (accessed Jun 1, 2026)
  4. Open PDFs in Chrome — official Google Chrome help article. Confirms the built-in viewer's read-only annotation surface. — Google Chrome Help (accessed Jun 1, 2026)
  5. WCAG 2.1 — Use of Color (Success Criterion 1.4.1). Guidance on why color alone is insufficient as a meaning signal — pair with text labels for accessibility. — W3C Web Accessibility Initiative (accessed Jun 1, 2026)
  6. Enhanced PDF Viewer — annotation toolbar spec, privacy architecture, and PDF.js engine attribution — PlugMonkey (accessed Jun 1, 2026)

More Resources

FAQCommon QuestionsIntegrationsWorkflow ConnectionsGlossaryKey Terms Explained

Annotate Any PDF in Chrome — Free Forever

Enhanced PDF Viewer adds highlights, comments, sticky notes, and freehand drawing to Chrome's PDF viewer. Built on Mozilla PDF.js, 100% local — no uploads, no telemetry, no account. Install once and Chrome routes every PDF through the enhanced reader automatically.

Install Free — Chrome Web Store(opens in new tab)Learn More