Initial render is slow
If your first HTML to PDF render with IronPDF is slow, we may be looking at the following underlying issues:
Reasons
- The "LinuxAndDockerDependenciesAutoConfig" property flag is set to true and/or the required Linux packages are not installed, causing them to be installed at runtime.
- You are developing on a Windows/Mac machine but deploying to a Linux production environment without using the IronPdf.Linux package, so some components are downloaded from NuGet at runtime.
Initiation Checks
IronPDF will check to ensure that CEF browser DLLs required to execute are available.
- In environments with persistent storage (IIS or web apps), SkipInitialization can be used to skip this check.
- Use the IronPdf NuGet package already preloaded with the files specific to your platform/environment. Please see our Advanced Installation Guide for further information.
- If using IronPdf.Slim, add Mac, Linux and/or Windows Native NuGet Packages to your project to speed up initialization, because native binaries will come pre-installed.
- Default usage requires you to set Installation.AutomaticallyDownloadNativeBinaries = true; to have the IronPdf.Native.Chrome package for your platform downloaded at runtime.
Please note
IronPdf.Slim is the base package for our Chrome-identical rendering engine. Using this package alone may allow the most flexibility but will require more time to initiate as the required files are retrieved from the NuGet CDN.
CEF browser application start-up time
The initial render may take 2-3 seconds to execute. This is normal start-up time that is similar to the time it takes for Chrome to open on a desktop environment.
- If initialization is taking more than 5 seconds, the server or PC may be under-provisioned. We would recommend using a more powerful server or Azure Web app plan (B1 is the minimum).
