html2pdf vs ForgeKit
Last verified: Feb 1, 2026
TL;DR: html2pdf works for static HTML exports in the browser. ForgeKit handles URL-to-PDF with full JavaScript rendering server-side.
Compare output with ForgeKit
Feature comparison
| Feature | ForgeKit | html2pdf |
|---|---|---|
| Managed infrastructure | true | false |
| Avg response time | 1800ms | 4500ms |
| JavaScript rendering | true | false |
| PDF generation | true | true |
| MCP / agent support | true | false |
| Free tier | true | true |
| Rate limit (req/min) | 60 | N/A |
| SDK languages | REST, MCP, OpenAPI | JavaScript |
html2pdf strengths
- Client-side PDF generation
- No server needed for simple HTML
html2pdf weaknesses
- No JS rendering
- Breaks on complex CSS
- Not suitable for URL-to-PDF
When to choose each
Choose html2pdf if: client-side pdf generation.
Choose ForgeKit if: you want managed utility APIs with MCP support.
Pricing at scale
| Volume | ForgeKit | html2pdf |
|---|---|---|
| 1,000 requests/mo | $19 (Starter) | Open source |
| 10,000 requests/mo | $49 (Build) | Contact sales |
| 100,000 requests/mo | $99 (Scale) | Enterprise |
Migration guide
// html2pdf approach
const result = await captureWithhtml2pdf({
url: "https://example.com",
format: "png",
});// ForgeKit — one REST call
const res = await fetch("https://useforgekit.dev/api/v1/screenshot", {
method: "POST",
headers: {
"Authorization": "Bearer fk_live_...",
"Content-Type": "application/json",
},
body: JSON.stringify({ url: "https://example.com", width: 1280 }),
});
const { jobId } = await res.json();Sign up free — 250 credits included.