--- title: "Choose the right digital signature workflow" canonical_url: "https://www.nutrient.io/guides/dws-processor/developer-guides/choose-the-right-digital-signature-workflow/" md_url: "https://www.nutrient.io/guides/dws-processor/developer-guides/choose-the-right-digital-signature-workflow.md" last_updated: "2026-07-09T00:00:00.000Z" description: "Compare Web SDK standalone, Document Engine, and DWS Processor API for certificate-based PDF signing." --- # Choose the right digital signature workflow Digital signatures use certificates and cryptographic signing to protect a PDF’s integrity and establish signer identity. Choose a signing path by deciding who runs the signing. You can provide your own implementation, operate a signing service with Document Engine, or use Nutrient’s managed service through DWS Processor API. ## The same signing goal across products | Setup | Signing workflow | When to use it | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- | | Web SDK standalone | Web SDK prepares the PDF and can sign with certificate and private-key material supplied in the signing data, or call a signing callback when you use a separate signing implementation or service. Web SDK reloads the signed document; your app is responsible for saving or persisting the resulting document if it needs to retain it. | Use this when you want to sign in the browser with supported key material or integrate your own signing service. | | Web SDK + Document Engine | Web SDK can use Document Engine’s digital signatures API. Document Engine orchestrates the signing workflow and calls a separately configured signing service, which performs the cryptographic operation. Document Engine can also sign documents it manages. | Use this when you want self-hosted signing infrastructure and control over the signing service, certificates, and deployment. | | Web SDK + DWS Processor API | Web SDK uses DWS Processor API’s hash-signing workflow to send the signing hash and supported signature parameters to the API. The integration requires the API’s supported authentication and configuration. | Use this when you want Nutrient’s managed digital-signing service rather than operating your own signing service. | ## How to choose the right signing setup Use **Web SDK standalone** when you want to sign with supported certificate and private-key material in the signing data. Alternatively, use a callback to integrate a separate signing service or implementation. Your app must save or persist the resulting document if it needs to keep it. Use **Web SDK + Document Engine** when you already operate Document Engine or want a self-hosted backend and signing service. Document Engine orchestrates the workflow; the separately configured signing service performs the cryptographic operation. Document Engine’s digital signatures API is distinct from ordinary document viewing and persistence. Use **Web SDK + DWS Processor API** when you want managed certificate-based signing through DWS Processor API’s hash-signing workflow. Follow its supported authentication and configuration requirements. ## Keep electronic and digital signatures distinct An electronic signature can be a visual mark or record of a person’s intent to sign. A digital signature is certificate-based cryptographic data that can be validated to check document integrity and signer identity. They’re related workflows, but not interchangeable capabilities. Check the relevant product and license documentation for electronic signature UI availability. ## Typical decision questions 1. Do you need a certificate-based digital signature or an electronic signature mark/workflow? 2. Where will the private key and cryptographic operation live: your browser, your signing service, Document Engine’s configured signing service, or DWS Processor API? 3. Do you want to operate and secure signing infrastructure yourself or use a managed signing service? 4. Does the document need to remain in your infrastructure, be managed by Document Engine, or stay client-side during hash signing? ## Guides by product - **Web SDK** - [Digital signatures overview](https://www.nutrient.io/guides/web/signatures/digital-signatures/overview.md) - [Sign a PDF in the browser](https://www.nutrient.io/guides/web/signatures/digital-signatures/signature-lifecycle/sign-a-pdf-document.md) - [Sign through Document Engine](https://www.nutrient.io/guides/web/signatures/digital-signatures/signature-lifecycle/sign-a-pdf-document-document-engine.md) - **Document Engine** - [Document Engine signatures overview](https://www.nutrient.io/guides/document-engine/signatures.md) - [Document Engine signing lifecycle](https://www.nutrient.io/guides/document-engine/signatures/signature-lifecycle/signature-lifecycle-overview.md) - [Signing service architecture](https://www.nutrient.io/guides/document-engine/signatures/architecture-diagram.md) - **DWS Processor API** - [Sign through DWS Processor API](https://www.nutrient.io/guides/web/signatures/digital-signatures/signature-lifecycle/sign-a-pdf-document-dws.md) - [DWS Processor API authentication](https://www.nutrient.io/guides/dws-processor/developer-guides/authentication.md) --- ## Related pages - [API overview](/guides/dws-processor/developer-guides.md) - [Authenticate your requests](/guides/dws-processor/developer-guides/authentication.md) - [Choose the right Build API and server-side assembly workflow](/guides/dws-processor/developer-guides/choose-the-right-build-api-and-server-side-assembly-workflow.md) - [Choose the right stored-document processing and export workflow](/guides/dws-processor/developer-guides/choose-the-right-stored-document-processing-and-export-workflow.md) - [Build API workflows](/guides/dws-processor/developer-guides/combine-workflows.md) - [Deployment options](/guides/dws-processor/developer-guides/deployment-options.md) - [Troubleshooting errors](/guides/dws-processor/developer-guides/errors.md) - [PDF generation](/guides/dws-processor/developer-guides/pdf-generation.md) - [Performance](/guides/dws-processor/developer-guides/performance.md) - [Web SDK integration](/guides/dws-processor/developer-guides/web-sdk-client.md)