What implements IPdfDocumentObject in IronPDF?

Concrete implementors of IPdfDocumentObject in IronPDF include PdfFont, LineTextObject, FontObject, CheckboxFormField, ComboboxFormField. Code that accepts IPdfDocumentObject works uniformly across all implementors, with a cast to the concrete type only required when type-specific behavior is needed.

How do you use IPdfDocumentObject in C# code?

Accept IPdfDocumentObject as a parameter or return type in C# code that needs to work uniformly across IronPDF implementors. The interface defines the contract; concrete behavior is provided by the implementor returned at runtime.

What is the difference between IPdfDocumentObject and a concrete implementor?

IPdfDocumentObject is the interface contract; its concrete implementors carry the actual behavior. Reference IPdfDocumentObject when writing code that should work across multiple implementors; use a concrete type when a single implementor's behavior is required.

Where does IPdfDocumentObject live in the IronPDF API?

IPdfDocumentObject is in the IronSoftware namespace, shipped in IronPdf.dll. It extends IPdfDocumentObject. Concrete classes such as PdfFont, LineTextObject implement it.

Interface IPdfDocumentObject

PDF document object

Namespace: IronSoftware

Assembly: IronPdf.dll

Syntax

public interface IPdfDocumentObject

Iron Software API in IronPDF is exposed through the IPdfDocumentObject contract. It represents PDF document object, so code can work with Iron Software API uniformly across implementors rather than binding to a concrete type.

Concrete implementors include PdfFont, LineTextObject, FontObject. Code that accepts IPdfDocumentObject works uniformly across these implementors, so applications can read or configure C# PDF features without binding to a specific concrete type.

Most of the usable surface is inherited. The members that carry everyday use of this contract are Client, the IPdfDocumentObject contract members; consult these first when implementing or consuming IPdfDocumentObject.

using IronPdf;

// IPdfDocumentObject is consumed as the API surface for the family of implementors
void Consume(IPdfDocumentObject target)
{
    // Use members defined on the interface; concrete behavior follows the implementor
}

For collection-wide operations and end-to-end examples, see the IronPDF C# documentation for related guides. For collection-wide operations on IPdfDocumentObject instances, the IronPDF C# documentation lists the relevant container types and their methods. Concrete behavior depends on which implementor of IPdfDocumentObject is returned at runtime; consult the specific class reference for type-specific members. Polymorphic access through IPdfDocumentObject lets code work uniformly across the family of implementors, with a cast required only when type-specific behavior is needed. The reference tables below list the full set of members defined on IPdfDocumentObject along with any inherited members exposed through the contract. In a typical IronPDF C# workflow, IPdfDocumentObject appears as a parameter or return type at the boundary between the application and the IronPDF API. See the methods table below for the complete set of members defined directly on IPdfDocumentObject. Implementing IPdfDocumentObject directly in application code is uncommon; the typical pattern is to consume instances returned from the IronPDF API. When iterating over a collection of IPdfDocumentObject instances, prefer the inherited members for portable code; downcast only when type-specific behavior is required.

Properties

Client

Pdf client

Declaration

IPdfClient Client { get; set; }

Property Value

Type	Description
IronSoftware.Pdfium.IPdfClient