# HTML Rendering Overhead and Lightweight Alternatives
`HtmlStamper`, `HtmlHeaderFooter`, and HTML-based watermarking all render through a full browser before the content lands in your PDF. That gives you accurate layout and styling, but it also carries a cost worth understanding before you reach for it.
## Why HTML Rendering Is Heavy
Any time IronPDF processes HTML for output, whether it is a header, footer, watermark, or stamped content, it spawns a **headless Chromium browser instance** under the hood. That browser renders the HTML to pixel-perfect output, which is then merged into the final PDF.
The approach guarantees compatibility with complex HTML, CSS, and JavaScript. It also affects four things:
- **Performance and resource usage:** spinning up a browser is a heavyweight operation that consumes CPU and memory, especially under high throughput.
- **Threading and concurrency:** multiple simultaneous render operations contend for system resources and can create bottlenecks.
- **Runtime requirements:** Chromium adds dependencies that may change application behavior in containers or sandboxed servers.
- **Output size:** rendered HTML embeds full layouts and styling, which can inflate the size of the final PDF.
## When To Use the Text APIs Instead
For simple text-based content such as plain headers, footers, or watermarks, you do not need the full HTML pipeline. IronPDF ships lightweight drawing APIs that skip the browser step entirely. They run faster, use fewer resources, and avoid the extra runtime dependencies.
### Option 1: DrawText / DrawBitmap
Draws static text or images directly onto pages with no HTML or CSS rendering. `DrawText()` provides overloads for font, color, and size, making it a direct replacement for `HtmlStamper` and header/footer content that needs styling.
### Option 2: TextHeaderFooter
Adds simple headers and footers without invoking a browser. Reach for this when the header or footer is plain text rather than a styled layout.
### Option 3: ApplyStamp with TextStamper
Handles watermarking with minimal overhead. The `TextStamper` object exposes properties for text style, fonts, and opacity, which makes it a better fit than an HTML-based stamp or watermark.
[[t:(Match the tool to the content: keep the HTML APIs for genuinely complex layouts, and route plain text headers, footers, and watermarks through the drawing APIs to cut the per-render cost.)]]
HtmlStamper, HtmlHeaderFooter, and HTML-based watermarking all render through a full browser before the content lands in your PDF. That gives you accurate layout and styling, but it also carries a cost worth understanding before you reach for it.
Why HTML Rendering Is Heavy
Any time IronPDF processes HTML for output, whether it is a header, footer, watermark, or stamped content, it spawns a headless Chromium browser instance under the hood. That browser renders the HTML to pixel-perfect output, which is then merged into the final PDF.
The approach guarantees compatibility with complex HTML, CSS, and JavaScript. It also affects four things:
Performance and resource usage: spinning up a browser is a heavyweight operation that consumes CPU and memory, especially under high throughput.
Threading and concurrency: multiple simultaneous render operations contend for system resources and can create bottlenecks.
Runtime requirements: Chromium adds dependencies that may change application behavior in containers or sandboxed servers.
Output size: rendered HTML embeds full layouts and styling, which can inflate the size of the final PDF.
When To Use the Text APIs Instead
For simple text-based content such as plain headers, footers, or watermarks, you do not need the full HTML pipeline. IronPDF ships lightweight drawing APIs that skip the browser step entirely. They run faster, use fewer resources, and avoid the extra runtime dependencies.
Option 1: DrawText / DrawBitmap
Draws static text or images directly onto pages with no HTML or CSS rendering. DrawText() provides overloads for font, color, and size, making it a direct replacement for HtmlStamper and header/footer content that needs styling.
Option 2: TextHeaderFooter
Adds simple headers and footers without invoking a browser. Reach for this when the header or footer is plain text rather than a styled layout.
Option 3: ApplyStamp with TextStamper
Handles watermarking with minimal overhead. The TextStamper object exposes properties for text style, fonts, and opacity, which makes it a better fit than an HTML-based stamp or watermark.
Tips: Match the tool to the content: keep the HTML APIs for genuinely complex layouts, and route plain text headers, footers, and watermarks through the drawing APIs to cut the per-render cost.
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.
