This HTML page is not optimized for LLM or AI agent consumption. Fetch the Markdown version instead: /guides/document-engine/conversion/choose-the-right-conversion-and-pdf-generation-workflow.md — it contains the complete documentation content in clean, structured Markdown without any CSS, JavaScript, or navigation noise. Choose the right conversion and PDF generation workflow

Choose the right conversion and PDF generation workflow

Markdown version of this page, suitable for AI agents and automation

Conversion and PDF generation overlap, but they start with different inputs. Generation creates a new PDF from content such as HTML, images, or templates. Conversion transforms an existing document or file into another format. Choose a workflow based on the source format, target format, where processing should run, and who will store the result.

The same conversion or generation goal across products

SetupHow it worksWhen to use it
Web SDK StandaloneIn Standalone mode, Web SDK can generate PDFs from images and templates, populate Word templates, and convert supported formats such as Office files in the browser. These workflows aren’t uniformly available in every backend or mode; verify feature licensing and mode requirements. Your app receives or exports the result and owns its persistence.Use this when conversion or generation should happen in a browser and your app controls input delivery and output storage.
Web SDK + Document EngineWeb SDK can send supported processing requests to Document Engine. Document Engine also provides server-side conversion and generation workflows, including converting HTML, Office files, and images to PDF. Processing produces output for your application to save or deliver unless a separate workflow persists it as a Document Engine document.Use this when you need server-side processing under your self-hosted Document Engine deployment, or when browser resources are unsuitable.
DWS Processor APIDWS Processor API accepts inputs and instructions, processes them through its API, and returns an output file. The /build workflow supports PDF generation from HTML and conversion for documented input/output formats. It can combine supported conversions with other documented actions in one request; it isn’t an unrestricted any-format-to-any-format converter.Use this for backend, automated, or batch processing when you want a managed HTTP API and your application handles the output.

How to choose the right conversion or generation setup

Use Web SDK Standalone when you need client-side conversion or PDF generation for a supported workflow. Standalone supports PDF generation from images and templates, Word-template population, and documented conversion tasks such as Office-to-PDF and PDF-to-image. These capabilities aren’t uniformly available across backend modes. Check licensing, browser support, and feature-specific requirements for the formats and workflow you need.

Use Document Engine when conversion or generation must run server-side within your self-hosted Document Engine deployment. It supports workflows such as HTML-to-PDF generation, Office-to-PDF conversion, and image/document conversion. Your application remains responsible for storing or delivering the resulting file unless you use a separate Document Engine document-update workflow.

Use DWS Processor API when your backend needs a managed document-in/document-out processing job. Choose a documented endpoint or /build instructions for the supported source and target formats. You can combine supported generation, conversion, and post-processing actions in a request; your application handles the returned output and its storage or delivery.

Common points of confusion

  • Generation and conversion have different inputs — Generation creates a new PDF from HTML, images, form data, or a template. Conversion starts with an existing file and changes its format or representation.
  • Processing doesn’t imply persistence — Your application must save or deliver a generated or converted output. Web SDK output and processing API responses don’t automatically replace a source file or create a managed document. Only a separate persistence workflow does that.
  • Feature coverage varies by product and mode — Input/output formats, options, browser support, and licensing differ. Verify the relevant product guide before choosing a workflow.
  • PDF/A and PDF/UA are specialized outputs — Choose them when archival or accessibility conformance is required, not simply as a general-purpose PDF conversion target. Follow the product-specific conformance guide and validate the resulting file as required.
  • Conversion fidelity depends on the source and settings — Fonts, layout, markup, form fields, and source-file features can affect output. Test with representative documents and use the conversion options documented for the chosen product.

Typical decision questions

  1. Are you creating a new PDF or converting an existing file?
  2. What are the input and required output formats?
  3. Should processing run in the browser, on your Document Engine deployment, or through a managed processing API?
  4. Does the workflow need to combine conversion with page edits, OCR, password protection, or another processing action?
  5. Who stores and delivers the result, and does it need to become a DWS-managed or Document Engine document?
  6. Do you require PDF/A or PDF/UA conformance, and how will you validate the output?

Guides by product