Convert ASP to PDF

Reports, invoices, and completed forms generated by a Classic ASP site are often needed as fixed files for email, printing, or records when recipients cannot access the IIS application. The PDF must be created from the page the server renders, not from the .asp source file.

What an ASP file is

An .asp file normally contains Classic Active Server Pages code for Microsoft IIS. It can combine HTML with VBScript or JScript, database queries, include files, session values, and server-side components; IIS executes that code and sends the resulting HTML to the browser.

An ASP file is not a portable document format. Opening report.asp directly from File Explorer does not run it through IIS, so server-side code, database content, and includes will not produce the intended page. Classic ASP remains available as an IIS feature but is an older technology; it is distinct from ASP.NET files such as .aspx, .cshtml, and .razor.

Some unrelated programs also use the .asp extension. If the file did not originate from an IIS web project, identify its creating application before attempting conversion.

What PDF provides

PDF stores a fixed-layout view of text, fonts, images, vector graphics, and page dimensions. Recipients can open the exported report without the web server, database connection, application account, or session that generated it.

A PDF preserves visible output at export time, not web application behavior. Database queries, form submission, login state, JavaScript controls, and interactive charts do not remain functional.

Convert a rendered ASP page with a browser

1. Run the application on its IIS server or a correctly configured local IIS installation. For local Classic ASP, enable the IIS World Wide Web Services → Application Development Features → ASP role service and configure the site, application-pool permissions, include paths, and database access.
2. Open the page through its HTTP or HTTPS address, such as http://localhost/reports/monthly.asp. Do not open the source file with a file:// path.
3. Sign in and enter report parameters before export. Wait for tables, images, and JavaScript-generated charts to finish loading.
4. In Microsoft Edge, Google Chrome, Firefox, or another current browser, choose Print → Save as PDF. Select paper size, orientation, margins, scale, and headers or footers, then save the PDF.

Edge and Chrome are usually the best choices for one-off output because they print the same current browser rendering used to view the report. Enable Background graphics when the layout uses colored headings, shaded rows, logo backgrounds, or CSS background images.

Automate repeated exports

For an accessible, non-authenticated page, Chromium can print a URL from the command line: chrome.exe --headless --print-to-pdf=report.pdf http://localhost/reports/monthly.asp. The browser must be able to reach the IIS site, including any required assets.

For authenticated pages or pages that load data asynchronously, use Playwright or Puppeteer to sign in, wait for a report-ready element, and call the browser PDF function. This is more reliable than printing immediately from a command because it can retain cookies and wait for charts or API requests. Avoid wkhtmltopdf for modern sites unless its output has been tested; its old WebKit engine can differ substantially in CSS and JavaScript support.

Online conversion and output checks

Online services such as CloudConvert can convert uploaded HTML or a public webpage into PDF, but they cannot execute an uploaded ASP source file as an IIS application. Use them only for non-sensitive, already-rendered HTML or a public URL; do not upload customer data, session cookies, private URLs, or source code.

Use a print stylesheet to remove navigation, controls, and sidebars. Rules such as @media print, @page, and break-inside: avoid can control visibility, margins, page breaks, and table-row splitting.

Inspect the final PDF for clipped wide tables, missing fonts, broken image URLs, and blank delayed charts. Browser-generated PDFs are not automatically PDF/A-compliant or fully tagged for accessibility; use a validated PDF/A or accessibility workflow when those requirements apply.