Mac PDF review checklist for text and colors

The short answer: review the PDF in Preview first, confirm whether the text is selectable, extract text locally only when the text layer is usable, sample colors from the rendered page when visual evidence matters, and save one small folder with the source PDF, notes, and any exported text. Do not trust a copied paragraph or sampled color until you know where it came from.

Disclosure: I build TeenyApps, including TeenyColor for screen color sampling and TeenyTool for local utilities such as PDF to Text. My bias is toward local Mac checks. The baseline is still Preview, Finder, and a careful note.

This guide is narrower than the Mac research downloads checklist. That page covers downloaded sources as a batch. This one starts after the PDF is open and you need to decide what text, colors, or files should survive the review.

If the review target is a Markdown draft, README, release note, or internal spec instead of a PDF, use the Mac document review checklist for Markdown and monitors so the local preview, source notes, and display state stay attached to the decision.

PDF review decision table

01Confirm whether the PDF has real text

Open the PDF in Preview and try normal text selection before using any extractor. Apple documents Preview text selection as a direct copy workflow: choose Text Selection, drag over the text, then copy it. If that works cleanly, you probably have a usable text layer.

If text cannot be selected, do not force the workflow. Apple lists several reasons: the Text Selection tool may not be active, the PDF may require a password, or the document may not contain selectable text. Many scanned PDFs are image-only pages. A text extractor cannot invent a text layer unless it includes OCR, and TeenyTool's current PDF to Text view is not an OCR tool.

For review work, write down which kind of PDF you have: selectable text, restricted text, scanned image, or mixed. That one note prevents bad quotes later.

02Extract local text only when it helps

Copying one paragraph in Preview is faster than exporting a whole document. Use a local extractor when you need to search a long PDF, move text into a note, compare page sections, or hand a plain-text copy to someone who should not dig through the original file.

TeenyTool includes a PDF to Text utility. The homepage lists PDF to Text under Files & PDF, and the local Swift source uses PDFKit: it opens a PDFDocument from the selected file, reads each page's string when available, shows the page count, lets you copy all extracted text, and exports either .txt or a minimal .docx. It also rejects non-PDF files before extraction.

That is useful for searchable PDFs. It is not a promise that tables, columns, footnotes, hyphenated line breaks, or scanned pages will come out perfectly. Check the text against the PDF before quoting it.

03Sample PDF colors from the rendered page

PDF colors can mean different things depending on the question. If you need production source values, use the design or PDF production tool that owns the file. If you need review evidence for what a person sees, sample the rendered PDF page on your screen.

TeenyColor is built for that visible-pixel job. Its homepage describes a Mac menu bar color picker that auto-copies in nine formats, keeps local history, and checks WCAG contrast. The source uses Apple's NSColorSampler, converts the sampled color to sRGB, stores local history, and copies your selected format to the macOS pasteboard.

The practical rule is simple: zoom the PDF to the size you will review, sample a flat part of the color, and repeat the pick if antialiasing, compression, or a tiny chart edge might have changed the pixel. For exported image issues, use the TeenyColor guide to checking image color shift on Mac.

04Check contrast only when the color carries text

A PDF may contain decorative colors, brand colors, chart fills, UI screenshots, and actual text. Do not turn every sampled color into an accessibility audit. Use contrast checks when someone must read text, labels, captions, table values, or UI copy from the PDF.

WCAG's contrast guidance is specific: normal text generally needs at least 4.5:1 contrast, while large text has a 3:1 threshold. TeenyColor calculates contrast against white and black for each picked color. TeenyTool also has a separate contrast checker when you need foreground and background pairs.

If a sampled chart color is only a legend fill, write that down. If it is text, sample both the foreground and background from the rendered PDF and record the ratio with the page number.

05Save one review bundle

When the PDF review is done, keep the result boring. Create one Finder folder with the source PDF, extracted text if you made it, color values if you sampled them, and one short note explaining what was accepted, rejected, or needs follow-up.

A useful review note can be plain:

1. PDF name and source.
2. Pages reviewed.
3. Text layer status: selectable, restricted, scanned, or mixed.
4. Extracted text file name, if any.
5. Sampled colors with page numbers and purpose.
6. Open questions or files to delete after the handoff.

If the review leads to an image handoff, pair it with the broader Mac image handoff checklist. If it leads to a public upload, use the Mac file upload checklist before sending files.

Five-minute Mac PDF review routine

1. Open the PDF in Preview.
2. Try text selection on a normal paragraph.
3. Label the PDF as selectable, restricted, scanned, or mixed.
4. Extract text locally only if the text layer is good enough to reuse.
5. Check extracted text against the PDF before quoting it.
6. Sample visible PDF colors only when color evidence matters.
7. Record page numbers for copied text and sampled colors.
8. Save the source PDF, extracted text, and notes in one review folder.

Common questions

What is the safest way to review a PDF on Mac?

Start in Preview, confirm whether the text is selectable, extract text locally only when the text layer is usable, sample colors from the rendered page when visual evidence matters, then save a small review bundle with the source PDF and final notes.

Why can't I copy text from some PDFs on Mac?

Some PDFs are scanned images, password restricted, or built without a usable text layer. In those cases, normal text selection or PDFKit extraction may return no useful text. Use OCR only when you need it and verify the result.

Should PDF colors be sampled from the PDF file or the screen?

For review evidence, sample the visible rendered page because that is what the reader sees. For source-file production work, use the design or PDF production tool that owns the original color data.

Sources checked

• TeenyColor claims were checked against the TeenyColor homepage and local Swift source for NSColorSampler, sRGB conversion, pasteboard copy, nine output formats, local history, and contrast display.
• TeenyTool claims were checked against the TeenyTool homepage and local Swift source for PDF to Text, PDFKit extraction, page count, copy all, .txt export, .docx export, and unsupported-file handling.
• Apple Support: Select and copy text in a PDF in Preview on Mac.
• Apple Support: If you can't select or copy text in a PDF in Preview on Mac.
• Apple Developer Documentation: PDFDocument.
• Apple Developer Documentation: PDFPage.
• Apple Support: Allow apps to use screen and audio recording.
• W3C WAI: Understanding Success Criterion 1.4.3 Contrast (Minimum).