OfficeIMO.PowerPoint.Pdf 3.6.1

OfficeIMO.PowerPoint.Pdf - PowerPoint to PDF export

PowerPoint PDF export lives in this adapter and uses the first-party PDF engine. Native slide image export stays in OfficeIMO.PowerPoint and draws through Core. PDF-to-PowerPoint reconstruction lives in OfficeIMO.Pdf.PowerPoint.

Install

dotnet add package OfficeIMO.PowerPoint.Pdf

Quick start

using OfficeIMO;
using OfficeIMO.PowerPoint;
using OfficeIMO.PowerPoint.Pdf;

using var presentation = PowerPointDocument.Load("deck.pptx");
presentation.SaveAsPdf("deck.pdf");

Examples

Export with slide-content controls

using OfficeIMO;
using OfficeIMO.PowerPoint;
using OfficeIMO.PowerPoint.Pdf;

using var presentation = PowerPointDocument.Load("board-review.pptx");

var options = new PowerPointPdfExportOptions {
    IncludeHiddenSlides = false,
    IncludeSlideBackgrounds = true,
    IncludePictures = true,
    IncludeTextBoxes = true,
    IncludeTables = true,
    IncludeCharts = true,
    WarnOnPictureAspectRatioDistortion = true
};

presentation.SaveAsPdf("board-review.pdf", options);

Export to bytes or a stream

using OfficeIMO;
using OfficeIMO.PowerPoint;
using OfficeIMO.PowerPoint.Pdf;

using var presentation = PowerPointDocument.Load("training.pptx");

using var pdf = presentation.ToPdf();
byte[] pdfBytes = pdf.ToBytes(new OfficeIMO.Pdf.PdfSaveOptions { AllowLoss = true });

using var stream = File.Create("training.pdf");
presentation.SaveAsPdf(stream);

Export speaker notes and handouts

using OfficeIMO;
using OfficeIMO.PowerPoint;
using OfficeIMO.PowerPoint.Pdf;

using var presentation = PowerPointDocument.Load("training.pptx");

presentation.SaveAsPdf("training-notes.pdf", new PowerPointPdfExportOptions {
    PageLayout = PowerPointPdfPageLayout.NotesPages,
    IncludeSpeakerNotes = true
});

presentation.SaveAsPdf("training-handout.pdf", new PowerPointPdfExportOptions {
    PageLayout = PowerPointPdfPageLayout.Handouts,
    HandoutSlidesPerPage = 3,
    IncludeSpeakerNotes = true
});

Handouts support 1, 2, 3, 4, 6, or 9 slides per landscape page. Three-up output pairs each thumbnail with notes or writing lines. Notes are read without creating missing notes parts. A slide-page layout or IncludeSpeakerNotes = false reports existing nonempty notes as speaker-notes-omitted with typed omission evidence. Notes that exceed their Notes Pages or Handouts frame report speaker-notes-overflow with typed clipping evidence during serialization.

Review conversion warnings

using OfficeIMO;
using OfficeIMO.PowerPoint;
using OfficeIMO.PowerPoint.Pdf;
using OfficeIMO.Pdf;

using var presentation = PowerPointDocument.Load("complex-deck.pptx");
var options = new PowerPointPdfExportOptions {
    IncludeCharts = true,
    IncludeAutoShapes = true
}.UseProfile(PdfExportProfile.Faithful);

options.TextFallbacks = PdfTextFallbackFeatures.Default;
options.ResourcePolicy = PdfResourcePolicy.CreateTrustedHost();

OfficeConversionReport report = presentation.SaveAsPdf("complex-deck.pdf", options);
foreach (OfficeDiagnostic finding in report.Diagnostics) {
    Console.WriteLine($"{finding.Code}: {finding.Message}");
}

What it maps

• Full-slide pages use the authored slide size; notes pages use portrait letter and handouts use landscape letter.
• Slide backgrounds, text boxes, supported pictures, supported tables, supported charts, and basic auto-shapes.
• Text box fill, outline, margins, font defaults, alignment, vertical anchoring, rich runs, and hyperlinks.
• Supported JPEG/PNG pictures through the shared PDF image pipeline.
• Full-slide PDF output always uses the native per-shape PDF renderer, including hyperlinks and rich text. Conversion no longer chooses a different renderer from document content or an option toggle.
• PNG, SVG, visual-review HTML, and notes/handout thumbnails use the shared visual snapshot; those surfaces have a different scene/raster contract and do not select the PDF engine at runtime.
• Profile presets through PowerPointPdfExportOptions.UseProfile(...), plus shared TextFallbacks and ResourcePolicy controls. The balanced default uses installed fonts while denying arbitrary local and remote reads; portable deterministic mode is explicit.
• Per-operation conversion findings through OfficeConversionReport.Diagnostics.

Numbered paragraph counters reset deeper levels after a parent item in shared visual output and PDF text boxes. PDF table cells retain numbered and character markers as separate text runs, including explicit marker fonts and sizes. Percentage marker sizes use the effective body, header or footer text size. Tables report table-list-layout-approximation because paragraph indentation, marker placement and spacing use the PDF table's inline layout.

Links between slides

Full-slide output preserves supported internal slide links as PDF named destinations. Text-run links follow wrapping, clipping and frame/group transforms; picture and supported shape links use their transformed frame bounds. Line links include the visible stroke so horizontal and vertical lines retain a usable region. Rich table-cell links also retain their targets. Native PowerPoint next-slide actions, including inherited layout/master text, resolve against the active slide in the authored slide order.

Hidden slides keep their source identities. If an export excludes a target slide, its links are omitted with internal-slide-target-omitted evidence. A next-slide action on the final slide has the same missing-target outcome. Other exposed relative targets produce relative-hyperlink omission evidence. These internal-link guarantees apply to the slides layout; notes and handouts retain their separate thumbnail contract. External text-run and picture links remain supported; external links on other shape frames and additional slideshow actions remain outside this mapping.

Current limits

PDF and slide images share the same content and limitations. Stored autofit values, computed shrinking, shape growth, table margins and row growth, theme colors, and native connectors run through this layout. Static conversion does not reproduce chart 3-D scenes, animation playback, or every DrawingML effect.

• Presentation content comes from OfficeIMO.PowerPoint; layout and PDF writing use OfficeIMO.Pdf.
• PdfPowerPointImportMode.Auto is the options default. It resolves an opened PDF to EditableContent and an already reduced PdfDocumentReadResult to EditableTables; use CreateVisualPages() only when one rendered page image per slide is the intended output.
• PdfPowerPointExportOptions.ReadOptions controls the canonical semantic profile, page selection, layout, custom stages, and semantic work limits. The same page selection is used by visual and hybrid imports.
• PdfPowerPointExportOptions.MaxPages defaults to 100 and remains a destination import/rendering safety limit. It is separate from ReadOptions.Pipeline.MaxPages; both limits apply when semantic reconstruction is required.
• PdfPowerPointImportMode.EditableContent reconstructs text blocks, detected tables, safe vector primitives, and supported images as native slide objects and reports anything it cannot represent safely. Fully transparent and unplaced image resources are suppressed; images whose clips, soft masks, unresolved transparency masks, or unsupported blend modes could expose hidden pixels are omitted instead of embedding the raw picture. Supported opacity is mapped to native picture transparency.
• PdfPowerPointImportMode.EditableTables reconstructs detected tables and uses SourceScope / HasOmittedPageContent to expose unrelated page content.
• PdfPowerPointImportMode.HybridVisualAndEditableTables retains each selected page as a visual layer and overlays bounded editable table segments at source-relative geometry.
• The visual and hybrid modes accept caller-supplied fallback fonts for Base-14 and other unembedded font programs. Renderer capability diagnostics remain visible because a fallback is still a substitution, not the source font program.
• Navigation, groups, forms/controls, annotations, interactive media/animations, and complex vector or image placements are not claimed as editable slide objects; stable report warnings identify their visual-only, simplified, or omitted disposition.

Related packages

• OfficeIMO.PowerPoint - PowerPoint presentation model.
• OfficeIMO.Pdf - PDF engine.
• OfficeIMO.Markup.PowerPoint - Markup to PowerPoint rendering.

Targets and license

• Targets: netstandard2.0, net8.0, net10.0.
• License: MIT.
• Repository: EvotecIT/OfficeIMO

Dependency footprint

• External: None beyond the dependencies of its OfficeIMO format packages; no native or commercial PDF renderer.
• OfficeIMO: OfficeIMO.PowerPoint, OfficeIMO.Pdf, and OfficeIMO.Core own slide snapshots, PDF rendering, and reports.

See the complete OfficeIMO package map for related formats and conversion paths.

Generated capability summary

This table is generated from the package-neutral OfficeIMO operation catalog. The detailed source contracts remain authoritative for feature-level behavior and limitations.

The complete rows for OfficeIMO.PowerPoint.Pdf are published in the generated operation contract.