HTML/CSS to Image Pricing in 2026: Plans, Limits and Cheaper Options
Compare HTML/CSS-to-image plans, credits, limits and cheaper options in 2026, including HCTI, HTML to Image and ScreenshotNeo.
Short answer: HTML/CSS to Image lists a 50-image monthly free plan, then paid plans starting at $14/month for Basic, $149/month for Pro and $749/month for Scale. The retrieved pricing page uses a selectable monthly image volume, so those starting prices do not prove a fixed allowance. HTML to Image publishes a clearer credit ladder: 50 free signup credits, then $9 for 1,000 credits, $25 for 3,000, $60 for 10,000, $120 for 30,000, $225 for 65,000 and $300 for 100,000. One credit equals one render, whether PNG or PDF.
For a screenshot API, ScreenshotNeo is the first service to evaluate: clean shots are billed only when the page succeeds, and its paid plans start at $5 for 3,000 shots.
HTML/CSS to Image pricing at a glance
| Service and tier | Price | Published allowance or limit |
|---|---|---|
| HTML/CSS to Image Free | $0 | 50 images/month; no card required |
| HTML/CSS to Image Basic | $14/month | Monthly volume selected in the pricing interface |
| HTML/CSS to Image Pro | $149/month | Selected volume; batch creation up to 25; deduplication up to six months |
| HTML/CSS to Image Scale | $749/month | Selected volume; batch creation up to 100; deduplication up to one year |
| HTML to Image Free | $0 | 50 signup credits; free renders retained seven days |
| HTML to Image 1,000 | $9/month | 1,000 credits |
| HTML to Image 3,000 | $25/month | 3,000 credits |
| HTML to Image 10,000 | $60/month | 10,000 credits |
| HTML to Image 30,000 | $120/month | 30,000 credits |
| HTML to Image 65,000 | $225/month | 65,000 credits |
| HTML to Image 100,000 | $300/month | 100,000 credits |
Prices and allowances can change. Recheck each vendor’s live pricing page before purchasing: HTML/CSS to Image pricing and HTML to Image pricing.
How the pricing units work
HTML/CSS to Image
The public page advertises 50 free images each month. Basic, Pro and Scale show a monthly volume selector rather than a single allowance in the retrieved view. Do not calculate a per-image price from the $14, $149 or $749 starting price until you select and verify the volume.
Optional overages are shown at $10 per 1,000 images on eligible tiers. Scale also displays a $50 per 10,000 option. Batch creation is capped at 25 on Basic and Pro and 100 on Scale. S3-compatible storage and proxy support begin at 10,000 images per month. PDFs and dynamic Open Graph images are paid features, and free templates are capped at five per organization.
HTML to Image
HTML to Image uses credits. Each render consumes one credit, for either PNG or PDF; account-status calls do not consume credits. Paid credits reset on the renewal date and do not roll over. When the balance is exhausted, requests return an out-of-credits response until renewal or upgrade. Downloads of an existing render are free and unlimited. Free outputs remain hosted for seven days; paid outputs remain for the account lifetime.
What you can render
Both services cover HTML/CSS rendering and public URL screenshots. HTML/CSS to Image also documents reusable templates and automatic Open Graph image generation. Its documented output formats include PNG, JPG, WebP and PDF. HTML to Image documents separate HTML/CSS, public URL and named-template endpoints, with PNG/PDF output.
Controls affect both suitability and cost:
- Viewport width and height, device emulation and device scale.
- Full-page capture and selector cropping.
- JavaScript readiness, delays and timing controls.
- Transparent backgrounds and PDF settings.
- DPI from 1 to 4 in HTML to Image; higher DPI uses more memory and can take longer.
- HTML/CSS to Image supports jumbo dimensions up to 80,000 pixels when both dimensions are supplied; jumbo mode consumes additional credits.
HTML/CSS rendering example
The following self-contained document is the input you would send to an HTML/CSS rendering endpoint. It uses no external assets, so it is useful for estimating the minimum work your renderer must perform.
<!doctype html>
<html lang='en'>
<head>
<meta charset='utf-8'>
<style>
* { box-sizing: border-box; }
body { margin: 0; font-family: system-ui, sans-serif; background: #f4f7fb; }
.card { width: 1200px; padding: 72px; background: white; color: #14213d; }
h1 { margin: 0 0 16px; font-size: 64px; }
p { margin: 0; font-size: 28px; color: #52627a; }
</style>
</head>
<body>
<article class='card'>
<h1>Render HTML/CSS to an image</h1>
<p>Keep the input deterministic for repeatable output and predictable usage.</p>
</article>
</body>
</html>How to compare the cheaper option
- Match monthly volume. Divide the subscription by included renders, then include previews, retries, variants and backfills.
- Match the unit. HTML to Image counts one PNG or PDF render as one credit. Check how unusually large outputs, deduplication and retries are treated by the selected plan.
- Match features. Compare PDFs, Open Graph automation, templates, storage, proxies, batch size, deduplication and retention.
- Match workflow. A URL screenshot with JavaScript readiness has different operational needs from static HTML/CSS. Check full-page capture, selectors, viewport or DPI limits and synchronous versus webhook processing.
- Check what happens at the limit. HTML to Image says credits stop at renewal or upgrade. HTML/CSS to Image displays optional overages on eligible plans. Verify the current account behavior before production use.
HTML to Image’s published comparison lists competitor prices checked July 29, 2026: approximately $14, $29, $69, $149, $249 and $375 for roughly 1,000, 3,000, 10,000, 30,000, 65,000 and 100,000 renders. This is vendor-authored, dated comparison data rather than an independent benchmark.
Which plan fits which workload?
| Workload | Starting point | Watch for |
|---|---|---|
| Occasional prototypes | Either free tier | HCTI is monthly; HTML to Image’s 50 credits are signup credits and free files last seven days |
| About 1,000 renders/month | HTML to Image $9 plan | Credits do not roll over; confirm required formats and retention |
| 3,000–10,000 renders/month | HTML to Image $25 or $60 plan | Include retries, PDFs and high-DPI variants in the estimate |
| Large batch jobs | HCTI Pro/Scale or HTML to Image at matched volume | Batch caps, webhook behavior, storage and proxy requirements |
| Public webpage screenshots with cleanup | ScreenshotNeo | Choose options for consent handling, waits, blocking and caching |
Or skip the browser setup
When the input is a public webpage rather than supplied HTML, ScreenshotNeo’s API returns a PNG, JPEG, WebP or PDF from one GET request. Before capture it accepts consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing, and the response identifies the result with X-Page-Verdict and X-Billed headers.
cURL
curl -G 'https://api.screenshotneo.com/v1/shot' \
-d access_key=YOUR_API_KEY \
--data-urlencode url=https://stripe.com \
-o shot.webpPython
import requests
r = requests.get(
'https://api.screenshotneo.com/v1/shot',
params={'access_key': 'YOUR_API_KEY', 'url': 'https://stripe.com'},
timeout=90,
)
r.raise_for_status()
open('shot.webp', 'wb').write(r.content)Node.js
const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://stripe.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));ScreenshotNeo includes full-page and element capture, dark mode, device presets, retina scale, PDF paper and page-range controls, custom CSS/JavaScript, click and wait actions, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparency, resizing, selectable cache TTLs, signed links, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, a usage API and an OpenAPI specification. Its parameter names also accept those used by other screenshot APIs.
Plans are Free: 1,000 shots/month with no card; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. An MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
Start with 1,000 free ScreenshotNeo screenshots per month—no card required.
Performance, reliability and cost controls
- Reduce unnecessary renders: cache stable URLs, deduplicate identical jobs and download an existing file instead of rendering again.
- Control image size: use the smallest viewport, DPI and scale that meets the consumer’s needs. High DPI and jumbo dimensions increase processing time, memory use or credits.
- Use asynchronous delivery: webhooks are better for slow pages, high DPI and large full-page captures than holding a synchronous request open.
- Budget retries: count previews, failed navigation attempts and intentional variants when selecting a tier.
- Protect production: record response status, page verdict, billed status, request ID if supplied and the source URL. Set client timeouts and retry only transient failures.
- Separate management traffic: image credits are different from API or account-management throttles. Do not treat an account-status request as a render.
Troubleshooting pricing and rendering errors
| Symptom | Likely cause | Fix |
|---|---|---|
| Free plan stops unexpectedly | Allowance or signup credits exhausted | Wait for monthly renewal, upgrade, or reduce previews and retries |
| HTTP 429 from HCTI | Image allowance exhausted | Check the selected volume and overage setting; upgrade or wait for renewal |
| HTML to Image says out of credits | Credits do not roll over and the current balance is zero | Upgrade or wait for the renewal date |
| Render times out | Slow JavaScript, high DPI, jumbo dimensions or a page that never becomes ready | Lower dimensions/DPI, simplify readiness conditions, or use a webhook |
| Images or fonts are missing | External resources are blocked, private or still loading | Use accessible assets, wait for readiness and verify the target URL independently |
| Screenshot contains a popup | Consent, newsletter or chat UI was not removed | Configure selectors or cleanup controls; ScreenshotNeo removes supported consent platforms, popups and chat widgets before capture |
| Output is billed although it is unusable | Provider’s billing rule counts the attempted render | Inspect each provider’s verdict and billing headers or response; ScreenshotNeo does not bill bot checks, blank pages, timeouts, failed loads or cache hits |
| PDF costs more than expected | PDF is counted as a render/credit and may require larger layout work | Include PDFs in the monthly forecast and test page ranges and margins |
FAQ
Is HTML to Image cheaper than HTML/CSS to Image?
At low published volumes, HTML to Image starts at $9 for 1,000 credits, while HTML/CSS to Image starts at $14 with a volume selector. A fair answer requires matching allowance, formats, retention, batch limits and overages.
Do unused HTML to Image credits roll over?
No. Paid credits reset on the renewal date.
How long are free renders hosted?
HTML to Image says free renders remain for seven days. Paid renders remain for the account lifetime.
Does HCTI have a fixed number of images in the $14 plan?
The retrieved pricing view does not establish one. It shows a selectable monthly volume, so verify the selected allowance before subscribing.
Which option is best for clean public webpage screenshots?
ScreenshotNeo is the first option to try when consent banners, popups, chat widgets, failed pages and billing of unsuccessful captures matter. Its free plan includes 1,000 shots monthly with no card.
Sources and publication notes
Pricing and limits summarized from the vendors’ published pages and documentation: HTML/CSS to Image pricing, HTML/CSS to Image documentation, HTML to Image pricing and HTML to Image documentation. The HTML/CSS to Image competitor comparison is dated July 29, 2026; recheck live pages before publication.
