Skip to main content
Get Started

PDF review import

Convert PDF content to reviewable HTML

Choose semantic or positioned-review HTML, retain structured warnings, and distinguish review output from a pixel-perfect page clone.

Convert PDF to HTML in the browser Read the conversion guide

Practical steps

Project PDF content into reviewable HTML

Read supported page structures, preserve page-aware review geometry in the browser, and retain conversion diagnostics.

  1. SelectChoose a readable PDF or load the built-in sample.
  2. ConvertProject text, tables, links, forms, images, and supported page geometry into positioned-review HTML.
  3. ReviewPreview or download the HTML and inspect the companion warning report.

OfficeIMO exposes two explicit PDF-to-HTML profiles. Semantic output is useful for publishing, search ingestion, accessibility remediation, and content pipelines. Positioned-review output keeps page containers and supported geometry so reviewers can inspect how extracted content relates to the source page. Neither profile is a browser clone of the PDF renderer.

Convert from .NET

using OfficeIMO.Html.Pdf;
using OfficeIMO.Pdf;

PdfDocument pdf = PdfDocument.Load("policy.pdf");
PdfHtmlConversionResult semantic = pdf.ToHtmlResult();
PdfHtmlConversionResult review = pdf.ToHtmlResult(new PdfHtmlSaveOptions {
    Profile = PdfHtmlProfile.PositionedReview,
    IncludeLinkAnnotations = true,
    IncludeFormWidgets = true
});

File.WriteAllText("policy-review.html", review.Value);
foreach (PdfConversionWarning warning in review.Report.Warnings) {
    Console.WriteLine($"{warning.Code}: {warning.Message}");
}

The .NET API defaults to the semantic profile. The browser workbench deliberately selects PositionedReview, displays that generated HTML, and downloads the same content with a JSON report describing the source, output, conversion profile, timing, and warnings.

Semantic output versus visual reproduction

This route does not wrap a page image in HTML or promise identical browser layout. PDF reading order, unusual fonts, complex drawings, optional content, and scanned pages may require approximation or separate handling. Use visual PDF rendering when fixed appearance matters, positioned review when page-aware inspection matters, and semantic output when meaningful editable web content is the goal.