HTML To PDF
Render HTML content into a PDF document, capturing the layout, styling, and structure of the rendered page in a printable and shareable format.
What You Can Control With PDF Action
With the PDF action, you can control how HTML content is rendered into a PDF, including page size, layout behavior, and output formatting.
- HTML content used for PDF rendering
- Page size and document layout settings
- Rendering viewport dimensions
- Handling of page breaks in the output PDF
- Generating a single PDF from rendered HTML
- Preparing rendered PDFs for storage or distribution
H2I Endpoint Capabilities
The H2I endpoint converts HTML markup into visual outputs using predictable rendering rules, enabling developers to generate images or PDFs from dynamic content reliably.
HTML to Image
Renders HTML markup into a raster image output using controlled viewport sizing and layout calculation, producing consistent visual results for server-side image generation.
HTML to PDF
Renders HTML markup into a paginated PDF output using controlled viewport sizing and layout calculation, producing consistent document-ready results for server-side PDF generation.
Why Developers Use the H2I Endpoint
Predictable Rendering Behavior
The H2I endpoint enforces strict rendering rules that produce consistent visual output across requests, allowing developers to rely on repeatable results for dynamic content.
No Rendering Infrastructure to Manage
Developers do not need to maintain browsers, rendering engines, or headless services. HTML input is rendered securely without exposing execution environments.
Suitable for Production Automation
H2I is designed for background jobs, scheduled rendering, and automated workflows where reliability and non-interactive execution are required.
Flexible Output Formats
The endpoint supports both image and PDF outputs from the same HTML input, allowing a single source of truth for multiple delivery formats.
Secure Output Delivery
Rendered files are returned through structured responses with controlled output URLs, making integration with applications and storage systems safe and straightforward.
Layout-Accurate Results
Viewport sizing, scaling, and documented print-related options allow developers to control server-side rendering behavior and produce consistent visual output without relying on client-side rendering.
Clean API Surface
The endpoint avoids hidden behaviors and internal flags, ensuring integrations remain stable and understandable over time.
Use Cases Powered By H2I Endpoint
Email & Template Rendering
Use the H2I endpoint to render HTML email or template layouts into images or PDFs using server-side rendering. This allows teams to generate consistent visual previews of templates for review, testing, or delivery workflows without relying on client-side browsers, ensuring the same output across environments and automated systems.
Report & Document Generation
Use the H2I endpoint to convert HTML-based reports or documents into image or PDF outputs with controlled viewport sizing and layout calculation. This enables reliable generation of documents for automated reporting, exports, or archival use, without managing rendering infrastructure or browser environments.
UI Snapshot Generation
Use the H2I endpoint to render HTML representations of interfaces into static image outputs for snapshots, previews, or visual records. This is useful for capturing consistent UI states in automated workflows, testing pipelines, or documentation systems without requiring interactive rendering on the client side.
Marketing Asset Creation
Use the H2I endpoint to render HTML-based designs into image or PDF assets for banners, visuals, or promotional materials. By relying on server-side rendering rules, teams can produce consistent marketing outputs from a single HTML source without manual capture or environment-specific rendering differences.
Automated Rendering Pipelines
Integrate the H2I endpoint into background jobs or scheduled workflows to render HTML into images or PDFs automatically. This supports scalable, non-interactive rendering pipelines where reliability, consistency, and predictable output are required without maintaining headless browsers or rendering infrastructure.
Frequently Asked Questions
H2I Endpoint FAQ
1. What is the H2I endpoint used for?
The H2I endpoint is used to render HTML content into generated outputs through the Davix H2I API. Its core purpose is to convert HTML layouts, templates, or dynamically generated markup into image or PDF files for use in applications, websites, and automated workflows.
2. What does H2I mean?
H2I stands for HTML to Image. This reflects the original core capability of the platform: turning HTML content into image output. The platform also supports HTML-to-PDF rendering, but HTML rendering remains the defining capability of the H2I service.
3. What actions does the H2I endpoint support?
The public H2I endpoint supports two main actions: image and pdf. This allows you to use the same rendering service to generate either image output or PDF output from HTML content.
4. What kind of input does the H2I endpoint accept?
The H2I endpoint accepts structured requests that include an
actionvalue andhtmlcontent. In practice, this means you send HTML markup and request either image or PDF output, along with any relevant rendering parameters for the requested result.5. What can I build with the H2I endpoint?
The H2I endpoint is well suited for use cases such as visual report generation, automated documents, marketing assets, template-based output generation, and HTML-based PDF creation. It is especially useful when your system already generates HTML dynamically and needs to turn that content into files automatically.
6. Can I use my own HTML templates?
Yes. The H2I endpoint is designed for user-provided HTML layouts, templates, and dynamically generated markup. This makes it suitable for systems that already use HTML as their layout layer and want to generate image or PDF outputs from that content.
7. Can the H2I endpoint generate both images and PDFs from HTML?
Yes. HTML-to-image and HTML-to-PDF rendering are both central capabilities of Davix H2I, and the public H2I endpoint supports both output types.
8. Is the H2I endpoint only for developers?
No. Direct API usage is developer-friendly, but Davix H2I is designed to support a broader range of users through multiple integration paths. In addition to direct API usage, the platform also supports website and automation environments through integrations such as WordPress and n8n.
9. Can I use the H2I endpoint in automated workflows?
Yes. One of the key strengths of Davix H2I is its ability to function inside automation workflows. A system can generate HTML from data, send it to the H2I endpoint, and then use the returned image or PDF file as part of a larger automated process.
10. Can I integrate the H2I endpoint into apps, backend systems, or websites?
Yes. Davix H2I is designed to operate across a wide range of environments, including custom applications, backend services, websites, scripts, and workflow systems.
11. Do I need to build my own rendering infrastructure?
No. The H2I service is designed to give you access to rendering and processing capabilities without requiring you to build and maintain that infrastructure yourself. Its value is in making complex backend rendering available through a simple service interface.
12. How do I authenticate requests to the H2I endpoint?
You authenticate requests using your API key. The public
/v1/h2iendpoint supports standard API-key access as part of the Davix H2I public API surface.13. What does a successful H2I response return?
A successful H2I request returns a generated output URL for the rendered file. Depending on the selected action, that output will be the image or PDF file created from your HTML content.
14. Are generated H2I outputs returned as files or URLs?
Generated H2I outputs are returned through output URLs. The public output path for H2I-generated files is under
/h2i/*, and output delivery can use signed URLs depending on platform configuration.15. What happens behind the scenes when I send an H2I request?
When you send a request to Davix H2I, the rendering work is executed by the H2I engine (PixLab). Davix H2I is the product and service layer, while the H2I engine (PixLab) performs the actual backend rendering and output generation.
16. Is the H2I endpoint suitable for agencies, startups, and product teams?
Yes. Davix H2I is positioned as a backend processing service for developers, teams, businesses, startups, agencies, and automation builders who want to add media and document generation features to their systems without managing the underlying infrastructure.
17. What happens if my H2I request is invalid or unsupported?
If a request is invalid, missing required input, or exceeds supported request rules, the API returns a structured error response so your system can detect the issue and respond appropriately. For the full list of H2I-related errors, users should check the Errors and Limits section of the documentation.
18. Are there size or usage limits for the H2I endpoint?
Yes. The H2I endpoint is subject to rendering, validation, and service limits. For the latest usage rules and current limits, users should check the Errors and Limits section of the documentation.
19. What do I get when I buy access to the H2I endpoint?
You get access to the Davix H2I HTML-rendering service through the public API and supported integration paths, allowing your system to generate image and PDF outputs from HTML without building the rendering infrastructure yourself. For plan details and commercial information, users should check the Pricing page.