How to Export PDF/A, PDF/A-3, or PDF/A-4 Format Documents in C#

Why is Section 508 compliance important for PDF/A documents?

Section 508 compliance ensures PDF documents are accessible to individuals with disabilities using assistive technologies like screen readers. PDF/A documents meeting Section 508 standards guarantee content remains accessible throughout archival lifespan. This compliance is critical for government agencies, educational institutions, and organizations providing equal access to information for all users.

Minimal Workflow (4 steps)

1. Download C# Library for Creating PDF/A Documents
2. Load existing PDF or render from HTML/URL
3. Select PDF/A version based on archival requirements
4. Convert and save as PDF/A compliant document

What are the differences between PDF/A-1, PDF/A-2, and PDF/A-3?

PDF/A-1: Based on original PDF 1.4 version.

PDF/A-2: Released July 2011 as ISO 32001-1, includes all features of PDF versions up to 1.7 plus new features. Supports JPEG2000 for scanned documents and specific requirements for customized XMP metadata. When working with PDF metadata, IronPDF ensures proper XMP metadata handling.

PDF/A-3: Includes all Level 2 requirements. Allows embedding additional file formats—XML, CSV, and word processing formats—into PDF/A conforming documents.

PDF/A-4: The latest version of the PDF/A compliance standard, released in 2020. It is based on PDF 2.0 and introduces improved functionality, including enhanced support for digital signatures compared to PDF/A-3. This version is best suited for engineering documents and technical workflows that involve 3D models and other complex elements.

What does the input PDF look like before conversion?

What code converts existing PDFs to PDF/A format?

:path=/static-assets/pdf/content-code-examples/how-to/pdfa-fromfile.cs

using IronPdf;

// Create a PdfDocument object or open any PDF File
PdfDocument pdf = PdfDocument.FromFile("wikipedia.pdf");

// Use the SaveAsPdfA method to save to file
pdf.SaveAsPdfA("pdf-a3-wikipedia.pdf", PdfAVersions.PdfA3b);

How can I verify the PDF/A conversion was successful?

The output file is PDF/A-3b compliant:

How do I convert HTML files to PDF/A format?

:path=/static-assets/pdf/content-code-examples/how-to/pdfa-fromhtml.cs

using IronPdf;

// Use the Chrome Renderer to make beautiful HTML designs
var chromeRenderer = new ChromePdfRenderer();

// Render an HTML design as a PdfDocument object using Chrome
PdfDocument pdf = chromeRenderer.RenderHtmlAsPdf("design.html");

// Use the SaveAsPdfA method to save to file
pdf.SaveAsPdfA("design-accessible.pdf", PdfAVersions.PdfA3b);

The output file is PDF/A-3B compliant:

How do I convert websites to PDF/A format?

This example renders https://www.microsoft.com from URL to PDF using IronPDF and exports it as a PDF/A compliant file. The URL to PDF conversion feature ensures all web content, including JavaScript and CSS, is properly rendered.

The code below saves the output as a PDF/A-3B compliant PDF file.

:path=/static-assets/pdf/content-code-examples/how-to/pdfa-fromurl.cs

using IronPdf;

// Use the Chrome Renderer to make beautiful HTML designs from URLs
var chromeRenderer = new ChromePdfRenderer();

// Render a Website as a PdfDocument object using Chrome
PdfDocument pdf = chromeRenderer.RenderUrlAsPdf("https://www.microsoft.com");

// Use the SaveAsPdfA method to save to file
pdf.SaveAsPdfA("website-accessible.pdf", PdfAVersions.PdfA3b);

The output file is PDF/A-3B compliant:

Embed with File Paths

Embed files using their file paths. A collection of file paths is provided, and these files are included as attachments during PDF/A conversion.

:path=/static-assets/pdf/content-code-examples/how-to/pdfa-attachment-path.cs

using IronPdf;
using System.Collections.Generic;

PdfDocument pdf = new PdfDocument("Google.pdf");

// Initialize collection of embed file as string of path
IEnumerable<string> embedPaths = new[] { "File1.xml", "File2.png" };

// Convert to Pdf/A-3B with embeded files
pdf.ConvertToPdfA(embedPaths);

How do I embed files using byte arrays?

Embed files by providing file content as byte arrays with their respective file types. Useful when files are already loaded into memory.

:path=/static-assets/pdf/content-code-examples/how-to/pdfa-attachment-byte.cs

using IronPdf;
using System.Collections.Generic;
using System.IO;


PdfDocument pdf = new PdfDocument("Google.pdf");

// Initialize collection of embed file as Bytes and their file type
byte[] fileData1 = File.ReadAllBytes("File1.png");
byte[] fileData2 = File.ReadAllBytes("File2.xml");

var embedFileConfig1 = new EmbedFileConfiguration(EmbedFileType.png);
embedFileConfig1.EmbedFileName = "logo.png";

var embedFileConfig2 = new EmbedFileConfiguration(EmbedFileType.xml)
{
    EmbedFileName = "supportSystem.xml",
    AFDesc = "Internal system",
    ConformanceLevel = ConformanceLevel.XRECHNUNG,
    SchemaNamespace = SchemaNamespace.Zugferd1,
    SchemaPrefix = SchemaPrefix.rsm,
    PropertyVersion = PropertyVersion.v1p0,
    AFRelationship = AFRelationship.Supplement,
};

IEnumerable<EmbedFileByte> embedBytes = new[]
{
    new EmbedFileByte(fileData1, embedFileConfig1),
    new EmbedFileByte(fileData2, embedFileConfig2)
};

// Convert to Pdf/A-3B with embeded files
pdf.ConvertToPdfA(embedBytes).SaveAs("PdfACompliance.pdf");

How do I embed files using streams?

Embed files using streams for content with their file types. Ideal when file data is processed as a stream.

:path=/static-assets/pdf/content-code-examples/how-to/pdfa-attachment-stream.cs

using IronPdf;
using System.Collections.Generic;
using System.IO;

PdfDocument pdf = new PdfDocument("Google.pdf");

// Initialize collection of embed file as Stream and their file type
Stream stream1 = new MemoryStream(File.ReadAllBytes("File1.png"));
Stream stream2 = new MemoryStream(File.ReadAllBytes("File2.xml"));

var embedFileConfig1 = new EmbedFileConfiguration(EmbedFileType.png);
embedFileConfig1.EmbedFileName = "logo.png";

var embedFileConfig2 = new EmbedFileConfiguration(EmbedFileType.xml)
{
    EmbedFileName = "supportSystem.xml",
    AFDesc = "Internal system",
    ConformanceLevel = ConformanceLevel.XRECHNUNG,
    SchemaNamespace = SchemaNamespace.Zugferd1,
    SchemaPrefix = SchemaPrefix.rsm,
    PropertyVersion = PropertyVersion.v1p0,
    AFRelationship = AFRelationship.Supplement,
};

IEnumerable<EmbedFileStream> embedStreams = new[]
{
    new EmbedFileStream(stream1, embedFileConfig1),
    new EmbedFileStream(stream2, embedFileConfig2)
};

// Convert to Pdf/A-3B with embeded files
pdf.ConvertToPdfA(embedStreams).SaveAs("PdfACompliance.pdf");

How do I configure embedded file properties with EmbedFileConfiguration?

When converting a PdfDocument to PDF/A-3 format with embedded files, configure parameters such as EmbedFilePath, EmbedFileByte, or EmbedFileStream to specify the file type, name, and custom XMP metadata.

Proper configuration ensures embedded content is organized effectively and complies with PDF/A-3 standards. Customizing XMP metadata allows additional information about embedded files, enhancing document usability and accessibility. Using the EmbedFileConfiguration class, developers easily customize values and formats for the file.

var config = new EmbedFileConfiguration
{
    EmbedFileName = "Attachment.xml",
    AFDesc = "Associated File Description",
    ConformanceLevel = ConformanceLevel.EN16931,
    SchemaNamespace = SchemaNamespace.facturX,
    SchemaPrefix = SchemaPrefix.fx,
    PropertyVersion = PropertyVersion.v1,
    AFRelationship = AFRelationship.Alternative
};

 // Load a PDF document
 var document = PdfDocument.FromFile("wikipedia.pdf");

 // Configure embedded file parameters
 document.EmbedFileFromFilePath("path/to/attachment", config);

 // Save the document as PDF/A-3b
 document.SaveAsPdfA3B("output-with-configured-attachment.pdf");

var config = new EmbedFileConfiguration
{
    EmbedFileName = "Attachment.xml",
    AFDesc = "Associated File Description",
    ConformanceLevel = ConformanceLevel.EN16931,
    SchemaNamespace = SchemaNamespace.facturX,
    SchemaPrefix = SchemaPrefix.fx,
    PropertyVersion = PropertyVersion.v1,
    AFRelationship = AFRelationship.Alternative
};

 // Load a PDF document
 var document = PdfDocument.FromFile("wikipedia.pdf");

 // Configure embedded file parameters
 document.EmbedFileFromFilePath("path/to/attachment", config);

 // Save the document as PDF/A-3b
 document.SaveAsPdfA3B("output-with-configured-attachment.pdf");

• EmbedFileName: A string property representing the embedded file name in the PDF/A document. Default is empty string.
• AFDesc: A string property representing the associated file description for the embedded file. Default is empty string.
• ConformanceLevel: The conformance level of embedding XML files applying to XMP Metadata of PDF/A document. Default is ConformanceLevel.EN16931. IronPDF provides different values via the ConformanceLevel enum.
• SchemaNamespace: The PDF/A Schema NamespaceURI embedding XML files and applying to XMP metadata of PDF/A document. Default is SchemaNamespace.facturX, with various options available in the SchemaNamespace enum.
• SchemaPrefix: The PDF/A Schema Prefix for embedding XML files applying to XMP Metadata of PDF/A document. Default is SchemaPrefix.fx, with several options in the SchemaPrefix enum.
• PropertyVersion: The property version of embedding XML files applied to XMP Metadata of PDF/A document. Default is PropertyVersion.v1, with multiple options in the PropertyVersion enum.
• AFRelationship: The relation of the associated file (embedded file) to the PDF/A document. Several options are available in the AFRelationship enum.

Why do some characters appear broken in PDF/A documents?

For example, in the issue below, the top sample uses the correct font and displays characters properly, while the bottom sample fails to render them correctly due to font mismatch.

Input file: "ENV-2026-1847-Assessment-Report.pdf"

Code

:path=/static-assets/pdf/content-code-examples/how-to/save-as-pdfa4.cs

using IronPdf;

// Load the environmental impact assessment document
PdfDocument pdf = PdfDocument.FromFile("ENV-2026-1847-Assessment-Report.pdf");

// Save as PDF/A-4 compliant document for long-term archival
pdf.SaveAsPdfA("ENV-2026-1847-Report-PDFA4Compliant.pdf", PdfAVersions.PdfA4);

Output

The output file is PDF/A-4 compliant:

Ready to see what else you can do? Check out our tutorial page here: Create PDFs