IronPDF - failing when using file path that contain non-ASCII characters

Issue Overview

IronPDF encounters errors when the temp folder path contains non-ASCII characters, such as Nordic characters (ø, æ, å). This can lead to corrupted paths in IronPDF logs, causing failures in generating temporary file paths.

Example of Incorrect Encoding

If IronPDF is initialized in the following directory:
📌 C:\Users\TopcampMjøsa\AppData\Roaming\cshw\ironpdf

The logs may display a corrupted version of the path:
📌 C:\Users\TopcampMosjøen\AppData\Roaming\cshw\ironpdf

This happens because the ø character is misinterpreted due to encoding issues, leading to errors like: 

Workaround

To prevent this issue, ensure that the file path does not contain non-ASCII characters, such as Nordic characters (ø, æ, å).

✅ Recommended Solution: Move IronPDF’s working directory to a path that only contains standard ASCII characters (A-Z, a-z, 0-9, underscore, etc.).

For example:
❌ C:\Users\TopcampMjøsa\AppData\Roaming\cshw\ironpdf (Problematic)
✅ C:\Users\TopcampMjosa\AppData\Roaming\cshw\ironpdf (Recommended)

Conclusion

When using IronPDF, ensuring that the TempFolderPath contains only ASCII characters can prevent encoding-related issues and temp file generation errors. If you encounter problems with corrupted paths in logs, updating the TempFolderPath to a directory without non-ASCII characters is a reliable workaround. Following this approach will help maintain stable performance and avoid unexpected failures.