Where does SystemClientAccessor live in the IronPDF API?

SystemClientAccessor is a class in the IronPdf.Engines namespace, shipped in IronPdf.dll. It derives from Object and acts as the coordination point for resolving the active system PDF client within IronPDF's engine infrastructure.

When would you interact with SystemClientAccessor directly?

Most application code never touches SystemClientAccessor directly; IronPDF uses it internally during engine initialization. Direct interaction becomes relevant when extending IronPDF, diagnosing client-resolution issues, or building integration layers that need to inspect or override the default rendering client behavior.

Class SystemClientAccessor

Accesses system client implementations

Inheritance

System.Object

SystemClientAccessor

Namespace: IronPdf.Engines

Assembly: IronPdf.dll

Syntax

public class SystemClientAccessor : Object

Resolving the correct rendering engine at runtime is the job SystemClientAccessor performs inside IronPDF's engine layer. It acts as a coordination point that locates and surfaces the system-level PDF client implementation the library needs to process documents, so the rest of the pipeline can request a client without knowing which concrete implementation is active in the current environment.

SystemClientAccessor lives in the IronPdf.Engines namespace, a layer that sits between the public-facing PDF API and the lower-level rendering substrate. When IronPDF initializes, the engine infrastructure uses this accessor to wire up the appropriate client for the host platform, whether that is a local Chromium-based renderer or an alternative system client configured for a server or container deployment. Application code rarely constructs or calls SystemClientAccessor directly; instead, it benefits from the accessor's work transparently whenever a PdfDocument is created, a page is rendered, or HTML is converted to PDF through the standard API surface.

Understanding this type is most useful when extending IronPDF, diagnosing engine-initialization issues, or building integration layers that need to inspect or override the default client resolution behavior. In those scenarios, knowing that SystemClientAccessor is the seam between configuration and the active rendering client helps narrow down where to look.

For typical PDF generation and manipulation tasks, the IronPDF getting-started guide and the HTML-to-PDF how-to cover everything needed without touching this layer directly.