By PDFKits Team — Published February 19, 2026
TL;DR: The PDF tools for lawyers that matter are true content-stream redaction, e-signature, OCR for scanned discovery, merge for closing binders, and split/compress for court e-filing size limits. Uploading privileged files to cloud services raises an ABA Model Rule 1.6 confidentiality question; PDFKits runs every operation in the browser, so privileged content never leaves the device — and it costs $0 against Adobe Acrobat Pro at $14.99/month.
Legal practice runs on PDF. A mid-sized civil case generates 5,000–50,000 pages of discovery; a transactional matter produces hundreds of executed signature pages; every U.S. federal court accepts filings through CM/ECF in PDF, with PDF/A as the long-term archival flavor. The format problem starts when a file must be modified — redacted, signed, merged, OCR'd. Popular cloud tools such as Smallpdf and iLovePDF upload the file to their servers, and for privileged or work-product material that upload itself triggers ABA Model Rule 1.6(c): a lawyer must make "reasonable efforts to prevent the inadvertent or unauthorized disclosure" of client information. State bar opinions in California, New York, and Florida require due diligence on any cloud vendor touching client data.
Browser-only legal pdf software sidesteps the analysis entirely: PDFKits processes 100% of the file locally, so there is no transmission, no vendor, and no Data Processing Agreement to negotiate. Functionally, it is equivalent to opening the PDF in your local reader.
Best for: litigators, paralegals, solo practitioners, and in-house counsel handling privileged documents on machines where IT blocks new software.
Bates numbering — the sequential per-page identifier stamped on every produced document — remains the backbone of discovery citation. For a Bates numbering PDF workflow without a review platform, add sequential page numbers with a prefix (e.g., DEF000001) across the merged production set, split the set into volumes, and log the Bates range per volume. When a production arrives as image-only scans, OCR it first so the review team can keyword-search across all 80,000 pages; review platforms like Relativity and Everlaw can then index the text layer. Running OCR locally keeps the production within the protective order's distribution limits — no additional vendor's terms of service apply.
| Feature | PDFKits | Adobe Acrobat Pro | Smallpdf | iLovePDF |
|---|---|---|---|---|
| Cost | Free | $14.99/month | $9/month | $48/year Premium |
| Files stay on your device | Yes — browser-only | Yes (desktop) | No — cloud | No — cloud |
| Content-stream redaction | Yes | Yes | Limited | No |
| OCR for scanned discovery | Yes | Yes | Yes (Pro) | Yes (Premium) |
| Bar-rule vendor due diligence needed | No (no vendor) | For cloud features | Yes | Yes |
| Works on IT-locked laptops | Yes, no install | No — install | Yes | Yes |
| Login required | No | Adobe ID | Account-gated | Account-gated |
Desktop tools like Acrobat Pro and Foxit keep files local but require purchase orders, installation rights, and per-seat budgets. For ad-hoc work — one redaction before a deadline, one engagement letter signature — the browser tool removes both the procurement step and the Rule 1.6 vendor analysis.
The ABA Standing Committee on Ethics put it directly in Formal Opinion 477R (2017): lawyers using cloud services must undertake "reasonable efforts" to ensure the service preserves confidentiality. For a public filing being reformatted, a cloud tool is probably fine. For attorney-client communications, work product, settlement drafts, or material under a protective order, the lawyer becomes responsible for the vendor's encryption, retention policy, and breach history. With browser-only processing there is no vendor to vet — the analysis collapses to zero.
Filing a "redacted" PDF that is still searchable. High-profile failures (Manafort 2019, Stone 2019) involved annotation overlays instead of content removal. Always run the three verification checks before filing.
Filing image-only PDFs where PDF/A is required. Some clerk offices reject outright; others flag non-compliance. OCR scanned filings, then validate against the ISO PDF standards your district references.
Using a free e-signature service that retains the executed document. Several "free" services keep copies for audit logs — your engagement letter now lives in a third party's database. Browser-only signing leaves no copy with anyone.
Compressing below legibility to beat ECF caps. Most federal courts cap attachments around 50 MB but allow multiple attachments per docket entry. Use Split PDF instead of crushing image quality.
Flattening a PKI-signed document. Flattening alters signed content and invalidates certificate-based signatures. Flatten before cryptographic signing, never after.
Yes, under the ESIGN Act (15 U.S.C. §§ 7001–7031) and UETA enactments in 49 states; New York uses its ESRA statute. Wills, codicils, and some real-property conveyances are excluded depending on state. For filings, most federal courts accept /s/Name or graphic signatures.
Annotation redaction overlays a graphic; the text remains recoverable by copy-paste or annotation stripping. Content-stream redaction deletes the characters from the page itself. Only the second is forensically defensible, and it is what PDFKits Redact PDF performs.
It varies by district. NextGen CM/ECF prefers PDF/A but accepts standard PDF with extractable text; some districts require PDF/A for sealed filings. Image-only PDFs are widely rejected. When in doubt, file PDF/A-2u with embedded fonts.
Not with PDFKits. The file loads into browser memory and is modified there; no network request carries file content. Verify it yourself: open DevTools → Network, run the operation, and confirm no upload occurs.
Merge the production set in order, apply sequential page numbers with a party prefix (e.g., PLF000001), then split into volumes and record the Bates range of each. Keep an unstamped master so re-productions with different prefixes stay possible.
OCR first to create a text layer, then redact. The redaction removes both the recognized text and a masked region of the underlying image. Verify by searching the output for the redacted string and inspecting the region visually.
Sign PDF supports drawn, typed, and image signatures — sufficient for /s/Name court attestations and most engagement letters. Certificate-based cryptographic signing with revocation checking still requires a desktop tool such as Acrobat Pro.
Use Split PDF in page-range mode. Cut the production into roughly equal ranges (pp. 1–250, 251–500), name each by its Bates range, and file them as separate attachments under one docket entry. Most district courts cap single attachments near 50 MB.
Yes — that is the point. PDFKits runs in any modern browser without installation, so IT-locked firm laptops that block new executables still support the full workflow.
It is discarded. The file existed only in the tab's memory; closing the tab releases it. There is no server log, no temp file, no recovery — which is precisely the property you want for privileged material.
Redact PDF — content-stream redaction for exhibits. Sign PDF — browser-only e-signatures. Merge PDF — closing binders and filing packets. OCR PDF — searchable text for scanned discovery. Compare PDF — catch redline changes between versions. Split PDF — ECF-compliant volumes. Protect PDF — password protection before sharing with co-counsel.