C# Print PDF: Step-by-Step with iTextSharp and PdfiumViewer

Automating PDF Printing in C# — Best Practices and Troubleshooting

Overview

Automated PDF printing in C# lets apps send PDFs to printers without manual interaction — useful for batch jobs, kiosks, server-side reporting, and label/receipt printers. Common approaches: using a PDF rendering/printing library (PdfiumViewer, iText7 + renderer, Ghostscript wrappers), invoking Adobe Reader or system print commands, or converting PDFs to images and printing via System.Drawing/PrintDocument.

Recommended approach

• Use a reliable PDF rendering library that supports printing (e.g., PdfiumViewer / Pdfium, PDFiumSharp, MuPDF wrappers, or commercial SDKs). They render accurately and offer programmatic print control.
• Avoid automating desktop applications (Adobe Reader) on servers — unstable, unsupported, and requires interactive session.
• For headless/server environments, prefer libraries that can run without UI and that are thread-safe.

Key best practices

1. Choose the right library

   • Prioritize one that preserves layout, fonts, and transparency.
   • Check licensing (open-source vs commercial) for production use.

2. Run in a non-interactive/service-safe mode

   • Ensure the library supports headless printing and does not require a user profile or interactive desktop session.

3. Manage printers and drivers

   • Use stable, up-to-date printer drivers on servers.
   • Handle printer availability and default printer fallbacks.
   • Explicitly set printer names and verify capabilities (color, duplex, paper sizes).

4. Control print settings programmatically

   • Set paper size, orientation, duplex, copies, collation, and scaling.
   • Respect PDF page sizes; scale only when necessary.

5. Handle fonts and resources

   • Embed fonts in PDFs when possible.
   • If fonts are missing, provide fallback fonts or install required fonts on the host.

6. Threading and concurrency

   • Serialize access to shared printer resources if the library or drivers are not thread-safe.
   • Use a print queue or background worker to avoid locking the main app.

7. Error handling and retries

   • Detect common printer errors (offline, paper jam, out of toner) and retry with exponential backoff or alert operators.
   • Log full error details including printer name, job ID, and timestamp.

8. Security and resource limits

   • Validate/scan PDFs before printing to avoid malicious files.
   • Limit PDF file sizes, rendering timeouts, and resource usage to prevent DoS.

9. Performance and scaling

   • Pre-render pages to bitmaps if printing many copies or doing complex transforms.
   • Cache rendered output for repeated prints.
   • Use batching for many small jobs to reduce overhead.

10. Monitoring and observability

    • Expose print job status, success/failure counts, and queue length.
    • Emit structured logs and metrics for retries, durations, and errors.

Common troubleshooting scenarios

• Output looks different from expected

  • Cause: Missing fonts, different rendering engine, or printer driver differences.
  • Fix: Embed fonts, test with the target renderer/library, or rasterize pages before printing.

• Blank pages or truncated output

  • Cause: Library not fully rendering complex content, memory limits, or driver issues.
  • Fix: Increase memory/timeouts, update library, render to image and print the image.

• Printing hangs or jobs stuck in queue

  • Cause: Driver crash, locked spooler, or concurrent access issues.
  • Fix: Serialize access, restart print spooler service, ensure drivers are current.

• Slow printing / high CPU usage

  • Cause: On-the-fly rasterization; large PDFs; excessive concurrency.
  • Fix: Pre-render, reduce concurrency, or use more efficient renderer.

• Errors when running as a Windows Service

  • Cause: Service lacks an interactive session, user profile, or printer access.
  • Fix: Use libraries that support service accounts, install printers for the service account, or run a separate print worker under a user account with needed permissions.

• Printer not found or default printer ignored

  • Cause: Wrong printer name, permissions, or missing per-user printers.
  • Fix: Enumerate installed printers, use full printer share path, verify permissions.

Example workflow (high-level)

1. Validate and sanitize the PDF.
2. Select target printer and verify capabilities.
3. Load PDF with chosen renderer.
4. Set PrintSettings (page range, copies, orientation, duplex).
5. Submit print job asynchronously; monitor status.
6. Log result and handle failures (retry/alert).

Libraries and tools to consider

• PdfiumViewer / PDFium (good rendering fidelity)
• PDFium