Class ChromeClientAccessor
Accesses Chrome client implementations
Namespace: IronPdf
Assembly: IronPdf.dll
Syntax
public class ChromeClientAccessor : ObjectReaching the underlying Chrome rendering engine in IronPDF goes through ChromeClientAccessor, a gateway object that surfaces the Chrome client implementations IronPDF uses when converting HTML to PDF or rendering web content. Rather than constructing a renderer from scratch, you interact with ChromeClientAccessor to obtain and configure the Chrome client layer that powers HtmlToPdf, ChromePdfRenderer, and related rendering pipelines.
Because IronPDF delegates all HTML rendering to a managed Chromium process, ChromeClientAccessor sits at the boundary between the managed .NET API and that process. It exists so that advanced scenarios, such as tuning connection behavior, inspecting the active client state, or integrating custom rendering hooks, have a stable, typed entry point rather than relying on internal implementation details. For the majority of PDF generation tasks, the renderer classes handle everything automatically, and ChromeClientAccessor operates silently in the background. When precise control over the Chrome client layer is required, this object provides the access point.
ChromeClientAccessor inherits directly from System.Object and carries no public members of its own; its role is structural, acting as a typed handle that the IronPDF runtime resolves to the correct Chrome client implementation at runtime. This design keeps the public API stable even as the underlying Chromium integration evolves across IronPDF releases.
For typical HTML-to-PDF work, the IronPDF getting-started guide and the HTML to PDF how-to cover everything needed without touching ChromeClientAccessor directly.