Cloudinary Website Screenshots vs ScreenshotOne: Features and Pricing

Cloudinary URL2PNG fits teams that want website screenshots to enter an existing Cloudinary image transformation and delivery workflow. ScreenshotOne fits teams looking for a dedicated screenshot API with documented URL, HTML, and Markdown inputs and a broad set of rendering controls. If you want a third option to evaluate first, ScreenshotNeo combines consent-banner cleanup, usage-based billing rules that exclude failed captures and cache hits, and an API with an MCP server for AI agents.

There is no documented head-to-head visual-quality or reliability test in the available sources. Choose based on workflow, required controls and output, volume, rate limits, and the complete account cost—not the listed add-on price alone. Pricing and plan terms can change; verify the current vendor pages before purchasing.

1. The short comparison

Question	Cloudinary URL2PNG	ScreenshotOne
What is it?	An add-on that creates website screenshots within Cloudinary’s image management, transformation, and delivery pipeline.	A dedicated hosted screenshot and rendering API.
Documented inputs	Public website URL.	Website URL, HTML, or Markdown.
Documented outputs	Screenshot image in Cloudinary’s asset workflow, where it can be transformed and delivered.	PNG, JPEG, WebP, GIF, TIFF, AVIF, HEIF, PDF, HTML, or Markdown, according to request options.
Controls highlighted in the docs	Viewport, user agent, and delay.	Element selection, viewport and device emulation, styles, content blocking, waits, and localization, among other options.
Published free allowance	50 screenshots for the URL2PNG add-on.	100 screenshots per month; the pricing page says no credit card is required.
First listed paid tier	Bronze: $6/month for 1,000 add-on screenshots. A paid Cloudinary base plan is also required for paid add-on tiers.	Basic: $17/month for 2,000 screenshots, with a listed start rate of 40 requests/minute.
Best fit	Screenshot assets that belong in an existing Cloudinary media workflow.	A standalone screenshot service where its documented inputs, formats, and request controls fit the job.

These are documented product descriptions, not a claim that either service captures pages more accurately or operates more reliably. See Cloudinary’s URL2PNG documentation, the Cloudinary add-ons marketplace, Cloudinary billing documentation, and ScreenshotOne’s options documentation.

2. ScreenshotNeo: an alternative to try first

ScreenshotNeo is a website screenshot API and MCP server for developers, made by Yorker Media. It belongs at the top of a shortlist when clean captures and clear billing outcomes matter: it accepts cookie and consent banners like a visitor, removes more than 60 known consent platforms plus newsletter popups and chat widgets before capture, and bills only clean shots. Responses identify page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

One GET request returns an image or PDF. For example, this cURL request saves a WebP capture of Stripe:

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -o shot.webp

Equivalent Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Equivalent 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(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));

Read the ScreenshotNeo API documentation for request options and response details. Its documented capabilities include full-page capture with lazy images loaded, CSS-selector element capture, dark mode, 12 device presets and custom viewports, retina scale, PDF settings and page ranges, HTML/CSS rendering, custom CSS and JavaScript, click-before-capture, hiding selectors, selector/delay/network-idle waits, request and resource blocking, custom headers/cookies/user agents/Authorization, timezone and geolocation, transparent backgrounds, image resizing, configurable cache TTL, signed public image links, asynchronous jobs with signed webhooks, batches of up to 100 URLs, a usage API, and an OpenAPI spec. Common parameter names used by other screenshot APIs also work to make migration easier.

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. Every feature is on every plan.

Try ScreenshotNeo free: sign up for 1,000 screenshots a month with no card.

3. How Cloudinary URL2PNG works

URL2PNG is integrated into Cloudinary’s image workflow. It captures a public website through a dynamic delivery URL, then the resulting image can be resized, cropped, filtered, overlaid, and delivered through Cloudinary. This can reduce the number of separate systems involved when the screenshot is another managed image asset.

Cloudinary’s documentation highlights viewport, user-agent, and delay options. By default, URLs using the add-on must be signed or eagerly generated. Cloudinary documents a Console Settings option to allow unsigned add-on transformations. Teams should account for that access model when deciding whether URLs will be generated server-side, pre-generated, or made publicly usable.

Start with the URL2PNG add-on documentation and check the current account’s add-on availability and settings in the marketplace. The exact delivery URL construction depends on your Cloudinary account and chosen transformation, so use Cloudinary’s current docs rather than copying a made-up URL pattern.

4. How ScreenshotOne works

ScreenshotOne is a hosted screenshot and rendering API. Its getting-started guide describes authenticated HTTPS GET or POST requests using an access key, with an optional signature documented as well. The options reference covers URL, HTML, and Markdown inputs and output formats including images, PDF, HTML, and Markdown.

Its options documentation is the place to verify the exact parameter names and combinations for the capture you need. The dossier identifies selectors, viewport and device emulation, custom styles, content blocking, waits, and localization among its controls. Do not infer that a specific behavior is included in a plan or enabled by default without checking the current product documentation.

Useful references: getting started, request options, and pricing.

5. Pricing and quota comparison

The following is a snapshot from official vendor pages observed on October 3, 2026. Prices are published monthly prices and can change.

Service / tier	Listed monthly price	Included screenshots	Important qualification
Cloudinary URL2PNG Free	$0	50	Add-on marketplace tier.
Cloudinary URL2PNG Bronze	$6	1,000	Paid add-on tier; paid add-ons require a paid Cloudinary base plan.
Cloudinary URL2PNG Silver	$30	5,000	Paid add-on tier; add-on cost is separate from the base plan.
Cloudinary URL2PNG Gold	$75	15,000	Paid add-on tier; add-on cost is separate from the base plan.
Cloudinary URL2PNG Titanium	$200	50,000	Paid add-on tier; add-on cost is separate from the base plan.
ScreenshotOne free allowance	$0	100/month	Pricing page says no credit card is required.
ScreenshotOne Basic	$17	2,000	40 requests/minute; $0.009 per extra screenshot.
ScreenshotOne Growth	$79	10,000	80 requests/minute; $0.006 per extra screenshot.
ScreenshotOne Scale	$259	50,000	150 requests/minute; $0.004 per extra screenshot.

Cloudinary’s add-on tiers are not an all-in Cloudinary bill. The billing documentation says add-ons are billed separately from base plans, and paid add-on tiers require a paid base plan. ScreenshotOne’s pricing page says prices exclude VAT. Its pricing FAQ says HTTP, browser, or network failures do not consume quota; a successful capture with visual problems can still count. Cached responses generally do not count when served from cache, while a cache miss or expired entry can cause a new render.

To compare costs for your workload, estimate the number of successful uncached renders, include Cloudinary’s base plan if relevant, account for any overage terms, and check the service’s request-start rate. Do not treat the listed per-plan screenshot allowances as equivalent without checking what each vendor counts.

6. Compare workflow fit and requirements

Choose Cloudinary URL2PNG when

Your application already stores, transforms, and delivers media through Cloudinary.
Screenshots should be managed as part of that image pipeline.
The add-on’s documented viewport, user-agent, and delay controls cover your capture requirements.
Your team can accommodate the add-on registration and signed or eagerly generated URL workflow, or has deliberately configured unsigned transformations.

Choose ScreenshotOne when

You want a standalone screenshot API rather than screenshot generation inside an image delivery platform.
You need one of its documented inputs or output formats, such as HTML/Markdown input or PDF output.
The request-level rendering controls in its options reference match your use case.
The allowance and published request rate fit your expected workload and budget.

Put ScreenshotNeo on the shortlist when

You want consent banners, newsletter popups, and chat widgets removed before capture.
You want response headers that identify page verdict and whether a capture was billed.
You need an MCP server for AI agents, or features such as full-page capture, PDF, batch capture, signed links, custom waits, and request controls.
You want a free monthly allowance of 1,000 and paid plans starting at $5 for 3,000 captures.

These are decision rules inferred from the vendors’ documented workflows and published terms. The documentation does not establish comparative capture accuracy or uptime.

7. Integration and operational checklist

List the actual capture inputs. Decide whether the job starts from a public URL only or needs HTML/Markdown rendering.
Specify the output consumer. Record required image formats, PDF needs, downstream transformations, delivery, and storage.
Write down capture controls. Include viewport, device emulation, waits, selector capture, styling, localization, and content blocking where needed.
Set access rules. For Cloudinary, account for signing or eager generation and the unsigned setting. For ScreenshotOne, protect the access key and follow the documented authenticated request flow.
Define what counts as billable. Review the vendor’s failure, cache, and quota terms, and log request outcomes in your own integration.
Model peak traffic. Compare expected concurrency and burst rate with published per-minute request limits where available.
Price the whole workflow. Include base plan, add-on, overage, VAT where applicable, caching behavior, and any image storage or delivery charges relevant to your existing account.
Recheck pricing before committing. The figures here are a dated snapshot, not a quote.

8. Performance, reliability, and cost considerations

Performance

The source material provides no comparable latency benchmark. A page’s own load behavior, chosen waits, output format, cache state, and required rendering work can all affect the end-to-end time, but the reviewed sources do not support a numerical comparison. For a real workload, measure representative URLs and the complete request path in your environment before choosing a latency-sensitive design.

ScreenshotOne publishes request-start rates of 40/minute on Basic, 80/minute on Growth, and 150/minute on Scale. Plan for those documented limits when sizing bursts. The dossier does not establish equivalent Cloudinary URL2PNG rate limits; check the current account documentation if throughput is a deciding factor.

Reliability

Neither the listed feature set nor pricing establishes comparative uptime or visual correctness. Pages can change, fail to load, or render differently based on their content and timing. Build operational handling around the response behavior documented by the chosen vendor: set timeouts, record status and capture metadata, and decide whether and when retries are appropriate. Avoid retrying every failure blindly, since repeated attempts can add latency and may affect quota depending on the provider’s terms.

Cost

For Cloudinary, add the URL2PNG add-on cost to the relevant Cloudinary base plan; the marketplace tier alone is not total account cost. For ScreenshotOne, include the plan, expected excess successful renders, and VAT treatment. Its pricing terms distinguish failed requests and cache hits from successful renders, so estimate billable captures using those definitions. For either vendor, recalculate from current pricing and your actual workload rather than extrapolating a per-shot price without the plan constraints.

9. Common selection and integration problems

Symptom	Likely cause	What to check or do
A Cloudinary URL2PNG delivery URL is rejected or unavailable.	The add-on may not be registered or enabled for the account, or the URL may not follow the signed/eager generation requirement.	Confirm add-on access in the Cloudinary account, use the documented URL and signing workflow, and review the Console Settings option for unsigned add-on transformations.
The Cloudinary add-on price appears lower than the expected bill.	The displayed tier is the add-on price, separate from the Cloudinary base plan.	Use the billing documentation to account for the base plan and other relevant account charges.
A ScreenshotOne request is unauthorized.	The access key is absent, invalid, or sent in a way that differs from the documented request.	Follow the current getting-started guide for authenticated GET/POST requests; keep credentials out of client-visible code.
ScreenshotOne usage is higher than expected.	Successful captures with visual issues can still count; cache misses or expired entries can trigger new renders.	Inspect request outcomes and cache behavior, then compare them with the current quota and pricing terms.
Captures are slower than the application can tolerate.	The integration may wait for page activity or request rates may exceed the selected plan’s published rate.	Review configured waits and workload burst rate. Measure representative pages; do not assume a cross-provider speed difference without a benchmark.
A visual result is incomplete or unexpected.	The source page may have changed or required rendering behavior may not be configured as expected.	Check the vendor’s current options for viewport, delay/wait, styles, blocking, and other controls relevant to the page. Validate the output against the intended use.
Monthly cost is difficult to compare.	Included quotas, add-on/base-plan relationship, cache treatment, overages, and taxes differ.	Calculate using the same expected workload and each vendor’s current billable-event definitions and full account costs.

10. Frequently asked questions

Does the documentation prove one service takes better screenshots?

No. The source set documents features and pricing, but no hands-on comparison or independent visual-quality test was performed.

Is Cloudinary URL2PNG included in a Cloudinary base plan?

The marketplace lists URL2PNG add-on tiers. Cloudinary’s billing documentation says add-ons are billed separately, and paid add-on tiers require a paid Cloudinary base plan.

Does ScreenshotOne have a free tier?

Its pricing page lists 100 screenshots per month free and says no credit card is required. Verify the live page for current terms.

Which option is suitable if I need an AI agent to request captures?

ScreenshotNeo documents an MCP server with take_screenshot, get_page_info, and capture_pdf tools for MCP clients, including Claude and Cursor.

What should I verify immediately before buying?

Current prices and quotas, Cloudinary base-plan requirements, request rates, overage terms, output formats, and the exact capture controls your implementation needs.