Remove private contact blocks before publishing a PDF set.

For the first comparison, queue alpha, beta and different. Open alpha, mark its whole tinted contact block and choose Apply current preset. The matching pair exports; different is recorded as failed and has no PDF in the ZIP. Each included output still needs review.

Download corrected alpha PDF · Local record

Download corrected beta PDF · Local record

Scroll sideways to inspect the mapping.

Choose Both under Verification certificates to include the summary and per-file records. Compare the public workshop ID with the source filename, local fingerprint and archive name. Individual output downloads in the editor contain the same bytes as their ZIP entries. Records can contain removed text and source names: review before sharing. They are local checks, not independent privacy certification.

Download fictional missed-contact PDF

Download corrected moved-contact PDF

Use Edit each file when positions differ or need individual review. The actual reviewed ZIP below was produced with separate marks for alpha, beta and shifted through Save + next. All three known contact blocks are removed; each file keeps its own public content.

Clean metadata only also leaves the visible contacts and their stored text intact in these Standard Clean inputs, even with a current mark drawn. Choose a redaction workflow to apply marks. Maximum Clean rebuilds PDFs without the original text layer: inspect the visible pages, because an empty search result is not proof that a contact was covered.

1. Queue a manageable, reviewed set

   Open Batch queue and add the PDFs. Inspect every page for contacts, repeated details and extra pages. Group only files whose content genuinely aligns. Matching dimensions, crops and rotations establish geometry compatibility, not matching words or privacy coverage.

2. Build the mark on a representative file

   Choose Open, then cover the complete contact block with a solid rectangle and a margin. Add centered redaction plus Width, Height, X and Y provides a keyboard/phone alternative to dragging. For this fictional template’s 900 × 630 preview, use Width 804, Height 138, X 48, Y 168. These coordinates apply to this sample only.

3. Choose reuse or per-file editing

   Return to Batch queue. Apply current preset reuses the current marks; choose it only after checking all target positions. Edit each file uses Start guided queue, then Save + next / Save + finish queue to retain each file’s own edits. For shifted in this sample, Y is 450; its other numeric values stay the same.

4. Run and review before distributing

   Export, then choose Review output beside each PDF. The local view renders the actual bytes used by that output’s download and ZIP entry; no editor marks are overlaid. Use Output page to inspect every page and Output zoom for details. Confirm that private contacts are covered and public topics, times and rooms remain correct. Expand Check known text (optional), then enter an exact name, email or reference you already know. For the fictional shifted file, try DEMO-CONTACT-SHIFTED. A retained-text match identifies pages to revisit; metadata matches are reported separately. No match or no extracted text does not prove removal: also download and reopen every saved file. Standard may preserve public text when native export is verified; Maximum or a fallback loses the original text layer. Failed items have no PDF output.

5. Check completeness and keep the newest ZIP

   Match every intended source to its archive entry. Cancelling finishes the current file, then produces only the completed subset; a partial ZIP is not the whole set. Changes to queue, marks, mode or profile require a fresh run. Keep the page open while editing: clear, reload or close loses active queued edits, while recent originals may remain in local browser sessions.

The known-text check is case-sensitive after Unicode and whitespace normalization. It checks the current output only, adds no marks and clears when the review closes or output changes. Scans, fragmented text and unusual font encodings can cause misses. Check every page visually, including public content; this is not automatic contact detection or complete privacy certification.

1. Download and inspect the fictional pair. Download fictional schedule A PDF and download fictional schedule B PDF. All names, references and contacts are invented. Open A with the ordinary file picker; keep your originals separately.
2. Redact the private block before naming. For this pair only, use Add centered redaction and set X 45, Y 247.5, Width 810, Height 135 in the 900 × 630 preview. The mark covers the printed identifier and contact, keeping the public time and notebook instruction. Inspect B to confirm the position matches.
3. Export and review both current files. Open Batch queue, add A and B, select Apply current preset and choose Apply preset + export ZIP. Review output renders each actual PDF. Check both source mappings and all private/public areas; download and reopen the files too. Geometry alone does not prove coverage.
4. Choose labels and records deliberately. In Step 4, set Batch download names to Numbered names. For a ZIP containing documents without records, set Verification certificates to None. Selected summaries and detailed records retain source names. Individual batch downloads use the same numbered labels; originals and local history retain original names.
5. Extract the saved ZIP and check the whole pack. Confirm file-001.pdf is schedule A at 10:00 and file-002.pdf is schedule B at 14:00. Filters retain positions from this run; stopped runs contain only finished outputs. A new or changed queue can have different positions. With records set to None, no ZIP is downloaded if a filter has no documents. Choose a record option deliberately when issue details are needed.

Inspect the actual ZIPs, not just the outer archive label.

Microsoft’s archive instructions cover ZIP creation, renaming and extraction. Sejda offers PDF filename patterns; renaming is not exclusive to Blivion. The checks here concern these fictional files, their actual output bytes and explicit record choices. Continue with the sharing checklist.

Redax’s template documentation describes applying positioned marks to similarly formatted documents and verifying their locations. Nitro’s manual redaction guide describes repeating marks across pages, then applying them. Those published instructions are separate from Blivion’s own downloaded-output proof above.

These examples establish a small fictional workflow, not universal format support, automatic contact discovery, signature preservation or acceptance by a recipient. Practical capacity depends on file complexity and browser memory. For native/flattened tradeoffs see the PDF redaction hub; for individual scans, use the no-selection scan guide.