How to Make an Engineering Support Request for IronPDF

Curtis Chau

Updated: June 10, 2026

Download IronPDF

• Node Download

• ---

• Start Free Trial

Copy for LLMs

• Copy for LLMs

  Copy page as Markdown for LLMs
  # How to Make an Engineering Support Request for IronPDF We appreciate your taking the time to help us improve IronPDF and resolve any issue you may be experiencing. The vast majority of our features and updates are driven by customer requests, and we consider software development a two-way conversation between our customers and our developers. To provide support, our engineering team will need to be able to efficiently replicate an issue and create regression tests. Most issues we see are platform or runtime-specific. As such, we need to be provided with extremely concise information. Please send all support requests to [support@ironsoftware.com](mailto:support@ironsoftware.com). ## A Concise, Clear Description of the Issue A good technical report must include enough information to reproduce the issue. Imagine you are reporting the issue to a colleague or posting on Stack Overflow. A bug report should contain: - A clear description of the symptoms experienced and any ideas you may have regarding their cause. - Log files (see below) - Environment: IronPDF version, Node.js version, OS, and exact cloud environment (if applicable) Please include as many of the following as possible to prioritize your ticket: - Example project that fully reproduces the issue (see below) - A Stack Overflow style code snippet (please do not screenshot code) - Screenshots of symptoms or exceptions - Exception message text (error + stack trace) - Input parameters and assets: URL, HTML, HTML file, image, PDF, CSS, etc. ## How to Enable IronPDF Logs Place the following code before any other IronPDF calls: ```js const { IronPdfGlobalConfig } = require('@ironsoftware/ironpdf'); const config = IronPdfGlobalConfig.getConfig(); config.licenseKey = process.env.IRONPDF_LICENSE_KEY; config.logPath = '/tmp/ironpdf.log'; config.debug = true; await IronPdfGlobalConfig.setConfig(config); ``` Attach the generated log file to your support request. ## How to Attach an Example Project **An example project that accurately replicates an entire issue in isolation** enables our engineers to simply and swiftly recognize and understand an issue. **Our preferred format is a zipped, simple, standalone Node.js console project:** - Please enable full sharing when sending a Google Drive or Dropbox link. Please also include: - Input files (working and non-working), including PDFs, HTML, referenced assets (CSS, images) - Output PDFs (if applicable) and the expected output

• ---

• Open in ChatGPT

  Ask ChatGPT about this page
• Open in Gemini

  Ask Gemini about this page
• Open in Grok

  Ask Grok about this page
• Open in Perplexity

  Ask Perplexity about this page

Share

• Share on Facebook
• Share on X (Twitter)
• Share on LinkedIn

• ---

• Email article

We appreciate your taking the time to help us improve IronPDF and resolve any issue you may be experiencing. The vast majority of our features and updates are driven by customer requests, and we consider software development a two-way conversation between our customers and our developers.

To provide support, our engineering team will need to be able to efficiently replicate an issue and create regression tests. Most issues we see are platform or runtime-specific. As such, we need to be provided with extremely concise information.

Please send all support requests to support@ironsoftware.com.

A Concise, Clear Description of the Issue

A good technical report must include enough information to reproduce the issue. Imagine you are reporting the issue to a colleague or posting on Stack Overflow.

A bug report should contain:

• A clear description of the symptoms experienced and any ideas you may have regarding their cause.
• Log files (see below)
• Environment: IronPDF version, Node.js version, OS, and exact cloud environment (if applicable)

Please include as many of the following as possible to prioritize your ticket:

• Example project that fully reproduces the issue (see below)
• A Stack Overflow style code snippet (please do not screenshot code)
• Screenshots of symptoms or exceptions
• Exception message text (error + stack trace)
• Input parameters and assets: URL, HTML, HTML file, image, PDF, CSS, etc.

How to Enable IronPDF Logs

Place the following code before any other IronPDF calls:

const { IronPdfGlobalConfig } = require('@ironsoftware/ironpdf');

const config = IronPdfGlobalConfig.getConfig();
config.licenseKey = process.env.IRONPDF_LICENSE_KEY;
config.logPath = '/tmp/ironpdf.log';
config.debug = true;
await IronPdfGlobalConfig.setConfig(config);

const { IronPdfGlobalConfig } = require('@ironsoftware/ironpdf');

const config = IronPdfGlobalConfig.getConfig();
config.licenseKey = process.env.IRONPDF_LICENSE_KEY;
config.logPath = '/tmp/ironpdf.log';
config.debug = true;
await IronPdfGlobalConfig.setConfig(config);

Attach the generated log file to your support request.

How to Attach an Example Project

An example project that accurately replicates an entire issue in isolation enables our engineers to simply and swiftly recognize and understand an issue.

Our preferred format is a zipped, simple, standalone Node.js console project:

• Please enable full sharing when sending a Google Drive or Dropbox link.

Please also include:

• Input files (working and non-working), including PDFs, HTML, referenced assets (CSS, images)
• Output PDFs (if applicable) and the expected output

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.

...

Read More