IronPDF Fails with Non-ASCII Characters in File Paths

Updated:June 9, 2026

IronPDF fails to generate PDFs or write output files when the temp folder path contains non-ASCII characters such as Nordic symbols (ø, æ, å).

[2023-02-09 13:19:21] !!! Invalid (empty) temp path generated by operating system
[2023-02-09 13:19:21] Unknown exception
[2023-02-09 13:19:21] Warning! Failed to generate temp file path in temp directory, defaulting to working directory

IronPDF's internal path handling encounters encoding failures when the temp directory path includes non-ASCII characters. The character encoding is corrupted during path processing; for example, "ø" is misread as "osjÃ¸en", producing invalid temp paths and causing the exception.

Solution

Set TempFolderPath to a path that contains only standard ASCII characters (A–Z, a–z, 0–9, underscore, hyphen):

IronPdf.Installation.TempFolderPath = @"C:\IronPdfTemp";

IronPdf.Installation.TempFolderPath = @"C:\IronPdfTemp";

IronPdf.Installation.TempFolderPath = "C:\IronPdfTemp"

$vbLabelText $csharpLabel

Set this property before the first call to ChromePdfRenderer. If the original user profile path contains non-ASCII characters (for example, C:\Users\TopcampMjøsa\AppData\...), redirect to a path such as C:\IronPdfTemp or another ASCII-safe location.

Curtis Chau

Chat with engineering team now

Technical Writer

Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.

...

Ready to Get Started?

Nuget Downloads 19,345,590 | Version: 2026.6 just released