The short answer: annotation means marking up the page itself — highlights, margin notes, arrows, and stamps. Open the PDF in PDFEdit Studio, use the highlight, text, draw, shape, and stamp tools, then export. Your markup becomes part of the PDF.
What "annotate" really means on a PDF
People say "annotate" but mean different things: highlight key passages, scribble questions in the margins, circle problems, stamp a status, collect feedback. The common thread is visible markup on the page that communicates with the next reader.
One honest note up front: PDFEdit Studio doesn't have threaded comment bubbles or sticky notes. Instead, you annotate directly on the page — a yellow highlight on the clause, a text note in the margin saying "confirm this figure," a red arrow pointing at the problem. For review workflows, on-page markup is usually clearer anyway: the comment sits exactly where it belongs.
The five markup tools and when to use each
Highlight (Hi-Lite). Drag over text to mark it. Use it for the passages that matter — the number in the report, the clause under dispute. Studio caps highlight opacity so the text underneath stays readable.
Text boxes. Your margin notes. "Needs a source," "client approved 2026-09-20," "check against Q3 figures." Keep notes short; a text box isn't an essay.
Draw. Freehand ink for circling, underlining, and quick arrows. Best on touchscreens with a stylus, workable with a mouse.
Shapes. Rectangles, lines, and arrows when you want markup that looks deliberate rather than sketched. Arrows are the underrated hero of document review — they connect a margin note to the exact word it refers to.
Stamps. "DRAFT," "APPROVED," "CONFIDENTIAL," "REVIEWED" — one click, instant status. Stamps live in the toolbar and place like any other layer.
A review workflow that actually works
1. First pass: highlight only. Read through and highlight everything that needs a decision or a second look. Don't write anything yet — you're mapping the territory.
2. Second pass: notes and arrows. Go back through the highlights and add text-box notes. What needs to change? What's the question? Draw an arrow from the note to the exact clause.
3. Stamp the status. Put the document's state on the cover page — DRAFT for review, a date stamp, or your initials. Whoever opens it knows instantly where it stands.
4. Export and send. Every layer exports into the PDF permanently. The recipient opens it in any reader — Adobe, Preview, Chrome — and sees exactly your markup. Undo and the Inspector are there while you work, so nothing is final until export.
Tips for markup people can actually read
- Color-code with discipline. Yellow for "look at this," red for "problem," green for "approved." Say the key once in your cover note, then be consistent.
- Keep highlights short. Highlighting whole paragraphs trains readers to ignore your highlights. One sentence, one number, one clause.
- Put notes in the margin, not over the text. Text boxes that cover the original words force readers to move things around. The margin is your canvas.
- Date your review. A "Reviewed 2026-09-23 — DS" stamp turns markup from graffiti into a record.
Annotating on mobile vs. desktop
The workflow above assumes a desktop, but plenty of reviewing happens on phones. The honest comparison:
Desktop wins for long documents: precise text-box placement, easier arrow drawing with a mouse, and the Inspector panel for managing dozens of layers. If you're reviewing a 40-page contract, do it here.
Mobile wins for speed: open the PDF in your phone's browser, highlight with a finger drag, drop quick text notes. Studio's toolbar collapses into a touch-friendly bottom bar with the same tools. It's ideal for "read on the train, mark the three things that matter" reviews.
One practical tip for mobile: rotate to landscape when placing text boxes. The extra horizontal room makes a surprising difference to placement accuracy.
Sharing annotated PDFs: basic etiquette
Markup is communication, and a few conventions keep it professional:
- Identify yourself and the date. A small "Reviewed by DS — 2026-09-23" note on the first page turns anonymous markup into an accountable record.
- One reviewer, one color family — or at least one round of review per exported file. When three people's red highlights interleave, nobody knows who said what. Have each reviewer mark up their own copy, then consolidate.
- Export before sharing, obviously — but also name the file well:
contract-DS-review-2026-09-23.pdftells the recipient everything.contract-final-v7.pdftells them nothing. - Keep your layered master. Export a flattened copy for sharing, but keep the Studio session's editable version until the review round closes. Requested changes to wording are trivial before export and annoying after.
Export settings that matter
When the review is done, the export is the deliverable — get it right:
- Export at full quality. Markup is vector layers; there's no reason to downsample. If the tool offers quality options, keep them high — your highlights and notes should print crisply.
- Flatten review copies. Once a review round closes, flatten the shared copy so nobody can silently delete your comments. Keep the layered master until the round is truly over.
- Check the file on another device. Open the exported PDF on your phone or in a different reader before sending. Layer rendering is standardized, but a 10-second sanity check catches the rare surprise.
- Mind the file size for email. Heavily annotated scans can get large. If it won't attach, compress — annotations survive compression fine.
Do it with PDFEdit
PDFEdit Studio gives you the full markup set — text, highlight, draw, shapes, stamps, plus signatures when the review ends in approval — free, in your browser, with your file never leaving your device. For fixing the document's own wording rather than commenting on it, the Studio's in-place text editing has you covered too.
