🌐
Renders like Chrome
The rendering engine is real Chrome. Flexbox, grid, custom properties, modern fonts and JavaScript work exactly as they do in your browser. There is no second compatibility model to maintain.
HTML to Image
We render HTML to PNG so you don't have to host headless Chrome.
HTML to Image launched as a side project to solve a recurring problem in agency work. Clients kept asking for dynamic Open Graph images, automated invoice graphics, and screenshot APIs, and every team kept rolling their own Puppeteer setup on Lambda. Each one came with the same broken parts: cold starts, font loading bugs, memory limits, and a custodian rotation when the original engineer left. We built HTML to Image so that work would only need to happen once.
The architecture choice was deliberate. We render with real Chrome, not Satori or canvas-based shortcuts, because pixel-perfect parity with the browser matters when the same HTML and CSS already powers your product. If a layout works in your design preview, it works in the API. If it breaks in the API, it breaks in your browser. There is one rendering target to debug, not two.
We charge for renders, not seats. The free tier covers 25 images a month for the lifetime of the account. A team of 30 pays the same as a single developer at the same render volume. See pricing for the credit ladder.
What's different
🧩
Templates plus raw HTML
Use named templates for common shapes (invoices, OG images, code screenshots) or post your own HTML for full control. Mix the two as your needs grow.
Browse templates →👥
No per-seat charges
Pricing scales with credits, not users. A team of 30 pays the same as a single developer at the same render volume. Every plan includes every feature.
See pricing →Architecture
Renders run on isolated Chrome instances, one per request, so a slow page on one render does not block another. Finished PNGs land on the i.html2img.com CDN, the same CDN that fronts this marketing site. Slow renders, including full-page captures and high-DPI exports, can be delivered async via webhooks. Hot-path renders return synchronously inside a 30 second budget.
Trust
⚡
Uptime target
99.9 percent monthly. Renders that fail because of an outage do not consume credits.
✉️
Support response
One business day for paid plans. Reach out via the contact form.
Contact us →💳
Billing transparency
Cancel from the dashboard at any time. No proration penalty. Downgrade allowed at the next renewal.
See pricing →