Image Page Layout

Image Page Layout

This page documents the MultiPageLayout configuration class and its related image-rendering enumerations, and explains why they have no functional save pathway in this edition.

Aspose.Words FOSS for .NET includes a small set of model classes for describing how multiple document pages would be arranged when rendered into a single image-based output — MultiPageLayout and its supporting enumerations. This edition does not include the page-layout and rendering engine itself (see Features and Functionalities and the product overview), so these types exist in the public API surface as configuration primitives without a save pathway that consumes them in this build.

MultiPageLayout

MultiPageLayout is a sealed class whose static factory methods each build a different multi-page arrangement: Vertical(verticalGap) stacks pages top to bottom with the given gap between them; Horizontal(horizontalGap) places pages side by side, left to right; Grid(columns, horizontalGap, verticalGap) arranges pages left-to-right, top-to-bottom in a grid with the specified column count; TiffFrames() keeps each page as a separate frame instead of combining them into one image; and SinglePage() renders only a single page. Once built, a MultiPageLayout instance exposes BackColor and BorderColor (both Color) and BorderWidth (float) for styling the combined output.

Related Rendering Enumerations

Three additional enumerations describe the same “document pages as images” domain: ImageColorMode (None, Grayscale, BlackAndWhite) controls the color mode of generated page images; ImagePixelFormat lists the pixel formats available for generated page images (such as Format24BppRgb and Format32BppArgb); and ImageBinarizationMethod (Threshold, FloydSteinbergDithering) specifies how an image is converted to black-and-white. As with MultiPageLayout, these are defined in the API surface but are not currently wired to a save-options class in this edition — this FOSS build does not include image, PDF, or XPS export.

Tips and Best Practices

• Treat MultiPageLayout and its related enumerations as reference-only in this edition — there is no Save() pathway in the public API surface that consumes a MultiPageLayout instance to actually produce an image.
• If your workflow needs to render Word documents to TIFF, PNG, JPEG, or other image formats, use the commercial Aspose.Words for .NET, which includes the full rendering engine these types are designed for.
• Do not confuse this page-layout-for-images area with embedding pictures inside a document (the Shape / ImageData API) — that is a separate, normal document-content feature, not page rendering.

Common Issues

FAQ

Can I use MultiPageLayout to export my document as a multi-page TIFF?

Not in this edition. MultiPageLayout and its supporting enumerations (ImageColorMode, ImagePixelFormat, ImageBinarizationMethod) are present in the API surface, but the image-rendering save pipeline that would consume them is not part of this FOSS build.

Why does this class exist if it isn’t functional here?

Aspose.Words FOSS for .NET is the genuine Aspose.Words codebase reduced to a free core, not a rewrite — some model-layer classes tied to the removed rendering engine remain compiled into the library even though no supported save path currently uses them.

Is embedding a picture inside a document also excluded?

No — inserting and formatting pictures within a document’s content (via Shape and ImageData) is a normal, supported document-editing feature. Only rendering entire pages to an image format is excluded.

API Reference Summary