How to Create Different PDF Versions
A PDF can contain a wide array of elements, ranging from simple text and images to more complex features such as interactive forms, layered designs, and 3D models. The version of a PDF is directly determined by the features it includes; for example, a document with transparency requires at least version 1.4, while one with layers needs version 1.5. This article will demonstrate how IronPDF automatically manages this complexity, selecting the correct PDF version during conversion to provide a seamless and hassle-free experience.
Get started with IronPDF
Start using IronPDF in your project today with a free trial.
How to Create Different PDF Versions
- Download IronPDF from NuGet for creating different PDF versions
- Instantiate ChromePdfRender
- Using the
RenderHtmlAsPdf
method to to render HTML - Save and export the newly created PDF document
- Verify the version of the new PDF
PDF Version 1.4 Example
IronPDF supports all PDF versions ranging from 1.2 to 1.7. When converting from HTML to PDF, IronPDF automatically selects the lowest version offered by the Chromium engine, ranging from PDF 1.4 to PDF 1.6, to increase compatibility with other viewers.
As such, the version for many conversions is PDF 1.4. PDF 1.4 features include transparency, enabling modern graphic designs while maintaining broad compatibility with most viewers. In this example, we'll perform a simple conversion of an HTML string to a PDF using IronPDF to showcase this behavior.
Code Example
:path=/static-assets/pdf/content-code-examples/how-to/pdf-version-standard.cs
using IronPdf;
var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdf("<p> Hello World!</p>");
pdf.SaveAs("output.pdf");
IRON VB CONVERTER ERROR developers@ironsoftware.com
Output

As you can see from the version, IronPDF chose the lowest version from the range (PDF 1.4) to ensure compatibility with other viewers.
PDF Version 1.7 Example
IronPDF automatically generates a PDF 1.7 (the international standard) file when merging documents to ensure maximum compatibility with all PDF viewers. Since the source PDFs may use different versions and features, defaulting to the comprehensive 1.7 standard ensures that all original elements are preserved without losing data or functionality.
Code Example
:path=/static-assets/pdf/content-code-examples/how-to/merge-or-split-pdfs-merge.cs
using IronPdf;
// Two paged PDF
const string html_a =
@"<p> [PDF_A] </p>
<p> [PDF_A] 1st Page </p>
<div style = 'page-break-after: always;' ></div>
<p> [PDF_A] 2nd Page</p>";
// Two paged PDF
const string html_b =
@"<p> [PDF_B] </p>
<p> [PDF_B] 1st Page </p>
<div style = 'page-break-after: always;' ></div>
<p> [PDF_B] 2nd Page</p>";
var renderer = new ChromePdfRenderer();
var pdfdoc_a = renderer.RenderHtmlAsPdf(html_a);
var pdfdoc_b = renderer.RenderHtmlAsPdf(html_b);
// Four paged PDF
var merged = PdfDocument.Merge(pdfdoc_a, pdfdoc_b);
merged.SaveAs("Merged.pdf");
Imports IronPdf
' Two paged PDF
Private Const html_a As String = "<p> [PDF_A] </p>
<p> [PDF_A] 1st Page </p>
<div style = 'page-break-after: always;' ></div>
<p> [PDF_A] 2nd Page</p>"
' Two paged PDF
Private Const html_b As String = "<p> [PDF_B] </p>
<p> [PDF_B] 1st Page </p>
<div style = 'page-break-after: always;' ></div>
<p> [PDF_B] 2nd Page</p>"
Private renderer = New ChromePdfRenderer()
Private pdfdoc_a = renderer.RenderHtmlAsPdf(html_a)
Private pdfdoc_b = renderer.RenderHtmlAsPdf(html_b)
' Four paged PDF
Private merged = PdfDocument.Merge(pdfdoc_a, pdfdoc_b)
merged.SaveAs("Merged.pdf")
Output

As you can see from the version, IronPDF generated a 1.7 version PDF by merging the two PDFs.