Enterprise-Grade PDF Redaction for Regulated Industries
Enterprise-grade PDF redaction permanently removes underlying text and image content instead of masking it. Mark content in the browser with the Web SDK, redact on your own infrastructure with the Server SDK, and keep every document in your environment. Four properties define it: irreversible removal, reviewer approval, verification, audit trail.
What Enterprise-Grade Redaction Actually Means
Enterprise-grade describes behavior you can test, not a customer profile. A PDF redaction library earns the label when it meets four properties":
Irreversible removal:
The content is deleted from the file, not covered by a shape.
Reviewer approval:
A person confirms what gets removed before the removal is applied.
Verification:
Someone can confirm the removed content is gone from the output.
Audit trail:
The release leaves a record of who marked and applied what.
Apryse performs the removal on the Web SDK and the Server SDK. Your application owns the approval decision and the audit record. The next four sections cover each property.
Support Matrix: Web SDK and Server SDK
True Irreversible Removal, Not Masking
A black rectangle drawn over text is a mask. The text stays in the file, where anyone can search or copy it. True irreversible redaction deletes the underlying text and image content, and on the Server SDK it covers vector content too. The change is permanent once applied, so keep the unredacted original in your own storage.
Reviewer Approval Before Redactions Are Applied
Reviewers mark text and regions for redaction in the WebViewer UI. Redaction becomes permanent only when it is applied, so your application decides when the apply step runs. Your workflow routes the approval, and WebViewer is where each reviewer works.
Search and redact finds content by text string, ambient string, wildcard, or RegEx, such as SSNs and credit card numbers.
Verification: Proving the Content Is Gone
Redaction outputs a modified PDF with the content destroyed, not hidden.
Hidden data is a separate problem. Sanitization strips metadata, embedded scripts, form data, and hidden layers, and it ships in the Server SDK base package. Redaction removes what you can see, and sanitization removes what you cannot. Before release, see how to verify a redacted PDF.
Audit Trail for a Released Document
Your application writes the audit record. The Web SDK reports annotation changes to your code through the annotationChanged event, and your app logs them in its own store.
Run PDF sanitization before release so metadata and hidden layers leave with the redactions. The compliance redaction process walks through the steps.
Where Redaction Runs: Browser, Server, or Both
Web SDK
WebViewer processes documents in the browser with WebAssembly, and no document content is transmitted to Apryse. Reviewers mark text and regions in the UI. The full API redacts programmatically.
Server SDK
The Server SDK runs inside infrastructure you control and redacts programmatically. It has no viewer UI. To redact documents in bulk, loop over your files in your own code. The Server SDK provides no work queue, job scheduler, or batch orchestration. Run both surfaces when review happens in the browser and volume runs on your servers.
Deployment and Data Control
The Server SDK runs on-premises, in your private cloud, or self-hosted on a cloud VM or container, and it does not call Apryse servers at runtime. Fully offline operation depends on a license configured for it. See on-premises and air-gapped deployment.
The Web SDK processes documents in the browser, wherever you host your app. Apryse holds ISO 27001 certification and a SOC 2 Type II attestation. Both cover the company, not your deployment.
Requirements by Regulated Industry
Financial Services
Statements and loan files carry account numbers, SSNs, and card numbers. Pattern-based search and redact finds them on both surfaces. For a customer example, see how Intralinks secures its VDR offering.
Healthcare
Self-hosted operation keeps PHI inside your environment, and redaction removes content instead of covering it. The SDK supports HIPAA workflows. It does not confer HIPAA compliance.
Government
Public-records releases, such as FOIA responses, remove personal data before publication. The Server SDK runs inside FedRAMP-authorized environments you operate. The SDK itself carries no FedRAMP authorization.
Legal
Disclosure and privilege review release documents that must carry no hidden data. Redaction removes visible content and sanitization removes metadata and hidden layers, so the unredacted set stays in your environment.
Apryse provides the document layer. Your application owns routing, approval, storage, and the compliance program. Browse redaction use cases by industry.
Licensing and What the Add-On Covers
Redaction is an add-on license on both the Web SDK and the Server SDK. Neither base license includes it. Sanitization is the exception to know about: it ships in the Server SDK base package and needs no add-on.
A trial key gives full access to every add-on, so you can test Redaction before you license it. The secure PDF redaction developer guide covers setup. API detail lives in the Web SDK Redaction docs and the Server SDK Redaction docs.
Frequently Asked Questions
Four properties, all testable: the underlying content is permanently removed rather than masked, a reviewer approves redactions before they are applied, the output is verified to contain no recoverable sensitive data, and each release leaves an audit record. Apryse performs the removal on the Web SDK and the Server SDK. WebViewer is where reviewers mark content, and your application owns the approval and the audit record.
Any team whose documents carry sensitive visible content that must be removed before release. The need comes from the document and the regulation, such as GDPR, CPRA, or HIPAA. Redaction is licensed as an add-on to the Web SDK or the Server SDK, and a trial key gives full access to evaluate it.
Yes, in the browser. Reviewers mark text and regions for redaction in the WebViewer UI, and redaction becomes permanent only when it is applied. Your application decides when the apply step runs.
Nowhere, unless you send it. The Web SDK processes documents in the browser and the Server SDK runs inside your infrastructure, so no document content is transmitted to Apryse. The Server SDK needs no internet connection to process documents. By default, it sends limited usage metadata, never document content, and a no-tracking license is available on request.
No, that is Sanitization, a separate capability. Redaction removes visible page content: text, images, and vector regions. Sanitization removes hidden content such as metadata, embedded scripts, form data, and hidden layers, and it ships in the Server SDK base package only. A document released externally needs both when it carries hidden data as well as sensitive visible content.
An add-on license on the surface you use. On the Web SDK, redaction runs through the WebViewer UI and the full API, which needs no separate license, and the constructor needs both fullAPI: true and enableRedaction: true. On the Server SDK, initialize PDFNet before any other call. Operations on the Web SDK also wait for the documentLoaded event.
Manual redaction misses instances, and a black box drawn over text leaves the text in the file. Search and redact finds content by text string, RegEx, or pattern, such as SSNs and credit card numbers, so one rule covers every document. Apryse gives your developers the Web SDK and the Server SDK to build that step into your own application. Redaction is permanent once applied.
Apryse is not a service. The Server SDK redacts documents programmatically inside your own infrastructure, and your code owns the loop over the files. The Server SDK provides no work queue, job scheduler, or batch orchestration.
The Apryse Redaction add-on for the Web SDK and the Server SDK gives developers tools to build redaction into a compliance workflow. It permanently removes underlying text and image content and runs inside your own environment. Apryse holds ISO 27001 certification and a SOC 2 Type II attestation, which cover the company, not your deployment. Redaction supports GDPR, CPRA, and HIPAA obligations but does not confer compliance.
