Converting HTML to PDF format is one of the most common document tasks. A PDF gives you a portable, printable document that looks the same on any device. This is useful for archiving webpages, sharing reports offline, or generating invoices from web applications.

This guide covers four methods, from quick browser options to developer-focused solutions for automated workflows.

Method 1: Use your browser (print to PDF)

Your browser’s built-in print function converts any webpage or local HTML file to PDF.

Chrome

1. Open the HTML file or webpage in Chrome
2. Press Control-P (Windows) or Command-P (Mac)
3. Change Destination to Save as PDF
4. Adjust settings (margins, scale, and background graphics)
5. Click Save and choose a location

Firefox

1. Open the HTML file or webpage in Firefox
2. Press Control-P (Windows) or Command-P (Mac)
3. Select Microsoft Print to PDF or Save to PDF
4. Adjust layout options as needed
5. Click Save

Safari

1. Open the HTML file or webpage in Safari
2. Go to File > Export as PDF, or press Command-P
3. Click the PDF dropdown in the bottom-left corner
4. Select Save as PDF
5. Choose a location and click Save

Edge

1. Open the HTML file or webpage in Edge
2. Press Control-P (Windows)
3. Change Printer to Microsoft Print to PDF or Save as PDF
4. Adjust settings and click Save

Tips for better output

• Enable Background graphics to include colors and images
• Set Margins to None or Minimum for more content per page
• Use Scale to fit wide content on the page
• Remove Headers and footers for cleaner output

Method 2: Free online HTML-to-PDF converters

Online converters handle quick conversions without installing software. Upload an HTML file or enter a URL, and the service returns a PDF.

Popular free converters

When to use online converters

Online converters make sense when you need a quick PDF and don’t want to install anything. They’re useful for one-off conversions of public webpages or simple HTML files where exact formatting isn’t critical.

Avoid them for anything automated or sensitive, or where you need consistent results across multiple conversions.

Limitations to consider

• Privacy — Your HTML content is uploaded to third-party servers, which may not be suitable for confidential documents.
• File size limits — Free tiers restrict upload sizes, typically ranging from 2 MB to 50 MB.
• Internet required — These tools require an active internet connection and cannot work offline.
• Inconsistent rendering — CSS support varies significantly between tools, so complex layouts may not convert accurately.

Method 3: JavaScript libraries (for developers)

Several JavaScript libraries can add PDF export to your applications. These run either client-side (in the browser) or server-side (on your backend).

Client-side: html2pdf.js

html2pdf.js combines html2canvas and jsPDF to convert HTML elements to PDF directly in the browser:

// Include via CDN.
// <script src="https://cdnjs.cloudflare.com/ajax/libs/html2pdf.js/0.14.0/html2pdf.bundle.min.js"></script>
const element = document.getElementById('content');
html2pdf().from(element).save('document.pdf');

This works for simple documents but produces image-based PDFs with limited CSS support.

Client-side: jsPDF

jsPDF creates PDFs programmatically from JavaScript objects rather than HTML:

// Include via CDN.
// <script src="https://cdnjs.cloudflare.com/ajax/libs/jspdf/4.2.1/jspdf.umd.min.js"></script>
const doc = new jsPDF();
doc.text('Hello World', 10, 10);
doc.save('document.pdf');

Best for structured documents like invoices where you control the exact layout.

Server-side: Puppeteer and Playwright

Puppeteer and Playwright control headless browsers to render pages with full CSS support:

const { chromium } = require('playwright');
(async () => {
  const browser = await chromium.launch();
  const page = await browser.newPage();
  await page.setContent('<h1>Invoice</h1><p>Details here...</p>');
  await page.pdf({ path: 'invoice.pdf', format: 'A4' });
  await browser.close();
})();

These produce high-fidelity PDFs but require server infrastructure.

When to use JavaScript libraries

• Building apps with PDF export features
• Automated report generation
• Custom PDF workflows in your codebase

For a detailed comparison of JavaScript libraries, refer to our blog post on how to convert HTML to PDF with JavaScript.

Method 4: Professional SDKs (for production apps)

Free tools and open source libraries work for prototypes and internal tools. But when HTML-to-PDF conversion becomes part of your product — such as generating customer invoices, compliance reports, or contracts — you need reliability, consistent output, and support.

Why use a professional SDK?

Open source libraries render CSS inconsistently, produce flat PDFs without fillable form fields, and crash on large documents. They also lack enterprise security features and dedicated support. Professional SDKs solve these problems for production applications.

Nutrient solutions

Nutrient offers several options for HTML-to-PDF conversion: Document Engine for server-side processing, native SDKs for mobile and desktop platforms, a cloud API for zero-infrastructure setups, and no-code integrations for automated workflows.

Document Engine

Document Engine is a server-side toolkit that powers document processing, rendering, and automation behind the scenes of web, mobile, and desktop apps. It handles more than just HTML-to-PDF conversion: You can use it for document viewing, generation, conversion, OCR, redaction, and real-time collaboration at scale.

Document Engine uses a Chromium-based rendering engine, so modern CSS (flexbox, grid, custom fonts, and print stylesheets) works out of the box. We recommend previewing your HTML in Chrome before conversion, though minor differences may occur. HTML form elements (input, select, and textarea tags) automatically become fillable PDF form fields.

You can run document workflows entirely on the backend, or pair Document Engine with a frontend SDK. The backend handles large files and high-volume document batches that would overwhelm browser-based solutions. Features like form filling, annotation, and signing work through frontend and backend syncing, so users interact with documents in the browser while the server handles processing.

Document Engine integrates with .NET, Node.js, Java, iOS, Android, React Native, and Flutter.

curl -X POST http://localhost:5000/api/build \
  -H "Authorization: Token token=<API token>" \
  -F page.html=@/path/to/page.html \
  -F instructions='{ "parts": [{ "html": "page.html" }] }' \
  -o result.pdf

Three deployment options:

Self-hosted means you run the Docker container on your own servers. You control the infrastructure, updates, and scaling. This option works for air-gapped environments or when regulations require data to stay on-premises.

Nutrient Processor API is the fastest way to get started. You send HTTP requests to Nutrient’s servers and receive PDFs back. No infrastructure to manage, and you pay based on credits consumed. The API supports multiple languages, including JavaScript, Python, Java, C#, and PHP:

const axios = require('axios')
const FormData = require('form-data')
const fs = require('fs')
const formData = new FormData()
formData.append('html', fs.createReadStream('index.html'));
(async () => {
  try {
    const response = await axios.post('https://api.nutrient.io/processor/generate_pdf', formData, {
      headers: formData.getHeaders({
        'Authorization': 'Bearer your_api_key_here'
      }),
      responseType: "stream"
    })
    response.data.pipe(fs.createWriteStream("result.pdf"))
  } catch (e) {
    const errorString = await streamToString(e.response.data)
    console.log(errorString)
  }
})()
function streamToString(stream) {
  const chunks = []
  return new Promise((resolve, reject) => {
    stream.on("data", (chunk) => chunks.push(Buffer.from(chunk)))
    stream.on("error", (err) => reject(err))
    stream.on("end", () => resolve(Buffer.concat(chunks).toString("utf8")))
  })
}

Managed gives you a dedicated Document Engine instance that Nutrient operates on your behalf. You get the isolation of self-hosting without the operational overhead. This option fits organizations that need compliance guarantees but don’t want to manage infrastructure.

.NET SDK

The .NET SDK brings HTML-to-PDF conversion to .NET applications. It uses Chrome-based rendering for consistent output.

The SDK integrates with C# and other .NET languages. You pass an HTML string or file path to the conversion method, and it returns a PDF document. Since it runs locally, your HTML content never leaves your servers.

Android and iOS SDKs

Our Android SDK and iOS SDK generate PDFs directly on mobile devices. Android uses the system WebView for rendering, while iOS uses WebKit. Both produce PDFs without requiring a network connection or external server.

On-device conversion keeps sensitive data on the device instead of sending it to a server. You can convert HTML strings or local HTML files (including file and content URIs on Android).

React Native and Flutter SDKs

Our React Native SDK and Flutter SDK provide HTML-to-PDF conversion for cross-platform mobile development. Both SDKs use native implementations under the hood (WebView on Android, WebKit on iOS), so you write one codebase that works on both platforms.

In Flutter, the generatePdfFromHtmlString and generatePdfFromHtmlUri methods return a path to the generated PDF file. The React Native SDK offers similar PDF generation capabilities.

Beyond conversion, Nutrient’s mobile SDKs include viewing, annotation, form filling, and digital signature features.

Zapier and Power Automate

Zapier integration and Power Automate connectors bring HTML-to-PDF conversion to no-code workflows. You can trigger PDF generation from events in other apps without writing any code.

These integrations let you automate HTML-to-PDF generation as part of larger workflows — for example, generating documents from templates or form submissions. The PDF generation happens on Nutrient’s servers, and you receive the finished document in your workflow.

What you can build with Nutrient

Invoices — Generate branded invoices from HTML templates with dynamic data, watermarks, and automatic delivery to customers.

Compliance reports — Add digital signatures, encryption, and tamper-evident seals for SOC 2, HIPAA, or financial audits.

Contracts — Convert HTML contracts to PDF with fillable signature fields.

Customer exports — Let users download reports, statements, or receipts as PDFs from your web app.

Document pipelines — Chain HTML conversion with OCR, redaction, and merging in a single API call.

HTML-to-PDF conversion methods compared

Common issues when converting HTML to PDF

FAQ

Conclusion

For one-off conversions, your browser’s print function works. For production applications that need consistent output and automated workflows, Nutrient provides self-hosted, cloud, and SDK options with Chromium-based rendering and enterprise security.

Start your free trial to test HTML-to-PDF conversion with no watermarks.