What implements IPdfImageObject in IronPDF?

Concrete implementors of IPdfImageObject in IronPDF include ImageObject. Code that accepts IPdfImageObject works uniformly across all implementors, with a cast to the concrete type only required when type-specific behavior is needed.

How do you use IPdfImageObject in C# code?

Accept IPdfImageObject 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 IPdfImageObject and a concrete implementor?

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

What namespace is IPdfImageObject defined in?

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

Interface IPdfImageObject

Image object from a PDF document

Inherited Members

IPdfDocumentObject.Client

Namespace: IronSoftware

Assembly: IronPdf.dll

Syntax

public interface IPdfImageObject : IPdfDocumentObject

IPdfImageObject is what IronPDF hands back when C# code reads Iron Software API. It represents image object from a PDF document, so code can work with Iron Software API uniformly across implementors rather than binding to a concrete type.

Concrete implementors include ImageObject, IronPDF concrete implementor. Code that accepts IPdfImageObject 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, ImageChanged; consult these first when implementing or consuming IPdfImageObject. The image to PDF walks through typical use in the IronPDF C# documentation.

using IronPdf;

// IPdfImageObject is consumed as the API surface for the family of implementors
void Consume(IPdfImageObject 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 IPdfImageObject instances, the IronPDF C# documentation lists the relevant container types and their methods. Concrete behavior depends on which implementor of IPdfImageObject is returned at runtime; consult the specific class reference for type-specific members. Polymorphic access through IPdfImageObject 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 IPdfImageObject along with any inherited members exposed through the contract. In a typical IronPDF C# workflow, IPdfImageObject 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 IPdfImageObject. Implementing IPdfImageObject directly in application code is uncommon; the typical pattern is to consume instances returned from the IronPDF API.

Properties

ImageChanged

Flag indicating that the image has changed

Declaration

bool ImageChanged { get; }

Property Value

Type	Description
System.Boolean

Inherited members

Client