Where does PdfClientAccessor live in the IronPDF API?

PdfClientAccessor is a class in the IronPdf namespace, shipped in IronPdf.dll. It derives from Object and sits at the infrastructure layer beneath the rendering and document APIs.

When do you need to use PdfClientAccessor in a C# project?

Most projects work entirely through ChromePdfRenderer and PdfDocument and never touch PdfClientAccessor directly. It becomes useful when building extensions, writing diagnostic tooling, or wiring IronPDF into a dependency-injection container that needs to resolve or replace the client implementation at runtime.

Class PdfClientAccessor

Accesses PDF client implementations

Inheritance

System.Object

PdfClientAccessor

LinkAnnotation

TextAnnotation

PdfBookMarkCollection

PdfPage

PdfPageModel

PdfAttachment

PdfAttachmentCollection

PdfDocument

PdfSecuritySettings

Namespace: IronPdf

Assembly: IronPdf.dll

Syntax

public class PdfClientAccessor : Object

Gaining access to the underlying PDF client implementation is what PdfClientAccessor enables within the IronPDF library. Acting as a bridge object in the IronPdf namespace, it exposes the active PDF rendering and processing client so that advanced scenarios, such as custom configuration, diagnostics, or integration with lower-level pipeline components, can reach the engine directly without routing through the higher-level document API.

Because PdfClientAccessor has no declared members of its own, its role is structural rather than operational. It serves as a typed access point, giving the runtime a concrete handle to the client layer that powers PDF generation, conversion, and manipulation throughout IronPDF. Code that needs to inspect or substitute the client implementation uses this class as the recognized contract point, keeping that concern separate from document-level types like PdfDocument.

In practice, most applications work entirely through ChromePdfRenderer and PdfDocument and never interact with PdfClientAccessor directly. It becomes relevant when building extensions, writing diagnostic tooling, or integrating IronPDF into a dependency-injection container where the client implementation must be resolved or replaced at runtime. Understanding that PdfClientAccessor sits at the infrastructure layer, beneath the rendering and document APIs, helps clarify where to look when customizing engine behavior.

Explore the IronPDF documentation for a full picture of the rendering pipeline, and see the getting started guide for typical setup patterns that place PdfClientAccessor in context.