Skip to content

CurlShot, an HTML/CSS to Image alternative

Pick CurlShot if most of your images are screenshots of live pages or HTML you send, and you want PDF, scrolling video, ad and cookie-banner blocking in the same API, with a lower price per 1,000 on the entry plans. Pick HTML/CSS to Image if you design images from reusable templates in its visual editor, want each image to keep a permanent hosted address while your account is active, or need Zapier and Make apps. Both render pages and HTML in a real Chrome, take full-page captures, hide cookie banners, offer dark mode, send webhooks and have an MCP server.

Facts about HTML/CSS to Image checked on .

Features, side by side

Show the features table (19 rows)
FeatureCurlShotHTML/CSS to Image
Free plan100 screenshots a month50 images a month
Screenshots of live pagesYesYes
HTML and CSS as inputYesYes
Markdown as inputYesNot in its parameter list
Full-page screenshotsYesYes
Screenshot of one element (CSS selector)YesYes
Transparent backgroundYesYes
Hide cookie bannersYesYes
Block adsYesBlock requests by URL pattern, paid plans
Dark modeYesYes
PDF outputYesPaid plans
Video of the page scrollingYesNot in its parameter list
Batch in one callUp to 100 per callUp to 25 per request, paid plans
WebhooksPaid plansYes
MCP server for AI agentsYesYes
Reusable templates and a visual editorNoYes
Permanent address for each imageLinks expire; keep your own copyWhile your account is active
Zapier and MakeNoYes
Deliver to your own S3-compatible bucketNoFrom 10,000 images a month

What it costs per month

Monthly plans, billed monthly, before tax. The last column is the plan price divided by the screenshots it includes.

Show the prices (7 rows)
Product and planPer monthScreenshots a monthPer 1,000
CurlShot FreeFree100Free
CurlShot Starter$193,000$6.33
CurlShot Growth$7915,000$5.27
CurlShot Scale$24960,000$4.15
HTML/CSS to Image Basic$141,000$14
HTML/CSS to Image Basic (10,000)$6910,000$6.90
HTML/CSS to Image Pro (100,000)$375100,000$3.75

HTML/CSS to Image counts images, not screenshots. Read the per-1,000 figures as a guide, not an exact match.

Sources: HTML/CSS to Image pricing, and the CurlShot pricing page.

Pick CurlShot when

  • You mostly screenshot live pages and want a lower price per 1,000 on the smaller plans (see the table)
  • You need PDF, a scrolling video, or ad blocking next to the image, from the same API
  • You want a free plan of 100 screenshots a month to build on: HTML/CSS to Image gives 50 images
  • Failed renders and cache hits do not count against your CurlShot plan

Pick HTML/CSS to Image when

  • You design images from reusable templates, in a visual editor, and fill them from data
  • Each image should keep one hosted address for as long as the account is active
  • You want Zapier or Make apps, or renders delivered into your own S3-compatible bucket
  • You need very high volume on one plan: its Scale plans go up to 1,000,000 images a month
  • You already run on it and its image debugger and prices work for you: moving costs time

Move a request over, parameter by parameter

Every CurlShot option is described in the options reference.

Show the parameters table (18 rows)
To do thisCurlShotHTML/CSS to Image
Page addressurlurl
HTML instead of a page addresshtmlhtml
CSS for the pagestylescss
Output formatformatformat
Whole pagefull_pagefull_screen
Viewport widthviewport_widthviewport_width
Viewport heightviewport_heightviewport_height
Mobile viewportviewport_mobileviewport_mobile
Landscape viewportviewport_landscapeviewport_landscape
Pixel densitydevice_scale_factordevice_scale
Hide cookie bannersblock_cookie_bannersblock_consent_banners
Dark modedark_modecolor_scheme
Wait before capturedelayms_delay
One element onlyselectorselector
Print or screen stylesmedia_typemedia_type
Time zonetime_zonetimezone
Transparent backgroundomit_backgroundtransparent_background
Custom request headersheadersheaders

Questions people ask

Is CurlShot a good alternative to HTML/CSS to Image?

For screenshots of live pages and for HTML you send as a request, yes: the options map one to one for most of what you send (see the table), there is a free plan, and the entry plans cost less per 1,000. HTML/CSS to Image is the better fit if your images come from reusable templates, if you want permanent hosted addresses, or if you build on Zapier or Make.

How do I move my requests from HTML/CSS to Image?

Change the address and the credentials (it uses an API ID and key with Basic authentication, CurlShot an access key), then rename the options with the parameter table on this page. Its endpoint returns a JSON link to the stored image; add response_type=json here to get the same shape, or take the file straight from the response.

Does HTML/CSS to Image have a free plan?

Yes, as of the date on this page. Its pricing page lists a free plan of 50 images a month with limited templates and email support, and paid plans from 1,000 images a month.

Do both count a screenshot the same way?

Not exactly. HTML/CSS to Image counts image credits and reuses an identical recent image without a new credit through its dedupe option. CurlShot counts one successful render as one screenshot, and a failed render or a cache hit costs nothing. Read each pricing page for the full rules.

Sources: HTML/CSS to Image pricing, HTML/CSS to Image API parameters. Checked on 9 November 2026; prices and features change, so check them before you decide.

Try CurlShot on your own pages

Send the requests you send today, with the parameters renamed, and compare the results yourself. No card needed.