Integrations

Use HTML to Image in the stack you already work with.

There are official SDKs for PHP, JavaScript, Python and Ruby, framework packages for Laravel and Django, plugins for WordPress, Statamic and Craft CMS, and an Action for generating assets in CI. Each one covers the same three jobs: turning your markup into an image, capturing a live URL, and producing a vector PDF. Each page below is a complete implementation guide for that ecosystem, not a signpost back to the reference.

Get an API key Read the API reference

SDKs and languages

Typed clients for the three render endpoints, maintained alongside the API itself.

PHP A typed, framework-agnostic Composer package built on Guzzle. Renders HTML, captures URLs and produces PDFs from any PHP application. Official SDK JavaScript A zero-dependency, fully typed npm client for Node.js, Bun, Deno and edge runtimes, with dual ESM and CommonJS builds. Official SDK Python A zero-dependency, fully typed client with synchronous and async APIs, save and download helpers, and a bundled command line tool. Official SDK Ruby A zero-dependency gem built on Net::HTTP, with a Railtie, an install generator and Active Storage and Active Job patterns. Official SDKRails support

Frameworks

Framework-native packages that add config, storage, queueing and template rendering.

Laravel A facade, published config, filesystem storage helpers and an artisan health check, all auto-discovered. Renders Blade views straight to PNG or PDF. Official package Django Automatic Open Graph images for your models: a mixin, a registry, template tags, an admin panel and a bulk management command. Official package

Content management systems

Install, connect an API key and every entry gets a share image rendered from your own design.

WordPress An Open Graph image for every post and page, five bundled designs, and hand-off to Yoast, Rank Math, AIOSEO or SEOPress. Plugin directory review in progress Statamic Automatic Open Graph images for your entries, designed as an ordinary Antlers or Blade view, with a Control Panel preview. Official addon Craft CMS Automatic Open Graph images for your entries, designed as a Twig template, generated through the Craft queue on save. Official plugin

Automation and DevOps

Generate assets from a pipeline, so images are produced where the content changes.

GitHub Actions Render HTML, screenshot a URL or fill a template from a workflow step, with input hashing so unchanged renders cost nothing. Official Action Make A native Make app is in development. Until it lands, the HTTP module calls the API directly. Coming soon

The same call in four languages

Every SDK wraps one REST API, so the shape of a render is the same wherever you call it from: a document in, a hosted URL out.

$client = new Html2img\Html2imgClient(getenv('HTML2IMG_API_KEY'));

$response = $client->html(new Html2img\Request\HtmlRequest(
    html: $document,
    width: 1200,
    height: 630,
));

echo $response->url;

import { Html2img } from '@html2img/client';

const client = new Html2img(process.env.HTML2IMG_API_KEY);

const response = await client.html({ html: document, width: 1200, height: 630 });

console.log(response.url);

from html2img import Html2img

client = Html2img()  # reads HTML2IMG_API_KEY from the environment

response = client.html(document, width=1200, height=630)

print(response.url)

require "html2img/client"

client = Html2img::Client.new # reads HTML2IMG_API_KEY from the environment

response = client.html(document, width: 1200, height: 630)

puts response.url

Not in one of these languages? Any HTTP client works. POST JSON to https://app.html2img.com/api/html with an X-API-Key header, as described in the getting started guide.

What every integration shares

The packages differ in shape because the ecosystems do. What they render, and how they fail, does not.

One key, every endpoint

The same API key renders HTML, captures screenshots, fills named templates and produces PDFs. No separate products, no separate billing.

Real Chrome, everywhere

Every package posts to the same renderer, so flexbox, grid, custom properties, web fonts and inline JavaScript behave exactly as they do in your browser.

Nothing to host

No Chrome binary in your image, no Puppeteer version drift, no memory ceiling to tune. Your application makes one HTTP request.

Typed failures

Each SDK maps every API status onto its own exception or error class, so an out-of-credits response is something you can catch, not a string you have to parse.

Where to look next

Integration pages cover how to use the API from your stack. Two other sections cover everything that is not stack-specific.

Pick your stack and start rendering

50 free credits when you sign up. One credit renders one image or one PDF.

Get an API key See pricing