FAQ

Contents
[ ]

What formats does Aspose.PDF for .NET support?

Aspose.PDF for .NET supports popular file formats such as PDF, TXT, HTML, PCL, XML, XPS, EPUB, TEX, and image formats. For more details, please visit the page .

What AI features Aspose.PDF for .NET support?

Yes, the library has built-in OpenAI and Llama API clients. They allow you to make API requests and create AI copilots. You can find examples on page.

How many files can I combine to PDF at once?

You can merge an unlimited number of files into PDF at once.

How to insert Image into PDF?

To insert an image into a PDF using Aspose.PDF for .NET, you can find .

How to edit the text in PDF?

To edit the text in a PDF using Aspose.PDF for .NET, you can find .

How to add page numbers to PDF file?

To add page numbers to a PDF using Aspose.PDF for .NET, you can find .

How to create a background for PDF Documents?

To create a background for a PDF document using Aspose.PDF for .NET, you can find .

How to secure PDF document?

To secure a PDF document using Aspose.PDF for .NET, you can find .

How to add bold text in highlighted annotation on a PDF page?

To add bold text in a highlighted annotation, you can find .

How to validate a tagged PDF?

To validate a tagged PDF document, you can find .

How to implement regex search for TextFragmentAbsorber?

To use regex with the `TextFragmentAbsorber` class in Aspose.PDF for .NET, you can find .

How to make a valid PDF/A document unless the missing font or its substitution is provided?

To create a valid PDF/A document, you can find .

I see errors in PDF/A conversion log. Does it mean that the document wasn't converted successfully?

No, Aspose.PDF logs all problems it encountered, including the ones that were automatically fixed. If all entries in the log are marked as Convertable=True, all problems were fixed, and the document was successfully converted. Only the entries with Convertable=False indicate the conversion failure.

How to make a valid PDF/A document if the conversion log contains "Font not embedded" errors?

If a PDF/A conversion log contains "Font not embedded" error entries marked as Convertable=False, it means that the original document includes fonts that are missing both in the document itself and on the machine where the conversion is performed. Check to learn how to replace missing fonts.

Why doesn't Aspose.PDF convert a document to PDF/A with the ConvertErrorAction.None option?

The ConvertErrorAction.None option prevents Aspose.PDF from removing elements from the document, even if those elements are prohibited by the PDF/A standard. As a result, it may be impossible to convert a document using the ConvertErrorAction.None mode. Use this option when you do not want Aspose.PDF to automatically remove prohibited elements from the document, especially if you plan to review the conversion log and manually fix the document's issues. Another scenario for using this option is when your document is already mostly or fully PDF/A compliant, and you want to avoid unnecessary changes. More permissive PDF/A versions (e.g., PDF/A-2 or PDF/A-3) are more likely to be successfully converted with the ConvertErrorAction.None option. However, for PDF/A-1a and PDF/A-1b standards, it is generally recommended to use the ConvertErrorAction.Delete option.

Does Aspose.PDF for .NET support Linux?

Yes, Aspose.PDF for .NET supports running on Linux environments. You can use the .NET Core version or later, which is cross-platform and can be used on Windows, macOS, and Linux.

Does Aspose.PDF for .NET support .NET 2.0, 3.5, and 4.0 frameworks?

Aspose.PDF for .NET does not support the following .NET frameworks: .NET 2.0, .NET 3.5. However, you can use Aspose.PDF for .NET with any of these frameworks for your project. The library provides a consistent API across the different .NET versions, making it easy to migrate your code between frameworks as needed.

Where are your .NET Examples?

You can check all of them on .

Plugins