Forty PDFFree beta

FOR RECURRING REPORT HANDOFFS

One report batch.
The right copy for each recipient.

Your client needs the public update. Your internal team also needs the planning details. Prepare both PDF copies from the same originals, review them independently and keep the workflow for the next report.

Try two complete report batches →Use your own PDFs

Free beta · No account · Browser-local processing. The example files and people are fictional.

CLIENT COPY — THREE INCLUDED PAGES

Cover + report

Public report updates stay visible.

Chosen contact-name, email and internal-note areas are removed.

Review all three prepared pages for this recipient.

INTERNAL COPY — TWO INCLUDED PAGES

Report only

The cover is excluded.

Contact details and planning notes stay visible in this example.

Review both pages independently; client review does not carry over.

Try the first complete handoff

  1. Preview the example delivery setup. The sample starts with a cover PDF and a two-page report. Explicitly map “Cover sheet” and “Report” to these files, preview both recipient copies and inspect the proposed marks. A preview does not change the workspace.
  2. Create the recipient copies deliberately. Confirm the preview, then create the new handoff. Client has three pages and selected redactions; Internal has two pages with no marks. Every page starts unreviewed. Save the setup on this device only if you want to reuse it.
  3. Review each displayed page. “Handoff review” shows every version’s progress and links to its included pages. “Review all versions” opens the first unreviewed page. Check visible content and marks, then approve that page. Navigation continues through the remaining pages and versions. You can pause at any time; choosing a page or version manually also pauses it.
  4. Check and inspect one complete delivery. “Prepare all versions” opens delivery checks without approving anything. Confirm your review and build one ZIP, with one combined PDF per version or a PDF per source in each version. Inspect both actual prepared copies before downloading. If any copy fails, no partial delivery is offered.

Run the next batch with new files

Use “Load next synthetic batch” after the first handoff. Discarding unsaved work needs your confirmation. Reopen the saved setup or preview the example again, explicitly map the new cover and report, and change the Client finding term from Jordan Lee to Morgan Chen. Inspect the new previews before creating the handoff. Every new page needs a new review; old review flags and old text-match rectangles are not reused.

A reusable setup keeps source roles, included original pages, order, rotations, fixed areas and optional finding rules. It excludes original PDF bytes, source filenames and review state. Your own labels and finding terms may still be private. Source page counts and proportions are checked, but matching proportions do not prove the content stayed in the same place.

Send the intended copy

Default ZIP names use version numbers, such as “01-version.pdf” and “02-version.pdf.” The file list and prepared preview identify each version locally. Choose version labels or original source names in filenames only when suitable to share; those choices reset when you close the export review. Keep the full multi-version ZIP for yourself and send each recipient only their intended PDF.

A workspace supports up to five versions, 100 included pages per version and 30 MB of combined originals. A prepared ZIP is limited to 100 PDFs and 200 MB. Combine within each version, choose standard quality or export versions separately when needed.

Keep review and storage deliberate

The tool removes areas you mark; progress counts and navigation do not detect private information or certify the result. Check text, images and scans yourself. Image-only exports lose text search, selection, accessibility tags, valid signatures, links, forms and attachments. Unmarked visible content remains visible.

PDFs are processed in your browser without uploading documents. Saving a project deliberately keeps original unredacted files and all versions in unencrypted browser storage, which your browser can clear. Keep originals separately and use a trusted device. Setup exports can contain private labels or terms; share them carefully.

Tell us how the real handoff went

After trying your workflow, share a short, optional note: what you were preparing, where you finished or got stuck, and whether you would use it again. No documents or private text are needed. The workspace also offers local counts that you can enable and share deliberately; nothing is sent automatically.

The current beta is free and has no checkout or subscription. If a step fails, describe your browser and the step to support using fictional files; do not email sensitive reports. We aim to reply within two working days.

Try the two-batch workflow →Contact support