---
canonical: 'https://htmlcsstoimage.com/compare/cloudflare-browser-run'
title: 'HTML/CSS to Image vs Cloudflare Browser Run: Features & Costs'
description: 'Cloudflare Browser Run (formerly Browser Rendering) gives Workers a managed browser. HTML/CSS to Image adds templates, hosting, and image reuse on top.'
---

# HTML/CSS to Image vs Cloudflare Browser Run

Cloudflare Browser Run gives your Workers app a managed browser. HTML/CSS to Image gives you the rest of the image pipeline too: templates, signed URLs, hosting, and reuse.

[View this comparison on the website](https://htmlcsstoimage.com/compare/cloudflare-browser-run)

## The short answer

**Choose HTML/CSS to Image if:**

- You want finished, hosted images from one API call, not a browser to wire up.
- You want templates, a visual editor, and signed URLs for Open Graph and email images.
- Your image jobs come in bursts, and you'd rather not manage Quick Actions and session limits.
- You want per-image pricing instead of browser-hour billing.

**Choose Cloudflare Browser Run if:**

- Your app already runs on Workers, and images are one part of a bigger browser workflow.
- You need crawling, content extraction, or scripted sessions through Puppeteer, Playwright, or CDP.
- Your captures are short, so browser-time pricing works out cheaply.

## At a glance

| Capability | HTML/CSS to Image | Cloudflare Browser Run |
| --- | --- | --- |
| Render controls | Very flexible (90/100) | Very flexible (90/100) |
| Request rate limits | Yes — No per-minute limits | Partial — 30 Quick Actions/sec, 200 concurrent browsers |
| Hosted image URLs | Yes | Not available — Use your own storage and delivery |
| PDF rendering | Partial — Paid plans | Yes |
| Overages | Optional — $10/1,000, or $50/10,000 on Scale | Yes — $0.09 per extra browser hour |
| Extra features | Visual template editor<br>Signed template URLs<br>Dynamic OG images without API calls<br>Application-level deduplication | Full browser sessions via Puppeteer, Playwright, or CDP<br>Crawling and content extraction<br>Runs next to your Workers |

## Where they overlap

Both run managed browsers so you don't maintain your own Chromium servers. Cloudflare Browser Run, formerly Browser Rendering, takes screenshots of HTML or a URL through a REST API, with viewport, full-page, clipping, and timing controls. Both also output PDFs.

## What Cloudflare gives you

Browser infrastructure right next to your Workers application. Use Quick Actions for a screenshot or PDF, or drive a full browser session through Puppeteer, Playwright, or CDP. That makes it a good fit when you're also crawling pages, extracting content, or running custom browser steps.

## The part you still build

Cloudflare runs the browser. Saving and serving the images, caching repeat requests, filling in template variables, and retrying failures are up to you. If you already use Workers and R2, those pieces can fit naturally into your stack.

HTML/CSS to Image connects them: a visual designer and saved templates, signed template URLs that create images on request, hosting and CDN delivery, and application-level deduplication. Reusing an existing image URL never consumes another credit.

## Limits

Cloudflare applies separate limits to Quick Actions, at 30 requests per second on Workers Paid, and to browser sessions, at 200 concurrent browsers by default and three new instances per second. Paid limits can be raised on request. HTML/CSS to Image has no concurrency caps or per-minute limits on creating and rendering images.

## Pricing

Cloudflare charges for browser time. Quick Actions use browser-hour billing, and browser sessions also have a concurrency charge. Workers Paid includes 10 browser hours a month, then $0.09 per additional hour. Session concurrency is billed on the monthly average of your daily peak browser count: 10 included, then $2 per additional browser.

Add your Workers plan, storage, and delivery to those browser costs. HTML/CSS to Image prices the whole workflow per created image, with hosting, reuse, and output variants included.

### Getting started

**HTML/CSS to Image:** $14/month for 1,000 images on Basic.

Includes templates, the visual editor, and hosted image delivery. A free plan includes 50 images per month.

**Cloudflare Browser Run:** Workers Free includes 10 minutes of browser time per day.

Free usage is time-based rather than an image allowance.

### A production image service

**HTML/CSS to Image:** $69/month for 10,000 images on Basic.

Optional overages cost $10 per 1,000 images. Includes templates, hosted image delivery, storage destinations, and bring-your-own proxies at this volume.

**Cloudflare Browser Run:** Browser-time billing, plus your Workers plan and image storage and delivery.

Browser-session concurrency adds a separate charge, which doesn't apply to Quick Actions.

## Common questions

### Is Cloudflare Browser Run cheaper than HTML/CSS to Image?

It can be, for short captures. Workers Paid includes 10 browser hours a month, then $0.09 an hour, and browser sessions add a concurrency charge. Storage and delivery are extra. HTML/CSS to Image charges per image, from $14/month for 1,000, with hosting included.

### Is Cloudflare Browser Rendering the same as Browser Run?

Yes. Cloudflare renamed Browser Rendering to Browser Run.

### Does Cloudflare Browser Run host the screenshots?

No. The screenshot endpoint returns the image, and storing and serving it is up to you, often with R2. HTML/CSS to Image returns a hosted image URL with CDN delivery included.

### Can I use templates with Cloudflare Browser Run?

Not out of the box. You'd build the HTML and fill in the variables in your Worker. HTML/CSS to Image has saved templates, a visual editor, and signed template URLs.

## Comparison details

### Parallel rendering

**HTML/CSS to Image:** Send image creation and rendering requests in parallel, with no concurrency caps or per-second or per-minute rate limits.

Image credits and plan limits still apply.

**Cloudflare Browser Run:** Workers Paid allows 30 Quick Actions requests per second. Browser sessions have a default 200 concurrent-browser limit and three new instances per second.

HCTI has no request-rate or concurrency limits to manage.

### Image hosting and reuse

**HTML/CSS to Image:** Hosting and CDN delivery are included. Application-level caching keeps an existing image URL reusable, even after a CDN cache miss, without consuming another image credit.

Paid plans keep images while your account is active. Custom-storage-only images use your own delivery.

**Cloudflare Browser Run:** The screenshot endpoint returns image output. Connect it to your own storage, delivery, and cache logic.

HCTI includes persistent image URLs and application-level reuse.

## Research and sources

Last reviewed: 2026-09-30

Reviewed official Cloudflare Browser Run documentation, pricing, and limits alongside HCTI documentation. Quick Actions and browser-session limits are distinguished. Pricing describes billing models, not a benchmark or a calculated per-image infrastructure bill. No comparative captures were performed.

- [HCTI API reference](https://docs.htmlcsstoimage.com/getting-started/using-the-api/) (checked 2026-09-22)
- [HCTI render readiness](https://docs.htmlcsstoimage.com/parameters/render_when_ready/) (checked 2026-09-22)
- [Cloudflare Browser Run overview](https://developers.cloudflare.com/browser-run/) (checked 2026-09-30)
- [Cloudflare screenshot endpoint](https://developers.cloudflare.com/browser-run/quick-actions/screenshot-endpoint/) (checked 2026-09-30)
- [HCTI rate and usage limits](https://docs.htmlcsstoimage.com/getting-started/using-the-api/rate-limits/) (checked 2026-09-22)
- [Cloudflare Browser Run limits](https://developers.cloudflare.com/browser-run/limits/) (checked 2026-09-30)
- [HCTI plans and pricing](https://htmlcsstoimage.com/pricing) (checked 2026-09-30)
- [HCTI storage destinations](https://docs.htmlcsstoimage.com/guides/advanced/storage-destinations/) (checked 2026-09-22)
- [Cloudflare Browser Run pricing](https://developers.cloudflare.com/browser-run/pricing/) (checked 2026-09-30)
- [Cloudflare Quick Actions](https://developers.cloudflare.com/browser-run/quick-actions/) (checked 2026-09-30)
- [HCTI image templates](https://docs.htmlcsstoimage.com/getting-started/templates/) (checked 2026-09-22)
- [HCTI template editor](https://docs.htmlcsstoimage.com/template-editor/) (checked 2026-09-22)
- [HCTI duplicate detection](https://docs.htmlcsstoimage.com/guides/advanced/duplicate-detection/) (checked 2026-09-22)

## Try it out

[Try the live image demo](https://htmlcsstoimage.com/compare/cloudflare-browser-run#demo)

## Related comparisons

- [HTML/CSS to Image vs Browserless](https://htmlcsstoimage.com/compare/browserless.md)
- [HTML/CSS to Image vs Playwright](https://htmlcsstoimage.com/compare/playwright.md)
- [HTML/CSS to Image vs ApiFlash](https://htmlcsstoimage.com/compare/apiflash.md)
- [HTML/CSS to Image vs Puppeteer](https://htmlcsstoimage.com/compare/puppeteer.md)
- [HTML/CSS to Image vs APITemplate.io](https://htmlcsstoimage.com/compare/apitemplateio.md)
- [HTML/CSS to Image vs Urlbox](https://htmlcsstoimage.com/compare/urlbox.md)

## Get started

[Start creating free](https://htmlcsstoimage.com/join) · [Pricing](https://htmlcsstoimage.com/pricing.md) · [Documentation](https://docs.htmlcsstoimage.com)

We tried to make this an honest and fair comparison. We last updated the details on September 30, 2026. If you represent Cloudflare Browser Run and want to correct the record, please [email us](mailto:support@htmlcsstoimage.com).