Draw on a PDF — when free-form ink is the right markup, and what's actually getting saved
Drawing freely on a PDF — sketching arrows, circling key passages, jotting margin notes by hand — is one of those operations that feels primitive but is genuinely useful for review workflows. The challenge is that PDFs are a structured format and freehand strokes are anything but: every wiggle of a stylus or mouse needs to be captured as a path, embedded into the page, and rendered correctly across every viewer that opens the file. Here is what the draw tool actually does with your strokes, the precise difference between content-stream paths and proper /Ink annotations, and the four real-world review workflows where free-draw beats the alternatives.
What happens to your strokes under the hood
As you drag the pointer (or stylus, or finger), the tool captures every position in CSS pixels, smooths the line with light Bezier interpolation, then converts the points to PDF-space coordinates using the canvas's actual rendered size. When you click Apply, every stroke becomes an SVG path drawn into the destination page's content stream via pdf-lib's drawSvgPath. The page's existing content (text, images, vectors) is untouched; the strokes are layered on top.
The output PDF reads identically in every viewer. Strokes appear at the exact same on-page positions in Acrobat, Preview, Chrome, Firefox, every mobile reader. They scale correctly when zoomed (because they are vectors, not raster). They print at full resolution. They survive merging, splitting, page extraction.
Content-stream paths vs /Ink annotations
The technical distinction matters for one specific downstream workflow:
- Content-stream paths (what this tool does). Strokes are part of the page's drawn content — like every other text run, image, or vector. They look identical to /Ink annotations visually. The advantage: works in every viewer with no compatibility caveats. The trade-off: Acrobat's annotation panel doesn't list them (they're page content, not annotations), so workflows that depend on enumerating annotations (Adobe Acrobat's review tracker, some commenting platforms) won't see them.
- /Ink annotations (paid Annotate ships these). Strokes are stored as proper /Ink annotation objects. Acrobat's annotation panel lists them; comment-tracking workflows enumerate them; reviewers can right-click to add replies. The trade-off: some older viewers render /Ink annotations slightly differently than the canonical pen rendering.
Four real-world workflows where free-draw earns its place
Cases where ink markup is exactly what you want:
- Quick visual review feedback. Circling a paragraph, drawing an arrow to a chart, scratching out a sentence — these communicate review feedback faster than typed comments. The reviewer's intent comes across at a glance.
- Annotating diagrams and charts. Pointing to specific data points, marking an X on a flaw, highlighting a region of a screenshot. Ink markup is the natural fit; typed annotations would clutter the visual.
- Teaching and student feedback. Grading worksheets, marking essays, annotating student work. Free-draw matches how teachers naturally work in print and translates that to digital.
- Field notes on technical drawings. Engineering, architecture, construction — quick markup of CAD-exported PDFs in the field. Mobile + stylus + free-draw is the standard digital-replacement for paper redlines.
Tool features worth knowing
Specifics that determine usability:
- Page-aware undo. Click Undo to remove the last stroke on the CURRENT page. Won't accidentally remove a stroke from a previous page you already moved past. Useful for multi-page review where you want to fix a stroke without rolling back work on another page.
- Per-stroke editing before apply. The tool shows a stroke list — you can remove individual strokes before clicking Apply. Once applied, strokes become part of the page content and can't be removed without re-rendering through a redaction tool.
- 5 colors + adjustable stroke width. Black, red, blue, green, orange. Stroke width 1-8pt. Sufficient for the visual-feedback use case; not trying to be a full graphics tool.
- Touch + stylus support via Pointer Events. Works with mouse on desktop, finger on tablet, Apple Pencil on iPad, S Pen on Galaxy Tab. Pressure sensitivity isn't honored (stroke width is fixed per stroke); proper pressure-aware ink is a paid roadmap item.
- Mid-drawing window resize works. Strokes are stored in PDF coordinate space, not CSS pixels. Resize the window mid-session and committed strokes still align with the page content.
When to reach for a different tool
Three cases where free-draw isn't right:
- Highlighting passages. Use Highlight PDF for proper transparent-yellow highlights. Free-draw can simulate it but the result is a yellow squiggle rather than a clean highlight rectangle.
- Adding text comments. Use Add Text Box for typed annotations. Trying to handwrite with a mouse is painful; type instead.
- Removing or replacing text. Scratching out text with ink is visually OK but doesn't remove the underlying text — readers can still copy-paste the crossed-out content. Use Redact for real content removal.
Limits and compatibility
On the free web tool, free-draw handles PDFs up to 50 MB with no page-count cap. Processing runs in your browser via pdf-lib; nothing is uploaded. Output is byte-compatible with every PDF reader; strokes render identically across viewers because they're standard SVG paths in the content stream.
Common pairings: Free-draw + Add Text Box for documents with both ink markup and typed comments. Free-draw → Flatten to lock in the markup. Free-draw → Compress for the smallest final marked-up file.