Skip to content
dialegein

PrizmDoc

Accusoft's document viewing and processing APIs, with permanent redaction and AI-assisted PII detection, self-hosted or hosted.

Operated by Apryse

Visit PrizmDoc

Opens the vendor's own site.

Jobs covered

Open a task to see exactly what the vendor documentation supports.

View Browse all view tools

viewing documents with PrizmDoc, where the HTML5 Viewing page for v14.10 documents the viewer REST endpoints that get a page count, page attributes, SVG or image page renders, page tiles and thumbnails, and the page text for a range, and the overview says the HTML Viewer control lets users view, search, annotate, redact, print and download documents in many different file formats without leaving the application or installing custom software, with an option to use Microsoft Office for high-fidelity rendering of Word, Excel and PowerPoint files, support for viewing and searching large documents with thousands of pages, pre-converted viewing packages for faster loading, and a customizable stock UI and JavaScript API; the system requirements name the current and one version back of Android Chrome, Microsoft Edge, Mozilla Firefox and Safari, and the scope is the browser viewer and its documented operations, not a native application, with no rendering-fidelity guarantee beyond the options the vendor names

Edit Browse all edit tools

editing and annotating documents with PrizmDoc, where the Annotation API page says annotations are supported for 50+ file types including PDF, Office and image formats, that revisions are tracked through layers and annotations can be managed, merged and toggled on and off, that the system preserves the original documents, and that annotations can be removed from or burned into final files while preserving underlying content; the template-based forms page documents creating text fields directly in the viewer, adding signatures, initials, text boxes, dates and checkboxes, marking mandatory fields, assigning roles, controlling alignment, applying input masks and setting tab order; the form-field detection page documents automatic detection of form fields from AcroForm documents and from scanned TIFF or bitmap documents including underscore and low-dash lines, form field rectangles and checkboxes, manual addition where detection falls short, field types of text input, check box, date, initial and signature, and populating fields with customer data and extracting user-filled data, with the detector an add-on for self-hosted and included with PrizmDoc Cloud-Hosted; the watermark page documents text, diagonal text and image watermarks with font, placement, opacity and font size.

The scope is the documented annotation, form and watermark work, makes no claim of in-place editing of existing text or layout, and keeps redaction with the record's redaction field rather than this job

Extract Browse all extract tools

extracting text with PrizmDoc, where the HTML5 Viewing page for v14.10 documents a viewing-session Text endpoint that returns currently available text and text metadata for a range of pages and notes that it is designed to support the viewer, and explicitly directs anyone who wants to programmatically extract text from a document to the Search Contexts API, namely POST /v2/searchContexts and GET /v2/searchContexts/{contextId}/records; the large documents page documents server-side search for large documents and pre-converted viewing packages, and the advanced search feature page is listed as the search capability; the scope is the documented Search Contexts text extraction and the server-side search path, makes no OCR claim because OCR is the separate ocr job, and makes no structured-data, table or field extraction claim beyond form data described under edit

Convert Browse all convert tools

converting documents with PrizmDoc, where the Content Conversion Service page documents a REST conversion API that converts files from a variety of input formats to several common output formats, with POST /v2/contentConverters starting a conversion and GET /v2/contentConverters/{processId} reporting status, supporting output formats of jpeg, pdf, png, svg and tiff, plus docx only when the source is PDF and xlsx only when the source is XLS or CSV, with the docx and xlsx destinations requiring the Microsoft Office rendering mode and its feature in the licence key; multiple input files are supported only when the destination is pdf or tiff, the pages option is likewise only supported for pdf or tiff destinations, a password option and page rotation are documented, and the overview says conversion covers Office, PDF, Email, HTML, TIFF, PNG, JPEG, CAD and many other kinds of documents to PDF, TIFF, PNG, JPEG or SVG, that multiple input documents can be merged, that headers, footers and watermarks can be applied, and that a non-searchable PDF or TIFF can be converted into a visually identical PDF that supports full-text search; the scope records those directions and the Office-rendering licence dependency, and makes no fidelity guarantee

Sign Browse all sign tools

electronically signing documents with PrizmDoc, where the eSignature feature page documents allowing users to electronically sign and date documents inside the application without printing and scanning, creating a freehand signature by drawing with a mouse, stylus or finger or a text signature by typing in a text box, and saving signatures for reuse across multiple documents and sessions within the same browser, with the demo showing the e-sign workflow; the scope is electronic signatures as documented on that page, with no certificate-based digital signature, timestamping, long-term validation or audit-trail claim, and no claim of a full agreement workflow

OCR Browse all ocr tools

running optical character recognition with PrizmDoc, where the Advanced OCR API page documents OCR of full pages or user-defined zones, image orientation information and recognition of images in any orientation including multi-page images, location and confidence information for each character, segmentation, predefined character sets, rejection of characters whose recognition fails, minimum confidence values, expected data type and expected recognition language, alternate character results with confidence values, and regular expressions or data validation lists to refine results; the page states robust language support for over 60 languages and lists them, with Chinese Traditional, Hong Kong Traditional and Simplified, Indonesian, Korean, Japanese, Thai and Vietnamese provided by an additional Asian Language OCR add-on; the scope records the 60-plus language statement and the Asian add-on as the vendor's claims, makes no accuracy figure claim, and does not claim handwriting or structured table extraction

Where your files are processed

Mixed - depends on version and feature

The vendor's own documentation separates them. On the device: PrizmDoc Server deployed by the customer. On their servers: PrizmDoc Cloud hosted by the vendor. A single answer for the whole product would be wrong for one of them.

It depends on the deployment. A customer-hosted PrizmDoc server processes documents on infrastructure the customer controls, which is not browser-local processing, while the vendor cloud processes them on the vendor’s side with its own region and retention terms.

The United States summary applies to the cited hosted service rather than to every deployment, and the temporary work-file lifetime is separate from whole-service retention. AI and third-party processing is a feature-specific documented path that needs a direct source rather than being treated as proof that all deployments send documents to a particular provider.

What it does

PrizmDoc is Accusoft's document handling platform for content management systems, sold as a set of REST APIs and an embeddable HTML5 viewer rather than as an application. It displays PDF, Office, CAD and DICOM files inside somebody else's product, and around that core sits the processing work an ECM or eDiscovery platform needs: conversion and merging, annotation, watermarking, form filling, eSignatures, document comparison, server-side search across large documents, and redaction.

The redaction API is the notable one, because Accusoft documents it as permanent removal rather than a black box drawn over live text, and the AI add-ons built on IBM watsonx.ai extend that to detecting and redacting personal data. Deployment is explicitly a choice between self-hosted, private-cloud and vendor-hosted.

Best for

Teams building or extending a document management, eDiscovery or claims system who need viewing and processing to live inside their own application rather than send users to a separate tool. It is aimed at large regulated document volumes - legal, financial, insurance and government records - and the redaction and search APIs are the parts that matter most in those settings.

A reader who wants to open one PDF should look at a viewer instead.

Worth knowing

Accusoft has been acquired by Apryse, announced on the vendor's own site, so the company selling this is no longer independent - worth knowing before a long-term commitment, and worth checking what the acquisition means for the roadmap and for existing licences, which this record does not establish. There is no published price anywhere: every path is a contact form or a trial download, so budgeting starts with a conversation.

Where documents are processed depends on which of the three deployment models you choose, and the choice is material - a self-hosted installation keeps files on your infrastructure while a vendor-hosted one does not, and Accusoft's own answers cover only its hosted option: its FAQ states 'Our PrizmDoc Cloud environment is hosted on Amazon Web Services (AWS) running in us-east-1 (Virginia).' and the PrizmDoc Server 'Work Files' topic states 'All work files are temporary and, by default, will be deleted 24 hours after creation.' (both read on 2026-09-25), while no comparable region or retention commitment is published for a customer's own Self-Hosted or Private Cloud deployment, and the 24-hour figure is the default lifetime of intermediate work files, exposed in the same topic as a MinSecondsAvailable request parameter, rather than a whole-service retention policy for every document.

The AI features are built on IBM watsonx.ai, which means a third party is in the processing path for those add-ons specifically. Redaction layers can be saved and edited before being applied, which is a workflow stage rather than a statement that applied redactions are reversible, but the distinction is worth understanding before relying on it.

And the advanced capabilities are add-ons rather than included features, so the price of the base product is not the price of the product you end up needing. The official download page offers 300 free cloud evaluation transactions, which is evaluation access rather than an ongoing free tier.

Not every advanced capability is separately priced in every deployment: the vendor FAQ says available Cloud features are included in transaction and subscription purchases, while self-hosted options may need specific licences. Applied redaction is vendor-documented and separate from editable pending annotations, and prices are recorded as not established from the cited pages rather than as absent everywhere.

Details, and where each comes from

Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.

Versions covered
API · Self-hosted · Web · Windows · Linux
Website
accusoft.com
Requires an account
Not verified
Free tier
Not verified
Watermark on the free tier
Not verified
Maximum file size
Not verified
Batch processing
Not verified
Data residency
United States
Open source
No
Self-hostable
Yes
Licence
Commercial, quoted rather than published.

Commercial, quoted rather than published. A free trial is offered through the vendor's download centre; the pages read state no licence terms, no per-developer or per-server basis, and no price.

Redaction
Removes the content
Programmatic access
HTTP API · Browser JavaScript
Last availability check
Responded in 206 ms 21 October 2026

Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.

What the redaction verdict rests on

From the vendor's own documentation, read 22 September 2026. Not tested by us.

“Via the REST API (left), perform an auto-redaction process that finds matches of a given regular expression such as a social security number, permanently removes the text, and blacks out the displayed region. The end result is a PDF document with no traces of the text.”

What that does not establish

One of the clearest removal statements in this index, and it is specific where it counts: "permanently removes the text" and "no traces of the text" describe the file rather than the display, and the sentence distinguishes removing from blacking out - "permanently removes the text, and blacks out the displayed region" - which is exactly the distinction the redaction guide exists to draw. Corroborated on the same page by the description of the manual workflow, which offers search-and-redact by term or regular expression, redaction by text selection, rectangle or full page, and redaction reasons.

What it does not establish: that every route through the product is permanent. Redaction layers can be saved and edited before being applied, and the page does not say whether a layer applied and saved without being committed behaves differently.

The claim is about the API's output, and nothing was tested.

https://www.accusoft.com/products/prizmdoc/features/redaction/

What the vendor says

Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded - not that we tested the behaviour, unless the note says we did.

  • “Accusoft has been acquired by Apryse!”

    Checked by us - the source says this Read 22 September 2026

    Present verbatim as a site-wide banner at the top of the page, above the product marketing. It is recorded as a claim because it changes who the reader is dealing with, and because it is the second Apryse acquisition found in two batches - LEADTOOLS was the other, read in the same session, where the vendor's own text announces "its most recent acquisition of LEAD Technologies".

    The banner gives no date and the linked announcement was not followed, so the acquisition is established and its timing is not. owner is set to Apryse so the records group; the intermediate entity is Accusoft Corporation, which the footer gives as "© 1991 - 2026 Accusoft Corporation".

    Standing: Re-read, and the recorded hash was not reproduced

    Check it yourself: the source, the SHA-256, and how we checked
    From
    the text a browser renders
    SHA-256
    826ed225bff6c82b09f00e7d730fa794adde92fe03e11f998c405ca71e2b506b
    Note
    neither the raw response nor a render reproduced the recorded hash (210480 chars, recorded 826ed225bf…)

    How we checked

    https://www.accusoft.com/ rendered in headless Chrome with scripts/render-page.mjs on 2026-09-22 (visible text 4978 bytes) and the banner read from that rendered text. sourceHash is the SHA-256 of that text.

    What this hash proves, and what it does not

  • “Via the REST API (left), perform an auto-redaction process that finds matches of a given regular expression such as a social security number, permanently removes the text, and blacks out the displayed region. The end result is a PDF document with no traces of the text.”

    Checked by us - the source says this Read 22 September 2026

    Confirmed verbatim, and it is the sentence the redaction verdict rests on. It is recorded both here and as the redaction evidence because it is the rare case where a vendor states the mechanism rather than the benefit: the text is removed from the file and the black region is the display of that removal, not a substitute for it.

    The contrast with Sejda in this index is direct - Sejda's own tooltip warns that its whiteout "hides but will not completely remove underlying text" - and having both in one directory is the reason the redaction guide can be useful at all.

    Standing: Re-read and matched byte for byte

    Check it yourself: the source, the SHA-256, and how we checked
    From
    the text a browser renders
    SHA-256
    7adc168d0d35791d15f5f601fcccbf910142070350c2c54b061fbda6072e85e8

    How we checked

    https://www.accusoft.com/products/prizmdoc/features/redaction/ rendered in headless Chrome with scripts/render-page.mjs on 2026-09-22 (visible text 4422 bytes) and the claim checked against that rendered text. sourceHash is the SHA-256 of that text.

    What this hash proves, and what it does not

  • “PrizmDoc provides secure document viewing and processing capabilities for ECM solutions, which are easily embedded into your application.”

    Checked by us - the source says this Read 22 September 2026

    Confirmed verbatim, and corroborated by the rest of the page: the API grouping is named as "Viewing, Conversion and Annotation", the supported formats are given as "Adobe PDFs and Microsoft Office files to CAD and DICOM", and the viewer is described as a customisable HTML5 UI. "Easily embedded" is the sort of phrase that means nothing on its own; what makes it checkable here is that the product is an API and a viewer component rather than an application, so the integration claim is a description of the delivery model.

    Nothing about the difficulty of the integration was tested.

    Standing: Re-read and matched byte for byte

    Check it yourself: the source, the SHA-256, and how we checked
    From
    the text a browser renders
    SHA-256
    2ad27c9815ee0f0498fffb26a870a1c80df5df76956743ce0cc37317b3bb7986

    How we checked

    https://www.accusoft.com/products/prizmdoc/ rendered in headless Chrome with scripts/render-page.mjs on 2026-09-22 (visible text 4119 bytes), read together with the home page (4978 bytes) and the redaction feature page (4422 bytes). sourceHash is the SHA-256 of the product page text.

    What this hash proves, and what it does not

Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked - it is not a judgement about anyone.

Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.

Visit PrizmDoc Report a problem

Related reading

How this record was put together

Editorial review.
No editor has signed this record off. That is not the same as nothing having been checked, and the lines below say what has.
Source reading.
3 claims taken from the vendor's own pages, read between 22 September 2026 and 22 September 2026.
Website availability.
The vendor's site was last checked on 21 October 2026.
Behaviour testing.
We have not run this tool ourselves, so everything here rests on the vendors’ own pages.

Sources: accusoft.com, read 2026-09-22 with headless Chrome: the home page (visible text 4978 bytes), the PrizmDoc product page (4119 bytes) and the PrizmDoc redaction feature page (4422 bytes), including the deployment comparison table and the included-versus-add-on feature lists. Re-read on 2026-09-25 for the residency, retention and privacy questions: https://www.accusoft.com/faqs/where-is-your-prizmdoc-cloud-environment-hosted/ ('Our PrizmDoc Cloud environment is hosted on Amazon Web Services (AWS) running in us-east-1 (Virginia).'); https://help.accusoft.com/PrizmDoc/latest/HTML/work-files.html ('All work files are temporary and, by default, will be deleted 24 hours after creation.'); and the privacy notice at https://www.accusoft.com/company/legal/privacy/, dated May 29th 2026 and carrying a '7.3 RETENTION OF PERSONAL DATA' section. Vendor documentation, not independently tested; no trial was downloaded, no API was called and no document was redacted.